Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Can't access AT&T/Yahoo email through Thunderbird since 4-21-2021. Anyone know what's going on?

  • 8 replies
  • 1 has this problem
  • 103 views
  • Last reply by j.erbes

AT&t/Yahoo email quit on me on April 22. All I get for every account is: "Sending of password for user ****@att.net did not succeed. Mail server inbound.att.net responded: Server error - Please try again later.

I can, however, log into "Currently, from AT&T|Yahoo! Mail", (also known as mail.yahoo.com), and my emails are there and everything is working just fine.

Stuff I've tried so far: 1. Chatting with AT&T. Chatted with 5 different service techs for an hour before "David-Supervisor" said "Thank you for waiting, I talked to our technical team and we are having system upgrade for email access using email app which Thunderbird is affected by the update. For now, you can access your email via browser while we are working on the 3rd party apps." "Me: How much longer until the system is up again?" "David-Supervisor: There is no ETR specific time yet, but you can try again tomorrow."

I've been trying for the past four "tomorrows" with no luck.

2. Tried switching from POP inbound.att.net, to IMAP imap.mail.yahoo.com 993 SSL. That doesn't work either.

AT&t/Yahoo email quit on me on April 22. All I get for every account is: "Sending of password for user ****@att.net did not succeed. Mail server inbound.att.net responded: Server error - Please try again later.'' I can, however, log into "Currently, from AT&T|Yahoo! Mail", (also known as mail.yahoo.com), and my emails are there and everything is working just fine. Stuff I've tried so far: 1. Chatting with AT&T. Chatted with 5 different service techs for an hour before "David-Supervisor" said "Thank you for waiting, I talked to our technical team and we are having system upgrade for email access using email app which Thunderbird is affected by the update. For now, you can access your email via browser while we are working on the 3rd party apps." "Me: How much longer until the system is up again?" "David-Supervisor: There is no ETR specific time yet, but you can try again tomorrow." I've been trying for the past four "tomorrows" with no luck. 2. Tried switching from POP inbound.att.net, to IMAP imap.mail.yahoo.com 993 SSL. That doesn't work either.

Chosen solution

When you tried the yahoo server did you try changing the authentication to oAuth? that should do it I think.

Read this answer in context 👍 1

All Replies (8)

3. I tried the "secure mail key" thing too. That doesn't work either.

Chosen Solution

When you tried the yahoo server did you try changing the authentication to oAuth? that should do it I think.

Matt said

When you tried the yahoo server did you try changing the authentication to oAuth? that should do it I think.

Thanks, Matt. I gave OAuth2 a try, and it looks like that has fixed it and I can now receive emails in TB.

Also, it doesn't look like I need to use a secure mail key, at least for now. Maybe in the future.

Modified by j.erbes

New accounts are not required to be set up... just change the server name, click ok and open the edit dialog again to have the list refresh with the server name restricted oAuth option.

Securemailkeys are an alternative to oAuth, so if oAuth works for you you do not need a secure mailkey.

Matt said

New accounts are not required to be set up... just change the server name, click OK and open the edit dialog again to have the list refresh with the server name restricted oAuth option.

I don't seem to be able to do it that way. When I go to Server Settings for for the old POP account, it shows my server type as POP Mail Server, with no apparent way to change it over to IMAP.

I can enter in imap.mail.yahoo.com 993 for the server name and port and I can change authentication to OAuth2, but I don't see any "OK" to click, and when I go back and "Get Messages" with the server changed to imap, I get the TB error message "An error occurred with the POP3 mail server."

This TB Forum article https://support.mozilla.org/en-US/kb/switch-pop-imap-account says that the POP account needs to be disabled, new IMAP account created, files transferred over, and then the old POP account deleted.

I don't think you can directly change a POP account to IMAP. What am I missing here?

Modified by j.erbes

Matt said

New accounts are not required to be set up... just change the server name, click OK and open the edit dialog again to have the list refresh with the server name restricted oAuth option.

I don't seem to be able to do it that way. When I go to Server Settings for for the old POP account, it shows my server type as POP Mail Server, with no apparent way to change it over to IMAP.

I can enter in imap.mail.yahoo.com 993 for the server name and port and I can change authentication to OAuth2, but I don't see any "OK" to click, and when I go back and "Get Messages" with the server changed to imap, I get the TB error message "An error occurred with the POP3 mail server."

This TB Forum article https://support.mozilla.org/en-US/kb/switch-pop-imap-account says that the POP account needs to be disabled, new IMAP account created, files transferred over, and then the old POP account deleted.

I don't think you can directly change a POP account to IMAP. What am I missing here?

The talk I had is about using oAuth. not changing from imap to POP or vise versa.

The server for pop accounts is pop.mail.yahoo.com port 995

The server for an IMAP account is imap.mail.yahoo.com port 993

oAuth is available on both servers so is available for POP and IMAP.

The settings Thunderbird ises for yahoo accounts are stored here https://autoconfig.thunderbird.net/v1.1/yahoo.com

OK, it looks like we weren't on the same page. I was under the impression, after talking with AT&T for an hour, that any AT&T POP server accounts would need to be changed to Yahoo IMAP server accounts. Apparently, this is not true.

I went back to my old POP account (using the inbound.att.net server) and changed authentication to OAuth2. Everything works just fine with that POP account using OAuth2.

So, apparently OAuth is available for the old inbound.att.net servers as well.

When AT&T was trying unsuccessfully to help me, their fix was to set up a secure mail key. That definitely did not work. I don't know why they didn't suggest OAuth.