Window Keeps Popping Up for OAuth2 for Outlook/Hotmail - solved by changing from "OAuth2" to "Normal Password"
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
People
(Reporter: matead2111, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
5.74 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36
Steps to reproduce:
Clicked on "Get Messages".
Actual results:
Whenever I click on "Get Messages", a window opens for about 1 second logging me into my Hotmail account via OAuth2. This only started happening when I updated to V115.0 (before that, I was on if I recall correctly V115.X).
Expected results:
It should check my Hotmail account without popping up a new window. It's incredibly annoying because it pops open when I'm playing games, working or watching a movie.
BTW - this only impacts my outlook.com e-mail accounts. I use a POP-3 function with T-Bird.
Couple of "work-a-rounds" I've found to work for me.
- Change Server Security Settings Authentication Method from "OAuth2" to "Normal Password"
OR
- Delete the "outlook.com" related account and then add it as a new account. However you can't just select POP-3 or IMAP. You have to select the outoook.office365 labeled account to get started. The labeling might also say something about "Exchange Server", but I can't recall for sure. Once that done you will find that you can then either select POP-3 or IMAP and proceed from there. This will then allow the "OAuth2" Authentication Method to work with the new release of T-Bird.
I did not make screen clips of all the steps I was digging through as once I got it to work and I was fed up with the update that had messed up the working of the accounts before. Just didn't want to have to spend upwards of six hours trying to figure out what went on.
Reporter | ||
Comment 2•2 years ago
|
||
(In reply to matead2111 from comment #0)
Typo: This only started happening when I updated to V117.0.
I will try your workaround @NolanK.
Comment 3•2 years ago
|
||
(In reply to matead2111 from comment #2)
(In reply to matead2111 from comment #0)
Typo: This only started happening when I updated to V117.0.I will try your workaround @NolanK.
matead2111, did you have good results?
Reporter | ||
Comment 4•2 years ago
•
|
||
(In reply to Wayne Mery (:wsmwk) from comment #3)
(In reply to matead2111 from comment #2)
(In reply to matead2111 from comment #0)
Typo: This only started happening when I updated to V117.0.I will try your workaround @NolanK.
matead2111, did you have good results?
Yes, changing it from "OAuth2" to "Normal Password" solved the issue. Thanks for your help.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 5•2 years ago
|
||
What did you upgrade from?
I wonder if these reports may be clients that were not auto-migrated to OAuth2 in the beginning of the year. Gah, I see bug 1798875 was never uplifted to 102
In case it's helpful, although I'm seeing the same issue described by matead2111 it only impacts one of my two outlook pop3 OAuth2 accounts.
I encountered this after upgrading to Tb 115.2.0 a couple of days ago.
(I am unsure of prior version, but it was at least 102.12.0.0. If it would be helpful, let me know how to determine my exact prior installed version)
Added data points are:
- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderbird/115.2.0
- My two "<xxx>@outlook.com" POP3 accounts are configured as per table below.
Account1 has the issue. Account3 is working fine. - Configuring Account1 to use "Normal password" instead of "OAuth2" works (but is an undesirable workaround ;-) )
- No issue with a gmail pop3 OAuth2 account (not shown below).
ID Name Connection Security Authentication Method
account1 (pop3) outlook.office365.com:995 SSL/TLS OAuth2
account3 (pop3) outlook.office365.com:995 SSL/TLS OAuth2
I found a similar bug report #1848370, in which this comment provides good insight as to why one Outlook account fails but another works fine.
I used the TB config editor to change the values of "mail.server.server*.oauth2.scope" and the "mail.smtpserver.smtp*.oauth2.scope" (using values as described in the linked comment) for my impacted "account1" and I'm now able to complete the oauth2 procedure successfully.
Updated•2 years ago
|
Updated•2 years ago
|
Description
•