Google services not working: OAuth2 failure when using Google Account (Fixed in TB 68.2.1) - Affects IMAP accounts and 3rd-party add-on 'Provider for Google Calendar' (check https. Also, the Thunderbird ecosystem is a lot smaller than the Firefox one, so chances are much greater of a particular specialized add-on being the only one that. I think support for OAuth2 is hard-coded in Thunderbird for each known supported OAuth2-provider. Every OAuth2 provider has its own clientSecret, which aren't really secret, because you can find them in the source. I don't know why they are hard-coded and not in the mail provider.
Configuring Mozilla Thunderbird
To set up a new account
Note: These instructions assume you are running a version of Thunderbird 77.0b1 or later which supports OAuth2 modern authentication.
1. The Mail Account Setup dialog box should open the first time you open Thunderbird.
a. If it does not open:
i. Locate the Menu button in the top right corner.
ii. Click Menu > Account Settings...
iii. On the Account Settings page, under Account Actions, click Add Mail Account.
2. In the Mail Account Setup dialog box, enter the following information:
a. Your Name: enter the name you want on the 'From' line in your outgoing messages
b. Email Address: enter your @usf.edu email address
c. Password: enter your @usf.edu email password
d. Make sure the Remember password box is checked
3. Click Configure Manually
4. Enter the following information:
a. Incoming server hostname: outlook.office365.com
b. Outgoing server hostname: outlook.office365.com
c. Username: enter your @usf.edu email address
d. Change the Incoming Port field to 993 and the Outgoing Port field to 587.
e. Change the Incoming SSL field to SSL/TLS and Outgoing SSL field STARTTLS.
5. Once this information is filled in, select Advanced Config and then click OK in the popup.
6. In the Authentication Method dropdown menu, select OAuth2.
7. Select the Outgoing Server (SMTP) section in the left bar, click on your email address and click Edit.
8. In the Authentication Method dropdown menu, select OAuth2.
9. Restart Thunderbird. Once it restarts, it should prompt you to log in and accept MFA unless you have already done so.
Setup Thunderbird For Att Email
To change the settings on an existing account

Mozilla Thunderbird And Oauth
Note: These instructions assume you are running a version of Thunderbird 77.0b1 or later which supports OAuth2 modern authentication.
1. Open Thunderbird.
2. Locate the Menu button in the top right corner.
3. Click Menu > Account Settings...
4. Click Server Settings under your @usf.edu email.
5. Enter the following information:
a. Server Name: outlook.office365.com
b. Port: 993
c. User Name: your @usf.edu email address
d. Select SSL/TLS from the Connection security dropdown menu
e. Select OAuth2 from the Authentication method dropdown menu
6. Open the Outgoing Server (SMTP) menu. Open the server for your @usf.edu email.
7. Click Edit...
8. Enter the following settings:
a. Server Name: outlook.office365.com
b. Port: 587
c. Select STARTTLS from the Connection security dropdown menu
d. Select OAuth2 from the Authentication method dropdown menu
e. User Name: your @usf.edu email address
9. Click OK.
10. Click the Get Messages button.
11. Enter your @usf.edu email password when prompted. Check the box to Use Password Manager to remember this password and click OK.
Oauth2 Thunderbird For Sale
wrote:That possibly is the answer.
>Op 10-7-2020 om 13:03 schreef Stans:
>> On 10/07/2020 13:48, Onno Ekker wrote:
>>>
>>> I think support for OAuth2 is hard-coded in Thunderbird for each known
>>> supported OAuth2-provider.
>>> Every OAuth2 provider has its own clientSecret, which aren't really
>>> secret, because you can find them in the source.
>>> I don't know why they are hard-coded and not in the mail provider
>>> database, because now it's much harder to add a single new issuer.
>>> As far as I know, there is no way to add the needed client secret for
>>> your own OAuth2-provider yourself, except maybe by writing an add-on if
>>> there's an API for it.
>>>
>>> Onno
>>>
>> To make things clear, Telus is not the OAuth2 provider here. Google is,
>> and Tbird had Google's OAuth2 support added many years ago. This move by
>> Telus implies that Telus is not willing to implement its own OAuth2, but
>> would rather use a pre-existing provider (Google) as its new host for
>> its email accounts.
>
>K, so basically the OP is using GMail, right? Then there shouldn't be an
>problems. But if Telus provides its own mail server names, which
>redirect to GMail's mail servers, then it won't work.
As I said originally Telus mail is now 'powered by Google'. My
address remains as 'youknowwho at telus dot net'.
Logging into mail on-line (what Telus used to call 'webmail') launches
a Gmail interface but labelled with the Telus logo along with the
settings icon etc. in the top right.
