Upgrade to 115.3.3 has stopped me sending emails - need IMAP server as imap.outlook.com
Thunderbird has today auto-updated itself to version 115.3.3. When I try to send an email via smtp.outlook365.com, which I was able to do without problems, I get the message that login to that server has failed. The options presented are "Retry", "Enter new password" or "Cancel". When I press "Enter new password", nothing is presented to allow me to enter the new password; instead, it appears to proceed as if I had pressed "Retry".
Questions: - Why did the upgrade lose my password information? - Why does "Enter new password" not work? - How (exactly) can I configure Thunderbird to send mail via smtp.outlook365.com? - Alternatively, how can I revert to a version of Thunderbird which does not include this regression?
Wayne Mery moo ko soppali ci
Saafara biñ tànn
I think I've fixed it!
I noticed that in the (non-TB) mail client I use on my phone, the server names were different from what was in TB - the IMAP server was imap.outlook.com, and the SMTP server was smtp.outlook.com. When I changed TB to use those names (and specify "Normal password" rather than "OAuth2" as the authentication method), I was prompted to enter a password when accessing each one, those passwords were stored in the password manager under the relevant protocols, and TB is still receiving mail and has also started to send it again.
I still don't understand why TB changed those settings during the "upgrade", but at least it works now.
Jàng tontu lii ci fi mu bokk 👍 0All Replies (3)
What are your server settings?
https://support.mozilla.org/en-US/questions/1417298#answer-1588949
If there are any imap:// or smtp:// entries in Saved Passwords in Settings, remove them, restart TB, enter the account password in the OAuth window.
Thanks, but that didn't help. The only password in my list was an oauth:// one whose value bears no relation to any password I know for my account. I removed it, restarted TB, and the OAuth window appeared but then disappeared without allowing me to enter anything. When I checked the password list, the oauth:// one had reappeared but there were no others.
This set-up does give me the ability to download messages, but not to send them.
Server settings (both specifying my Outlook email address as user name): IMAP server: outlook.office365.com, port 993, security: SSL/TLS, authentication method: OAuth2. SMTP server: smtp.office365.com, port 587, security: STARTTLS, authentication method: OAuth2.
firefox2260 moo ko soppali ci
Saafara yiñ Tànn
I think I've fixed it!
I noticed that in the (non-TB) mail client I use on my phone, the server names were different from what was in TB - the IMAP server was imap.outlook.com, and the SMTP server was smtp.outlook.com. When I changed TB to use those names (and specify "Normal password" rather than "OAuth2" as the authentication method), I was prompted to enter a password when accessing each one, those passwords were stored in the password manager under the relevant protocols, and TB is still receiving mail and has also started to send it again.
I still don't understand why TB changed those settings during the "upgrade", but at least it works now.