On Sat, Aug 23, 2014 at 05:30:38AM -0700, Alexander Gattin wrote: > Hello, > > On Mon, Aug 18, 2014 at 11:24:06PM -0500, Russell > Urquhart wrote: > > I ended up including all the smtp > > authenticators, BUT cram-md5. > > > > If someone knows a more elegant solution, i'm > > all ears. > > What you'd like instead IMHO is for mutt to > continue with other authentication methods after > failing with CRAM-MD5.
That would be nice. I think, as i'll explain further, that the problem is Verizon's and really should be fixed on their end. Mutt worked fine until THEY did this on their server. > > Currently mutt doesn't continue because most > probably this error is treated like "wrong > password" (so there's no sense to continue trying > the same wrong password with less secure methods). > > If it's possible to distinguish "wrongly > advertized auth method" from "wrong password" > error reply, it's possible to fix the problem in > elegant way. > I had to dig on the Verizon support sites, but from what i gathered, the authentication is 'advertised" but actrually not there or supported. On my end, it looks like mutt tries to do the authentication, doesn't find it, and then i get a SMPT authentication failure. > Can you please send .muttdebug log? Or relevant > portions of it (SMTP error reply to CRAM-MD5 > attempt)? > Is a .muttdebug log created automatically? How how do i get one or find it? I'll gladly send what i have! Thanks, Russ
