POP Problems with AT@T Servers - inbound.att.net and outbound.att.net
I simply changed my AT@T password this morning using the AT@T WEB. I normally use THUNDERBIRD to send/receive email.
Ever since that change, I have not been able to send/receive any emails using THUNDERBIRD.
I am pretty sure I have not changed any of the various POP settings in the THUNDERBIRD application.
When I try and get emails using TB, I keep getting a message saying that inbound.att.net server failed--try again later. This has been going on for close to 7 hours now.
I also cannot send any messages using TB since changing my password. I am able to login to my AT@T account -- so I know the password change took place.
HELP
All Replies (5)
Did you delete the old passwords in Options/Security/Passwords/Saved Passwords, restart TB, and enter the new password when prompted?
A 'secure mail key' is recommended in place of the regular account password:
Actually, this DID and DID not solve my problem.
Thru most of the day, I have tried using the PW that I changed in the early morning.
I did not save the password.
However, I did use the secure email password in TB and all worked fine.
Any explanations as to why the changed password gets hung up.
THX for the HELP!!!!!
The changed password probably didn't work because the policy now is that only mail keys are accepted. Not that that would have necessarily been explained on the password-change site.
Well, by using the secure email key from AT@T as my password, I am able to get TB to work again.
One question-->when setting up the secure email key in AT@T, it's possible to assign a nickname to the key. I tired this and put the nickname into the password dialog box, but it doesn't seem to work.
Any Clues?
PS--thanks for all the help---sure got me back to where I can use TB again.
I think the nickname is purely for organizing keys in the webmail access of your account. TB has no knowledge of the connection between nicknames and the actual key that is sent to the mail server.