I can't log in to may mail on outlook with OAuth2
MS changed authorization method and now it require protocol OAuth2. I've changed my account for two layers authorization and tried change Thunderbird configuration due https://support.mozilla.org/en-US/questions/new/thunderbird/form but it not works. I can't connect. I've no problems to connect with Outlook and standard mail app for Win2010 or using BlueMail on android. Ive Thunderbird v. 115.11.0 (32)
Can You help me? I'd prefere to stay with Thunderbird.
Maciej Garnysz
All Replies (10)
MS sent messages to users about server changes. Try these: - incoming: outlook.office365.com, port 993, SSL/TLS, Oauth2 (assuming IMAP) - outgoing: smtp.office365.com, port 587, STARTTLS, Oauth2
I have 2 live.com and 1 outlook.com in TB. All suddenly had problems sending emails. The 2 live.com accounts were fixed by removing and then adding the accounts. However, the same method did not fix the outlook.com account. In fact checking TB's auto-filled info when adding back the outlook.com account showed it was using one of the live.com email addresses in the User Name field for the outgoing SMTP server! However, my fixing that did not fix the problem with sending emails.
I'm guessin' TB is assigning the wrong info for the outlook.com account (and the correct info for the live.com accounts)??
BTW, when adding the outlook account, TB did use the values shown in the previous message here ...
EDIT: bold emphasis added
Okulungisiwe
Incidentally, further to the above, the two affected live.com accounts had no problems sending in the K9 email app on Android. Only in TB did the problem occur.
I don't use the outlook.com email account on the Android device so am unable to check this.
Do all of the accounts have the settings I proposed? If so, what error messages are you seeing? Please post actual screenshots of each account that is giving you problems.
Yes, as said, all the accounts have the settings you proposed.
Today, with no changes made, the situation is different: the one still problematic outlook.com account seems to send but does not show the normal progress boxes. And the recipients do not receive the "sent" messages. Unlike previously, there are no error messages.
It's possible that the problem lies with the Microsoft email account, or, that TB is handling the send requests wrongly for this account.
To reiterate, all settings are the same for the two now-functional and one non-functioning accounts.
No need for screenshots: I've said it all here.
UPDATE: Just now the sent email from the problematic outlook.com account was received. As well, an email sent yesterday from that account's webmail service arrived. Given these odd events it seems the problem was primarily with the outlook.com account itself. So, everything kinda seems to have fixed itself ...
The problem with the 2 live.com accounts were, however, evidently with TB and the OP might try removing and re-adding their email account as that worked for me.
Okulungisiwe
Thanks a lot David. You help to resolve my probIem. It's all right now.
Thanks for the feedback. I was glad to assist. :)
My problem has re-emerged.
Changed nothing yet one of the live.com accounts was unable to send today.
In Edit SMTP server > User name was the wrong email address (taken from another email account in TB). This was a problem previously as described above. Editing this has apparently fixed the problem, at least temporarily.
This seems to be a bug in Thunderbird.
Although possible, a bug is unlikely. I say that because whenever a user reports that the SMTP server pane automatically changes, it has been because the user has more than one account with that email host and either has the SMTP servers swapped or is using the same one for both accounts, This is most easily cleared by editing the DESCRIPTION field on every SMTP server setting to be unique, and then clicking the account setting pane for each account and verifying the proper description apppears on the line linking to SMTP server.
But then why has the issue just suddenly appeared after being fine for years? No changes have been made - except the recently updated TB version ...
I'll try implementing your suggested fix, thx.
I'd like to transfer all of this to a new thread if possible ...