I've done a bit more tracing. Here's the "dispatching" sequence I
found, which I suspect is correct:

dispatching EHLO rope.net
dispatching STARTTLS
dispatching EHLO rope.net
dispatching AUTH CRAM-MD5

        The response to the first EHLO is correct:

250-testsmtp.rope.net Hello internal.rope.net [192.168.1.75]
250-PIPELINING
250-8BITMIME
250-STARTTLS
250 AUTH CRAM-MD5

        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.

        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. (I'd still appreciate a solid example of an entry in
config/auth_flat_file and the equivalent login name to use in the mail
client.) When done from a Netscape 7.1 on Windows, this is where the
plugin fails, right at the top of the plugin:

    my ( $pw_name, $pw_domain ) = split "@", lc($user);

    unless ( defined $pw_domain ) {
        return DECLINED;
    }

Reply via email to