removed the slash from all below changed [email protected] to just me:[email protected]
and still can’t send a email also CONFIG : set smtp_url = "smtp://[email protected]:[email protected]:25" ERROR : SASL authentication failed CONFIG : set smtp_url = "smtp://[email protected]:[email protected]:465" ERROR : SASL authentication failed CONFIG : set smtp_url = "smtp://[email protected]:[email protected]:587" ERROR : SASL authentication failed tried with set ssl_starttls=yes set ssl_force_tls = yes now getting No authenticators available so with CONFIG : set smtp_url = "smtp://[email protected]:[email protected]:587" set ssl_starttls=yes set ssl_force_tls = yes OR set smtp_url = "smtp://me:[email protected]:587" set ssl_starttls=yes set ssl_force_tls = yes I get ERROR: No authenticators available so searched google, and said to try these config items CONFIG : set smtp_authenticators = "login" ERROR : SASL authentication failed IN DEBUG FILE : 7< 535 5.7.3 Authentication unsuccessful SASL authentication failed CONFIG : set smtp_authenticators = "gssapi:login" ERROR : SASL authentication failed IN DEBUG FILE : 7< 535 5.7.3 Authentication unsuccessful SASL authentication failed CONFIG : set smtp_authenticators = "sasl:login" ERROR : SASL authentication failed IN DEBUG FILE : 7< 535 5.7.3 Authentication unsuccessful SASL authentication failed still no go, does anyone have a working mutt config to a exchange 2013 server ? or any ideas on how to get my mutt config to work > On May 25, 2015, at 2:57 PM, Paul <[email protected]> wrote: > > On Friday, 22 May, 2015 at 01:56:52 BST, cipher wrote: >> set smtp_url = "smtps://[email protected]:[email protected]:587/" >> set smtp_url = "smtps://[email protected]:[email protected]:465/" >> set smtp_url = "smtps://[email protected]:[email protected]:25/“ >> >> set smtp_url = "smtp://[email protected]:[email protected]:587/" >> set smtp_url = "smtp://[email protected]:[email protected]:465/" >> set smtp_url = "smtp://[email protected]:[email protected]:25/" > > I don't have the trailing slash in mine. Could it be that, or maybe it's > getting confused by the @ in your username?
