Re: smtp authentication fails

Chris Wilson <[email protected]> Fri, 7 Dec 2007 19:03:49 +0000 (GMT)
Newsgroups gmane.mail.pine.general
Message-ID <[email protected]>
Hi all,

On Fri, 7 Dec 2007, Marc Greene wrote:

> IMAP DEBUG 03:33:59 12/7: 220 lavabit.com ESMTP lavad
> IMAP DEBUG 03:33:59 12/7: EHLO riverstone
> IMAP DEBUG 03:33:59 12/7: 250-lavabit.com
> IMAP DEBUG 03:33:59 12/7: 250-PIPELINING
> IMAP DEBUG 03:33:59 12/7: 250-AUTH LOGIN PLAIN
> IMAP DEBUG 03:33:59 12/7: 250-AUTH=LOGIN PLAIN
> IMAP DEBUG 03:33:59 12/7: 250 Okay.
> IMAP DEBUG 03:33:59 12/7: AUTH PLAIN
> IMAP DEBUG 03:34:00 12/7: 501 Invalid AUTH command.
> IMAP 03:34:00 12/7 mm_log error: Can not authenticate to SMTP server: 501
> Invalid AUTH command.
> IMAP DEBUG 03:34:00 12/7: QUIT
> IMAP DEBUG 03:34:00 12/7: 221 Bye.
> call_mailer ERROR: Error sending: Can not authenticate to SMTP server: 501
> Invalid AUTH command.
> Send failed, continuing
> 
> So it appears that even though the lavabit.com settings page states that 
> their server supports LOGIN and PLAIN authentication, and the 
> lavabit.com server advertises it, that the server really doesn't support 
> PLAIN authentication, but only LOGIN. I was able to force pine into 
> using LOGIN authentication by adding
> 
> disable-these-authenticators=PLAIN
> 
> to my .pinerc, and now it is able to send mail through lavabit.com.
> 
> Thanks to everyone who gave help :)

Might I suggest to the Pine developers that if a supported authentication 
method fails, we fall back to the next one and so on until we run out of 
authentication methods?

Cheers, Chris.
-- 
_____ __     _
\  __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info