Closed Bug 1777714 Opened 2 years ago Closed 2 years ago

TB 102 break OAuth2 connections to


(Thunderbird :: Security, defect)

Thunderbird 102
Windows 10


(Not tracked)



(Reporter: evan.cooch, Unassigned)


(Blocks 1 open bug)


User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36

Steps to reproduce:

I recently updated TB from 91.10.x.x -> 102.0. Win 10 Pro - fully patched. Previously, been using OAuthy2 and TLS/SSL to connect to POP at Worked perfectly.

Following the upgrade, no longer able to connect to, at all.

To confirm it wasn't an addon issue, or anything else, I did a clean install of TB 102 in a fresh Win 10 install inside a virtual machine. I first tried using TLS/SSL and OAuthy2 to connect to Worked perfectly (suggesting the issue isn't with the OAuthy2 implementation in TB). But, when I tried again to connect to, failed completely.

Issue has been replicated by a number of people I work with who use TB -- 102 breaks connecting to

Actual results:

No connection

Expected results:

I should have been able to connect to, and download email.

OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Summary: TB 102 break OAuthy2 connections to → TB 102 break OAuth2 connections to

As part of experimenting with things, I re-configured and used IMAP instead of POP. Worked perfectly. So, this tells me that something fundamental has changed on the MS side of things. (maybe?) So, perhaps not a 'bug' after all, but merely (another) Draconian decision on the MS side of things?

Component: Untriaged → Security

You might want to try changing the user agent string. Just to see if the Outlook environment is responding differently to the newer version.

Perhaps try Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.1

The default can be overridden by setting the preference general.useragent.override in the config editor. See

The preference does not exist by default, so you will have to add a new string preference.

Is your office set up a business one? OAuth, at least in my case, does not work with free accounts. Office subscription arrangements however are probably being subjected to the process Microsoft have embarked on to automatically disable IMAP, SMTP and POP access to office business users unless a business admin actively enables it. There has been plenty of activity in recent months in support as organisations lock out IMAP, POP and SMTP for "security reasons". Not that any of those doing so can actually advise what the security reason is. My guess is they are just quoting Microsoft and they really have no idea.

Alas, I tried setting the general.useragent.override preference (thanks for the suggestion!), but that didn't work, I'm afraid. Troubleshooting information showed the modified User Agent had been set correctly, so I don't think its a 'typo' or anything that silly on my end.

I think the fact that configuring for IMAP connections worked, while my preferred protocol (POP) didn't, is likely informative.

If it helps at all, if I look at the Error Console output, I see the following generated at TB tries to connect to via POP:

09:05:20.879 services.settings: Failed to load last_modified.json: TypeError: NetworkError when attempting to fetch resource.
about:accountsettings : Unable to run script because scripts are blocked internally.

Forgot to add - setup is 'business' (well, not stricly -- ['higher education' -- large research-based university). Booth POP and IMAP have been turned on by our site admins (confirmed) -- must be true since both IMPA and POP were working fine with Oauth2 using TB 91.x.x. So, something has changed in TB 102.x.x that no longer plays nice with POP. Which is why I (tentatively) think this is a bug.

And, another byte of information: Using TB 102, OAuth2 works fine form

So, for OAuth2 --- IMAP - 102 works; SMTP - 102 works; POP - 102 fails.

Blocks: tb102found

I'm using version 103b4 and for me the breakdown with protocols and OAuth2 is:

IMAP - works
POP - don't use it

Was working perfectly fine last week, this week, nup. How can I debug the SMTP connection? I suspect the change was on the Microsoft side.

Far: smtp would be unrelated (and likely just a network issue)

Closed: 2 years ago
Resolution: --- → DUPLICATE

Indeed - resolved in code hack implemented in TB 103.0b6. Tested against POP for,, and a few others. All worked without obvious problems.

You need to log in before you can comment on or make changes to this bug.