[pmmail-list] SMTP Authentication

[Kevin Murphy]

Folks,

As a followup to my email from yesterday, I would like to point out that I have been corresponding with some folks involved with the e-mail server package I have been trying to work with, and they 
seem to be pointing to a defficiency in the way PMMail handles SMTP authentication.  Apparently the fallback/renegotiation method you have attempted would be adequate if PMMail waited around 
long enough for such a fallback to take place.  But unfortunately it seems that as soon as the CRAM-MD5 attempt fails, PMMail gives up and drops the connection, never attempting to continue on 
with LOGIN or in the future PLAIN.  This is my main reasoning for requesting that I be able to specify which authentication method PMMail uses when communicating with different servers.  I have only 
until Monday to come up with a solution, and things are really getting down to the wire here.  Can anyone provide any information?

As you can see in the following log extract, PMMail does not seem to wait around to even receive a response from the server.  As soon as I tell PMMail to send, I immediately get a successful response 
on the client side, and it has no idea that its authentication attempt has failed on the server side.

Aug 21 13:25:21 rockhopper courieresmtpd: started,ip=[::ffff:10.0.1.14]
Aug 21 13:25:21 rockhopper courieresmtpd: error,relay=::ffff:10.0.1.14,msg="535 Authentication failed.",cmd: AUTH CRAM-MD5
Aug 21 13:25:29 rockhopper courieresmtpd: error,relay=::ffff:10.0.1.14,msg="535 Authentication required.",cmd: MAIL FROM: <kevin@sargonps.com>
Aug 21 13:25:29 rockhopper courieresmtpd: writev: Connection reset by peer

Please let me know what you plan to do to correct this behavior.

Thanks!



--
Kevin Murphy
computec@bigfoot.com