TB 102.7.0: seems like multiple accounts on same SMTP server just broke
Thunderbird 102.7.0, 64-bit, Windows 10.
I just fell over this today but it may have been around for a while.
I have lots of email accounts. It was great when TB starting properly supporting a per-account (outbound) SMTP server, however, this seems to have newly broken. I fell over it today, but I don't reboot things for ages so I cannot pinpoint the start.
Here's the issue.
I have accounts on many mail servers, many on the same (mainly att.net, and gmail.com, as it happens).
Each one of them, to send mail, wants me to log in with an individual sending address. Fair enough. This used to work just fine.
However, suddenly, just the att.net addresses are broken. What *seems* to be happening is that the same, single login address is being used for all N accounts. Naturally, this breaks when the login address doesn't match the one on the From: line. So I have to futz around, fiddle around, and so on, and then things work. (I.E. I change the TB settings so that the outbound SMTP auth login matches the From: line, have to re-enter the password, and only then will the message be sent.) So if I have two accounts, x@att.net and y@att.net, only one of them (at a time) "works" with att.net - it's whatever I successfully used last. If I sent mail from x@, this address is being used (and it's in the account settings field. over-riding what was there before), even if I send mail from y@. Or z@. Etc. If I change the SMTP auth address to y@, then that account works perfectly, but x@ doesn't. And so on.
Now the weird part is this: my Gmail addresses still work perfectly. I can send from all of them without changing a thing.
The only thing I can see is that Gmail is set up to use oAuth, and att.net is set up to use 'normal password' (via SSL, so I'm not that bothered about security).
Did I unknowingly manage to break something? Is there a new tweak? Help!
Jonathan
Chosen solution
If you have each account sending through an smtp with a matching User Name (email address), then it should only be necessary to enter the password once if the passwords are saved in the password manager (Saved Passwords in Settings). With AT&T accounts using *.att.net servers, you must use a secure mail key in place of the account password in TB.
I suggest you make sure the accounts are pointing to the correct smtp servers:
https://support.mozilla.org/en-US/questions/1350593
remove the incoming and outgoing passwords for the AT&T accounts in Saved Passwords, restart TB, and enter the key for each account when asked for a password.
Read this answer in context 👍 0All Replies (2)
Chosen Solution
If you have each account sending through an smtp with a matching User Name (email address), then it should only be necessary to enter the password once if the passwords are saved in the password manager (Saved Passwords in Settings). With AT&T accounts using *.att.net servers, you must use a secure mail key in place of the account password in TB.
I suggest you make sure the accounts are pointing to the correct smtp servers:
https://support.mozilla.org/en-US/questions/1350593
remove the incoming and outgoing passwords for the AT&T accounts in Saved Passwords, restart TB, and enter the key for each account when asked for a password.
Thank you. Your solution (remove existing passwords, restart TB, re-enter passwords) worked like a charm. I also renamed (the nicknames, not the DNSnames) for the SMTP server on each account, to try and get some separation. No idea if this helped. Then I restarted.
I did notice one thing: I first entered the new password for a@; when I then looked at the account details (having done nothing else except send some test emails) I found that the SMTP server for b@ had gotten over-written with the SMTP info for a@. I changed this back manually, entered the correct password for b@, and things continued working as desired as they have done for months, maybe years.
I have no idea how things got messed up this way. I might guess that it was something to do with a TB reboot (or one of those damn Microsoft-forced reboots, same effect) triggering a TB upgrade which didn't quite go right. The only other thing I recall, in the hope that it's helpful, was that at (roughly, but I'm going to go with) the same time, the Composition option on one account only (the one giving trouble) had somehow changed from 'plaintext' to 'HTML'. Again, no idea how or why. I include this datum in the faint hope of helping someone track down some root cause.
Thanks again for the prompt response and the fix! If I can give any more info, please LMK.
Jonathan
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.