Thunderbird won't connect to ATT - Using OAuth and Secure Mail Key
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
People
(Reporter: kricks, Unassigned)
Details
Attachments
(1 file)
|
740.01 KB,
image/jpeg
|
Details |
Tbird Error Log.jpg
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0
Steps to reproduce:
About 4 days ago, TB stopped connecting to ATT. I determined that ATT was requiring a Secure Mail Key. I took these steps.
- Generated a Secure Mail Key
- Used that when prompted for new password.
- Changed to OAuth2
- Entered new key.
- It worked! Was able to download 184 messages
- Tested sending. Added new key to outbound server. It worked.
- closed everything and turned machine off. (normal procedure here)
- Fired everything up and loaded Tbird.
- It failed on ATT access. Google access fine using OAuth
- Continues to fail.
Actual results:
As noted above. Fails miserably. Lots of errors in console log.
Expected results:
Should connect. Snapshot of console log included. From a fresh startup of Tbird.
I can access the account via web and phone. I made no other changes.
|
||
Updated•3 years ago
|
|
||
Comment 1•3 years ago
|
||
Similar to Bug 1698316? ATT and associated domains do not have access to oAuth in Thunderbird as they do not use Yahoo.com server names.
Given that OAuth only appears as an authentication option when the server names match the preset list, how do you "change to OAuth"?
Are you hacking the prefs.js file directly?
A "Secure Mail Key" is nothing more than a 10 digit password generated by the provider. It is not going to be used in the exchange on a normal basis, so is I think, a red herring.
There are issues with the corruption of the storage file of passwords, but that mostly affects folk that jumped to V102 and skipped everything else after about V60. But I do not see this as probable, or the recent update might have made it into the report.
A quick look at that image file would indicate issues with the addon tbsync for the first half of the images and search for the last half, there is a single timeout issue from the POP3 module. But this could well be caused by a firewall blocking access to Thunderbird or the mail server simply ignoring the connection attempt. Clearly, the settings being used as "strange" as OAuth should not be available as an option to configure a Bellsouth or ATT mail account.
I do not see this as similar to Bug 1698316, I see it as a dup. Oauth is not available to ATT users (or should not be) using the server names published by the ISP, or returned from the ISPBD
Original Reporter here. An update. After a couple of days, I decided to give it another try. I ended up NOT needing the Secure Mail Key and OAuth protocol. I used the standard SSL/TLS Connection Security and Normal Password as the authentication method.
I am not sure why but I was able to connect to the ATT servers and now TBird is working normally for me. OAuth2 is working fine for my Google acct.
As far as I'm concerned, this can be closed.
Sorry to have cluttered things up.
|
|
||
Comment 4•3 years ago
|
||
Thanks for the update
Description
•