No Prompt For Password. Then "Connection to server inbound.att.net timed out"
Thunderbird Version 140.7.1esr, Build ID 20260123195141 User Agent Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 OS Linux 6.1.0-33-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.133-1 (2025-04-10) OS Theme Xfce / Adwaita Application Binary /usr/lib/thunderbird/thunderbird-bin
Having a problem with an ATT POP account. TB stopped getting mail. After a minute and a half or so (wish it would time-out faster), I get a pop-up box in the top right of the screen that states: "Connection to server inbound.att.net timed out" and then quickly goes away.
Deleted passwords and cannot see where to create them again, as it never prompts me for new ones.
Thanks.
Moambuepyre
Opaite Mbohovái (9)
Are you using a secure mail key in TB in place of the account password?
https://www.att.com/support/article/dsl-high-speed/KM1010523/
How can I tell?
If the entry in Saved Passwords is the account password, it's not a secure key. Create a secure key on the AT&T site and use that instead of the account password.
In either case, where are those entered (since there is no prompt)?
If there's already an entry in Saved Passwords, right-click, Edit. Or, delete it, restart TB, enter the key when prompted.
This for 'normal password' authentication. I think OAuth2 authentication might be supported for AT&T in TB 140, in which case enter the account password in the OAuth window when prompted.
"If there's already an entry in Saved Passwords,........"
That is the whole point. Please read first post, where it states: "Deleted passwords and cannot see where to create them again, as it never prompts me for new ones."
What is the authentication method on the incoming and outgoing? Confirm that before trying to figure out why you aren't prompted. I'm assuming there is no VPN or security software in your setup. Also, confirm your other server settings are as in the support article.
All confirmed. But please give reasoning for comments.
The reason? To eliminate the possibility the issue is caused by a simple factor such as an incorrect setting or an interfering external app. Is your current profile one that has been used in many earlier versions of TB? Sometimes the presence of an obsolete file can cause passwords to malfunction. Adding the account to a new profile is one way to test.