Re: Disabling specific SMTP authenticator

2014-09-08 Thread Alexander Gattin
Hello, sorry for late reply, On Sat, Aug 30, 2014 at 04:01:43PM -0500, Russell Urquhart wrote: ... from 1.5.19 to 1.5.23, and copied that to the appropriate location, for 1.5.23. When i try and get mail i get an ssl failed error. Did something in the muttrc, change from how SASL is

Re: Disabling specific SMTP authenticator

2014-08-30 Thread Russell Urquhart
On Sat, Aug 23, 2014 at 05:30:38AM -0700, Alexander Gattin wrote: Can you please send .muttdebug log? Or relevant portions of it (SMTP error reply to CRAM-MD5 attempt)? Hi, I compiled the 1.5.23 version with debug. I copied the muttrc from my 1.5.19, which is the current version of mutt i

Re: Disabling specific SMTP authenticator

2014-08-23 Thread Alexander Gattin
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

Re: Disabling specific SMTP authenticator

2014-08-23 Thread Alexander Gattin
On Sat, Aug 23, 2014 at 05:30:38AM -0700, Alexander Gattin wrote: 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. Another elegant solution would be to contact Verizon's admins and ask them to fix

Re: Disabling specific SMTP authenticator

2014-08-23 Thread Russell Urquhart
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

Re: Disabling specific SMTP authenticator

2014-08-23 Thread Russell Urquhart
On Sat, Aug 23, 2014 at 05:39:11AM -0700, Alexander Gattin wrote: Another elegant solution would be to contact Verizon's admins and ask them to fix the bug in their SMTP server. You would need to provide them the .muttdebug log too. The people posting on the Verizon support site said that

Re: Disabling specific SMTP authenticator

2014-08-23 Thread Alexander Gattin
On Sat, Aug 23, 2014 at 09:12:06AM -0500, Russell Urquhart wrote: Is a .muttdebug log created automatically? How how do i get one or find it? I'll gladly send what i have! You can safely send log of CRAM and DIGEST MD5 attempts, but not PLAIN or some others like LOGIN for IMAP, because the log

Re: Disabling specific SMTP authenticator

2014-08-19 Thread Luis Mochan
I don't think i have a .msmtprc file, what program is that associated with? msmtp, lightweight smtp client, http://msmtp.sourceforge.net/

Re: Disabling specific SMTP authenticator

2014-08-19 Thread Bob Holtzman
On Mon, Aug 18, 2014 at 11:24:06PM -0500, Russell Urquhart wrote: On Mon, Aug 18, 2014 at 06:47:00PM -0700, Bob Holtzman wrote: Does your ~/.msmtprc file have an auth on entry? If so, is it commented out? If it's there and not commented out, what does commenting it out do? I don't

Re: Disabling specific SMTP authenticator

2014-08-19 Thread Russell Urquhart
On Mon, Aug 18, 2014 at 10:49:06AM -0700, Alexander Gattin wrote: Then you can set the smtp_authenticators parameter to include all methods except CRAM-MD5: set smtp_authenticators=otp:digest-md5:login:plain:anonymous In my case there were problems with PLAIN method and excluding it

Re: Disabling specific SMTP authenticator

2014-08-19 Thread Paul E Condon
On 20140818_2324-0500, Russell Urquhart wrote: On Mon, Aug 18, 2014 at 06:47:00PM -0700, Bob Holtzman wrote: Does your ~/.msmtprc file have an auth on entry? If so, is it commented out? If it's there and not commented out, what does commenting it out do? I don't think i have a

Re: Disabling specific SMTP authenticator

2014-08-18 Thread Alexander Gattin
Hello, On Sun, Aug 17, 2014 at 01:59:52PM -0500, Russ Urquhart wrote: Is there a way to disable mutt from trying to do this authentication? I know the smtp_authenticators is a list of methods to try but does someone know the entire list mutt enabled SMTP tries? I could maybe list all BUT

Re: Disabling specific SMTP authenticator

2014-08-18 Thread Alexander Gattin
On Mon, Aug 18, 2014 at 07:18:23AM -0700, Alexander Gattin wrote: IIRC CRAM and other MD5 auth types work via SASL because they are not built in mutt. You can get list of available SASL methods via e.g. Tcl (you need both tcl and tcllib packages installed AFAIU): xrgtn@x505:~$ tclsh %

Re: Disabling specific SMTP authenticator

2014-08-18 Thread Bob Holtzman
On Sun, Aug 17, 2014 at 01:59:52PM -0500, Russ Urquhart wrote: Hi, I have Verizon and have been using mutt to send email without problems. As I understand it, as of 8/1, the Verizon SMTP servers are advertising that cram-md5 is available when in fact it isn't and this is causing me to

Re: Disabling specific SMTP authenticator

2014-08-18 Thread Russell Urquhart
On Mon, Aug 18, 2014 at 06:47:00PM -0700, Bob Holtzman wrote: Does your ~/.msmtprc file have an auth on entry? If so, is it commented out? If it's there and not commented out, what does commenting it out do? I don't think i have a .msmtprc file, what program is that associated with? I

Disabling specific SMTP authenticator

2014-08-17 Thread Russ Urquhart
Hi, I have Verizon and have been using mutt to send email without problems. As I understand it, as of 8/1, the Verizon SMTP servers are advertising that cram-md5 is available when in fact it isn't and this is causing me to recently start to get an authentication error when I try and send mail