+(this document is taken from +http://pobox.com/~djb/docs/smtplf.html) + +
+Solaris 2.5 sendmail: +Upgrade! +Fixed in Solaris 2.5.1. +You can fix the problem by putting ``,E=\r\n'' +at the end of Mether, Mtcp, or Msmtp in sendmail.cf. +(Note that Mether is not the same as DMether.) +
+sendmail V8 has a bug that will produce a bare LF +in certain messages (e.g., messages with very long lines). +This bug was identified in November 1996; +I don't know if it has been fixed yet. +
+Eudora Pro 4.0 for Windows: +Upgrade! +The HTML LF problem was fixed in 4.0.1. +The attachment LF problem was fixed in 4.1. +
+listproc 6.0c: +Chuck Foster says you should add ``CONVERT(buf);'' +before ``WRITE_TO_SOCKET'' around line 165 of sysmail.c +in the Listproc source code. +
+fetchmail: +Upgrade! +Recent versions of fetchmail reportedly do the right thing. +Make sure the forcecr option is on. +
+Galacticom WorldGroups: +Reported 19970716. No information yet on how it can be fixed. +
+Claris Emailer: +Reported 19980613. No information yet on how it can be fixed. +
+Every line in an Internet mail message +is required to end with CR LF. +The entire message ends with CR LF dot CR LF. +822bis specifically prohibits other uses of LF. +
+The mail clients discussed above +are incorrectly ending lines with LF +and, in most cases, ending the entire message with LF dot LF. +That's not CR LF dot CR LF, +so a server such as msn.com +will sit there waiting for the rest of the message. +After a while it'll give up and drop the connection. +Your mail doesn't get through. +
+Some mail servers convert a bare LF into CR LF, +and accept LF dot LF +as the end of a mail message. +This behavior is specifically prohibited by 821bis (and RFC 2821). + diff --git a/get.html b/get.html new file mode 100644 index 00000000..7f315ddf --- /dev/null +++ b/get.html @@ -0,0 +1,96 @@ + + + + + + +
qpsmtpd is actively developed, but very stable software. We +typically make a new release every 3-9 months.
+ +
+Latest release: 0.84 (April 7, 2010)
+Previous release: 0.83 (September 15, 2009)
+
+See the Change log
+
+
+You can also get qpsmtpd with Git. +
+ +Many users are using custom `forks` with their particular +value-added changes on top. If you go that route it's highly +recommended that you fork from git to make it easier to contribute +back the changes you wish to share. + +
+ ++ git clone git://github.com/smtpd/qpsmtpd.git ++ +
+ +You can browse the +repository. + +
+ +qpsmtpd has been used for the primary perl.org mail servers since +2001. At apache.org they are also using qpsmtpd for their mail +services. Years ago a happy user wrote and told that qpsmtpd is +rejecting several hundred thousand spams a day on his server; these +days that's too common to be exceptional. + + +
+ +qpsmtpd is a flexible smtpd daemon written in Perl. Apart from the +core SMTP features, all functionality is implemented in small +"extension plugins" using the easy to use object oriented plugin API. + +
+ ++qpsmtpd was originally written as a drop-in qmail-smtpd replacement, +but now it also includes smtp forward, postfix, exim and maildir +"backends". +
+ ++ +
+The important part is that there's no warrenty, but you can otherwise +do whatever you want with the software. (Use it, sell it, publish it, +modify it, sublicense, put it on a cd, burn the cd...). Just don't +remove the copyright and license. +
+ ++
+ +Copyright (C) 2001-2010 Ask Bjørn Hansen, Develooper LLC + +Permission is hereby granted, free of charge, to any person obtaining a copy of +this software and associated documentation files (the "Software"), to deal in +the Software without restriction, including without limitation the rights to +use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies +of the Software, and to permit persons to whom the Software is furnished to do +so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. + ++ +
+If you didn't recognize it; this is +the MIT +License; one of the most developer friendly and unrestrictive +licenses around. +
+ ++You can take the software and do whatever you want with it. Build a +service, distribute it on your spam-filtering appliance, make a +million bucks, give changes back, don't give changes back - it's all +allowed and encouraged. +
+ + + + ++Send mail to qpsmtpd-subscribe@perl.org +to subscribe. There is also a +web archive and a nntp interface. +
+ ++Most development activity occurs (still) on the qpsmtpd list, but we have a +separate list for commit messages and such. It's called qpsmtpd-dev. Web archive and a nntp interface. +
+ ++You can also subscribe +to release notifications over at the Freshmeat page for +qpsmtpd. +
+ + + +