Mozilla will shut down Pocket’s services on July 8, 2025. At that time users will no longer be able to access the Pocket website, apps and API. You can export your saved items and API data until October 8, 2025 before they are permanently removed. For more information, see this article.

Avatar for Username

Search Support

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

This thread was archived. Please ask a new question if you need help.

Profile transfer - new comnputer can not get email.

  • 3 replies
  • 0 have this problem
  • 1 view
  • Last reply by MITCH

MITCH
MITCH
more options

I transferred my THUNDERBIRD (TB) profile from a Win 7(32bit) - to a Win 10 (64b). The new install can not get my email. I carefully and repeatedly checked every setting with both comp screens side by side.

      • Every letter, dot, and number are identical.

I can still log in with my UN/PW on the Win 7 box - and I can log in online using my PW.

Every time I try on the Win 10 box get these two errors: FIRST: Login to server inbound.att.net with username mitchg@att.net failed 

     [Retry]      [Enter New Password]     [Cancel]

THEN: "Sending of password for user mitchg@att.net did not succeed. Mail server inbound.att.net responded [sys/temp] Server error - Please try again later."

RE: "LATER" - Please note: While this is on the Win 10 box screen I can send and receive email through the same account with TB on my Win 7 box and/or the ATT server webpage interface. I have tried "later" innumerable times for 10 hours.

BTW, I have also deleted the TB pkcs11.txt file more than once. I also opened that file on the Win7 and Win 10 boxes and compared them side by side. Other than the path to the folder they are identical.

Nothing I read indicated I should delete the FireFox file of the same name so I left it alone.

Thanks very much for your help. mitch

I transferred my THUNDERBIRD (TB) profile from a Win 7(32bit) - to a Win 10 (64b). The new install can not get my email. I carefully and repeatedly checked every setting with both comp screens side by side. ***Every letter, dot, and number are identical. I can still log in with my UN/PW on the Win 7 box - and I can log in online using my PW. Every time I try on the Win 10 box get these two errors: FIRST: Login to server inbound.att.net with username mitchg@att.net failed [Retry] [Enter New Password] [Cancel] THEN: "Sending of password for user mitchg@att.net did not succeed. Mail server inbound.att.net responded [sys/temp] Server error - Please try again later." RE: "LATER" - Please note: While this is on the Win 10 box screen I can send and receive email through the same account with TB on my Win 7 box and/or the ATT server webpage interface. I have tried "later" innumerable times for 10 hours. BTW, I have also deleted the TB pkcs11.txt file more than once. I also opened that file on the Win7 and Win 10 boxes and compared them side by side. Other than the path to the folder they are identical. Nothing I read indicated I should delete the FireFox file of the same name so I left it alone. Thanks very much for your help. mitch

Chosen solution

I just started all over and used a new key. It is fixed. thnx

Read this answer in context 👍 0

All Replies (3)

sfhowes
sfhowes
  • Top 10 Contributor
more options

You have to generate a secure mail key for each computer, even if the account is the same. Create a secure key from the W10 computer, delete the entries in Saved Passwords in Settings, restart TB, enter the key when asked for a password.

https://www.att.com/support/article/dsl-high-speed/KM1010523/

MITCH
MITCH Question owner
more options

I probably should have mentioned I am not using IMAP. I am using POP. There is only one place to put in a POP password AFAIK. I did as you said but it didn't change anything. Does it matter which computer I generate the new key on?

MITCH
MITCH Question owner
more options

Chosen Solution

I just started all over and used a new key. It is fixed. thnx