On Mon, 4 Mar 2002 07:54:51 -0600 (Central Standard Time) Jonathan Fosburgh 
<[EMAIL PROTECTED]> wrote:

JF> My ISP recently upgaded their SMTP, POP, and (now) IMAP server to
JF> Communigate Pro.  They still seem to be having problems with
JF> authentication, so I thought I would post here so I can try to check my
JF> mail with Mahogany.  This is 0.64 running on NT4+SP6. Here is a log trying
JF> to check with POP, which is what I had previously been using:
JF> 
JF> 07:53:47: Mail log: +OK POP3 Server 3.5.6 ready <[EMAIL PROTECTED]>
JF> 07:53:47: Mail log: POP3 Server 3.5.6 ready <[EMAIL PROTECTED]>
JF> 07:53:47: Mail log: AUTH
JF> 07:53:47: Mail log: +OK methods supported:
JF> 07:53:47: Mail log: LOGIN
JF> 07:53:47: Mail log: PLAIN
JF> 07:53:47: Mail log: CRAM-MD5
JF> 07:53:47: Mail log: DIGEST-MD5
JF> 07:53:47: Mail log: NTLM
JF> 07:53:47: Mail log: .
JF> 07:53:47: Mail log: AUTH CRAM-MD5
JF> 07:53:47: Mail log: + PDE1ODc3MS4xMDE0OTA0MjA1QG1haWwuaGFsLXBjLm9yZz4=
JF> 07:53:47: Mail log: c3lqZWYgNWVlOTQ4MDk4ZTE0MWVjY2I1ZWY0ZmNhMTc5YThhNDI=
JF> 07:53:49: Mail log: -ERR incorrect password or account name
JF> 07:53:49: Mail log: Retrying using PLAIN authentication after incorrect password 
or account name
JF> 07:53:49: Mail log: AUTH PLAIN
JF> 07:53:49: Mail log: + 
JF> 07:53:49: Status: Mail log: SECURITY PROBLEM: insecure server advertised AUTH=PLAIN
JF> 07:53:49: Mail log: -ERR SASL protocol has been interrupted
JF> 07:53:49: Error: Mail log: POP3 Authentication cancelled
JF> 07:53:49: Mail log: QUIT
JF> 07:53:49: Mail log: +OK POP3 Server connection closed

 Hello,

 sorry for the delay with the reply but I had to ask for help elsewhere as
I didn't understand very well what was going on here. I did get help but
the problem is that it still doesn't explain much :-(

 Anyhow, here is what I found out:

1. the "SECURITY PROBLEM" message can be ignored, it just means that the
   server is in violation of the RFC but it shouldn't result in any
   problems

2. everything else looks correct, so here is what Mark Crispin wrote in
   reply to my question as to why the authentification failed:

        Either the password is wrong, or there is something wrong with the
        server (possibly its authentication database isn't set up right).
        I'd suggest bringing in the Stalker people since Communigate Pro is
        their product; they'd be the ones to persue that question and
        determine what's going on.
 
   So all I can do is to repeat the advice that you

   a) check your password (I guess you already did it but well... BTW, can
      you login manually to your POP3 server by doing "telnet pop 110" and
      typing in "USER yourname" and "PASS password"?)

   b) contact your POP3 server vendor

JF> Is there some way to bypass SASL in Mahogany, since that appears to be
JF> what is necessary for the time being?

 Mark has also explained me how to do this but it's not possible in 0.64
unless you're willing to rebuild it yourself.

 Regards,
VZ


_______________________________________________
Mahogany-Users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mahogany-users

Reply via email to