Complete settings for AT&T/Yahoo/Bellsouth
It appears to be a combination of AT&T's latest security protocol "Security Key" and Thunderbird's release "78" that is causing issues.
We have two separate email accounts with additional identities that exhibiting the same problems. Without making any changes at the time, the identities quit receiving emails. One worked in the morning and stopped working in the afternoon, the identity in the other computer quit a couple of months ago. Now besides not receiving identity emails, neither account can send email.
The error message says sending of the password failed. I can log into both accounts and all the identities through Yahoo webmail and can send and receive emails just fine. The same is true for our email accounts on our iPhones, they never skipped a beat. One computer is win10 and the other win7 Professional.
The email is set up as "pop". What's a little different is that we have the older Bellsouth email account that is through Yahoo which is through AT&T. AT&T has been zero help with the settings.
I even hired an IT guy to have a try at it. He warned me that he has been through this before with other customers and it boils down to giving up Thunderbird, he couldn't get anywhere.
I really don't want to switch from Thunderbird, with my line of work I have a lot of folders with lots of emails I can't lose. Up to this point, Thunderbird has been great! And I really like its ease of use and functionality.
Please help! This is driving me nuts!
Thank you for your time, Dave ps. If I can get this working with confidence, I'll probably convert over to imap...
Chosen solution
OAuth2 isn't supported for the AT&T servers such as inbound.att.net. It only works with the Yahoo servers mentioned above, even though AT&T mail is provided by Yahoo. With AT&T, normal password authentication and secure mail keys is the recommended method.
Read this answer in context 👍 0All Replies (8)
Use a secure mail key for AT&T accounts:
https://support.mozilla.org/en-US/questions/1334109
https://www.att.com/support/article/dsl-high-speed/KM1010523/
If you have accounts that connect to Yahoo servers, e.g. pop.mail.yahoo.com, imap.mail.yahoo.com or smtp.mail.yahoo.com, set the authentication method to OAuth2.
Maybe I'm still doing something wrong, but that didn't work...
First, even though I'm using the security key, AT&T doesn't like the OAuth, see attached photo.
Then I was getting a server issue error, see the other attached photo.
I had to switch back to the "normal password" setting. Although the main email was working the identity wasn't.
I had security keys for both accounts, I pasted the identity security key into the "saved passwords", which got it to download 300+ emails :-)
It asked for a password went trying to send an email, pasted the identity security key and the test email sent.
Not sure if it's really fixed, but I know for sure the OAuth setting doesn't work for whatever reason...
Thank you,
Dave
Chosen Solution
OAuth2 isn't supported for the AT&T servers such as inbound.att.net. It only works with the Yahoo servers mentioned above, even though AT&T mail is provided by Yahoo. With AT&T, normal password authentication and secure mail keys is the recommended method.
I've got the email on one computer running as it was before.
The questions are: How stable is this configuration? Is there a better configuration that is more stable???
Thank you for all the help!
Off to tackle the other computer...
Dave
The normal authentication/secure mail key setup is the current recommendation for AT&T, and I haven't seen any reports that it's unstable - or any less stable than anything else in the computer world.
Thanks, sfhowes. I tried various setting such as "autodetect", "STARTTLS", "SSL/TLS" and "None", for the SSL settings on both in-going and out-going sides, and "autodetect", "Normal PSW", "Encrypted PSW" for Authentication, nothing gets past that error message. Anything else I might try? Thanks, Andy
holroydsills1 said
Thanks, sfhowes. I tried various setting such as "autodetect", "STARTTLS", "SSL/TLS" and "None", for the SSL settings on both in-going and out-going sides, and "autodetect", "Normal PSW", "Encrypted PSW" for Authentication, nothing gets past that error message. Anything else I might try? Thanks, Andy
No need to guess for AT&T - use the settings here and use a secure mail key in place of the account password. Ports 993, 995 or 465 use SSL/TLS, and all servers use normal password authentication.
Thanks you sfhowes. I went to AT&T, got a secure key, entered it in the password section... BINGO!! -bobam1