Branch: refs/heads/master
Home: http://github.com/abh/qpsmtpd
Commit: 3889821d165b1c507ba94c086410dbb2ce798a24
http://github.com/abh/qpsmtpd/commit/3889821d165b1c507ba94c086410dbb2ce798a24
Author: Devin Carraway <[email protected]>
Date: 2009-12-23 (Wed, 23 Dec 2009)
Changed paths:
M plugins/queue/exim-bsmtp
Log Message:
-----------
Use BSMTP response code; misc cleanups
Exim's BSMTP interface will indicate the SMTP response to the exchange;
actually use it rather than assuming all errors are 400-class soft ones.
Tolerate $transaction->header returning undef (since it evidently can under
some conditions).
Convert a few errant tabs to spaces.
Fix vi modeline.
Signed-off-by: Robert <[email protected]>
Commit: 7de104bf663c041fca8e6d1dc16dd6d97bfa6848
http://github.com/abh/qpsmtpd/commit/7de104bf663c041fca8e6d1dc16dd6d97bfa6848
Author: Rick <[email protected]>
Date: 2009-12-24 (Thu, 24 Dec 2009)
Changed paths:
M lib/Qpsmtpd/Auth.pm
Log Message:
-----------
AUTH PLAIN bug with qpsmtpd and alpine
Trying to get SMTP auth working with alpine, I came across a bug.
Alpine sends AUTH PLAIN and waits for a 334 response, then sends the
auth string. According to the RFC, the server should reply with 334
and a nothing else, but in Auth.pm qpsmtpd responds with "334 Please
continue." the "Please continue" is interpreted as a non-zero
length initial challenge which causes alpine (and maybe other
clients?) to abort the session.
Signed-off-by: Charlie Brady <[email protected]>
Signed-off-by: Robert <[email protected]>
Commit: 44c67fcbc7276c1c66e6b0319e4302c1046083b5
http://github.com/abh/qpsmtpd/commit/44c67fcbc7276c1c66e6b0319e4302c1046083b5
Author: Devin Carraway <[email protected]>
Date: 2010-01-14 (Thu, 14 Jan 2010)
Changed paths:
M lib/Qpsmtpd.pm
M lib/Qpsmtpd/Postfix.pm
Log Message:
-----------
Add a whatis to Qpsmtpd.pm and Postfix.pm's POD
Signed-off-by: Robert <[email protected]>
