On February 12, 2022 9:58:50 PM PST, Ranjan Maitra <mai...@email.com> wrote: >Hi, > >I am using the browser (sorry) to send this e-mail because I am no >longer able to send email from mutt from anything other than my office >account (which uses smtp and is delivered via postfix). > >So, here is what I have in my .muttrc at the very end. > > >folder-hook . 'unset smtp_url' >folder-hook '(mutt|R|fedora|postfix|fetchmail|openbox|sylpheed)' 'set >from = t...@email.com; set >smtp_url="smtps://t...@email.com@smtp.mail.com:465/"; set >smtp_pass="xxxxxxxxxxx"; set envelope_from_address="t...@email.com"; >set use_envelope_from=yes; set from = "t...@email.com"; set >forward_format = "[FW frm %a:%s]"; set realname = ""; my_hdr Bcc: ""; >set ssl_force_tls = yes; set ssl_starttls = yes' > > > >The password is correctly entered (and this configuration worked fine, >in the sense that it delivered email from this account a few weeks ago. >This has not worked for a few weeks and I finally decided to try and >see if anyone had suggestions. > > > >I am on Mutt 2.1.5 and on a full up to date Fedora 35. > > > >I tried debugging and get..... > > > >2022-02-12 23:18:26] External SSF: 256 >[2022-02-12 23:18:26] External authentication name: t...@email.com >[2022-02-12 23:18:26] mutt_sasl_cb_authname: getting authname for >smtp.mail.com:465 >[2022-02-12 23:18:26] mutt_sasl_cb_authname: getting user for >smtp.mail.com:465 >[2022-02-12 23:18:26] mutt_sasl_cb_pass: getting password for >mai...@email.com@smtp.mail.com:465 >[2022-02-12 23:18:26] Authenticating (PLAIN)... >[2022-02-12 23:18:26] 5> AUTH PLAIN ....(removed) >[2022-02-12 23:18:27] 5< 535 Authentication credentials invalid >[2022-02-12 23:18:27] 5< 535 Authentication credentials invalid
One possibility is that your email provider may have disabled normal password auth. I know that both Office365 and GSuite offer a setting to enable or disable using your account password for authentication, with the desired alternative being oauth. I don't remember offhand if there is a way to use oauth with mutt, but these providers will often provide an "app-specific password" mechanism as an alternative. Another thought is to switch to the submission port 587 if the provider offers it. Based on your error messages I doubt it's the issue, but it does provide a small security boost by removing the possibility of STARTTLS stripping attacks. --Sean
