I’ve been using mutt for sometime now (1.5.23). Compiled with SASL it has
worked with out issue. A couple of weeks ago I ended my contract with
Verison/Frontier/AOL and was concerned that my [email protected] email
address would no longer work. I started to see this sporadic working of the
SASL component of mutt, and I started to take apart my mutter file. As I WAS
able to get the Mail app on my OS X laptop to work with my email address, I
surmised that everything must be ok, I put my muttrc back to the way it was,
and things worked fine. Until about now. :(
Here what is happening after I load mutt and do a Shift-g to load new mail:
1. Certificate Host failed:
Then it offers me to reject, accept once, or accept always. I take the
always.
2. then it tries authenticating SASL (this seems to take a while, Then:
SASL authentication failed.
3. It goes to Logging in…
for a long time until it comes back with:
Login failed: PASS: [SYS/TEMP] Server error - Please try again later
I think my incoming and outgoing mail servers are ok. They are the ones and
same credentials that I use for the OS X Mail app (which is working) and my
iphone. Is there something on the SASL authentication?
Here are some specifics from my muttrc file:
set
smtp_authenticators="external:anonymous:plain:otp:skey:digest-md5:scram:ntlm:gssapi:browserid-aes128:eap-aes128”
This is a pop access to the mail servers.
Can anyone shed any light on this? Please help don’t want to stay in Mail app!!
:)
Thanks,
Russ
