[EMAIL PROTECTED] wrote:
The responsee to the 2nd EHLO is different:
250-sprint.rope.net Hello []
250-PIPELINING
250-8BITMIME
AUTH CRAM-MD5
For some reason, the values for $conn->remote_info and
$conn->remote_ip cannot be found the 2nd time through.
That's fixed in branches/0.3x, but it has nothing to do with the AUTH
failure (it will prevent relaying however). Can we release 0.31.2 to
cover the few fixes on the branch? Ask??? Is this thing on????? ;-)
I'm not convinced that this is a direct issue - it's just using
the values for a response to EHLO. However, might it be indicative of
something that causes the AUTH to fail? I'm going to try some connections
using Outlook 2000.
My recommendation is that you stop using fat MUA's (which purposely hide
implementation details from the user). Try using swaks instead:
http://www.jetmore.org/john/code/#swaks
which is a Perl e-mail client (with TLS support) that makes it very easy
see the entire SMTP transaction (including AUTH negotiations).
John
