huh!

You have three email accounts. Each will have it's own account and each will have it's own SMTP server. Unless you have some bizarre mail aggregation thing going on with some web mail somewhere. So please clarify

If I was clear I wouldn't be here...

There seem to be two ways to get to the Manage Certificates area. one way allows you to set a single Default. The other seems to set the one to be used by a particular user. Dunno if that is the same as "default."

But it seems that if you ever create an Account that wants to use a server different from the existing account, you have to find that 2nd access point. I don't see this in any of the documentation.

I don't see why the 1st entry point does not allow you to designate which server is used by which account, as well as designating a "default" if an account has not specified a particular server. It could be displayed visibly & clearly in the grid.

And today I broke firefox by foolishly trying the next version... that's been 5 hours of beating my head on a different wall. It won't allow me to select my "old" Profile as the Default to the re-installed "old" version. So although I was able to re install v69, I cannot link it to the Profile that has 10-15 years of information in it... Happens in about:profile & if I manually copy & paste the Profile contents to the "new" profile.

Your reply just made things worse. You talk of Manage Identities, then Manage Certificates, then you talk of Firefox while this is Thunderbird support... Consider me just as confused as you are.

I'm guessing that the 2nd access point is the solution to individualizing the account Server Name, would like some verification.

I have problems with BOTH apps at the moment. And I have to keep re-starting between the problem user account and THIS account, where I can communicate and access my files on how-to.

Any notes I make have to be drop-boxed into the other account; at least I can view both SHARED folders since both are Admin users. OSX needs a SuperUser acct type to be able to read & write any files at all.

Just ranting about the Firefox problem. Got a separate post in the FF forum.

What are these 1st and 2nd access points? Post screenshots of what you're trying to tell us. All email accounts that are setup in Thunderbird have their own individual smtp server. You literally don't need to do anything to assign an smtp server to each account. This is taken care of by default.

Access points: under OUTOING SERVER you can make any one the Default.

Clicking on the name of the user, at the bottom, "outgoing server (SMTP)" can select which to use for that user. You have to figure out that "default" means it will be used if there is nothing selected here.

Probably most people only have one internet provider, so every email account will happen to go to the same SMTP server. Not if you have a major IP, and also forwarding from the defunct Yahoo Groups, and a secure IP such as ProtonMail. Then you need to pick the correct one for each user.

Probably most people only have one internet provider, so every email account will happen to go to the same SMTP server. Not if you have a major IP, and also forwarding from the defunct Yahoo Groups, and a secure IP such as ProtonMail. Then you need to pick the correct one for each user.

Not really. Like I said, each email account gets its own smtp server when it's added to Thunderbird. The account setup process requires both incoming and outgoing server settings, so you cannot end up with an account or "user" as you put it, that doesn't have a corresponding smtp server individually assigned to it. You would have to tinker around and delete an outgoing server to end up in the situation that you're describing.

The user acct does not magically "get" an smtp server, you have to enter it correctly when you set it up. If you need a security certificate exemption, it gets weird.

Right now I have a wonky ProtonMail account, TB cannot find the server for 127.0.0.1 - even though years ago when first set up, it did. Why it stopped working when they suddenly forced a Bridge update last week, is the issue to be solved.