User Agent: Mozilla/5.0 (Windows NT 6.1; rv:102.0) Gecko/20100101 Firefox/102.0

Steps to reproduce:

In an attempt to minimize unwanted duplicate emails (different bug), I turned off (unchecked) all settings for "include this server when getting new mail" for all accounts -- except for one specific to this device. I clilcked GET MESSAGES to test, and only this device-specific account was polled -- correct and as expected. Then I went on to other things, presuming that no emails would come down unless & until I manually polled specific account(s).

Later, after messages had leaked through, I relaunched TB to ensure that the current ("unchecked") settings would be loaded (and presumably heeded).

Actual results:

Out of the blue, an email came down. Later, a whole bunch of Bugzilla notices came in unobserved from its specific account. And perhaps one or two more. I confirmed that the "include" settings had not changed or reverted -- they were still UNCHECKED.

After relaunching TB (to ensure settings were actually read), I noticed more emails came down uninvited.

Expected results:

TB should pay attention to its settings and not run wild. Only accounts set to-be-included should be included in the mail fetches.

I have several accounts unchecked and they have never gotten polled, so I know the process and how it works. Most of these accounts are low traffic, so there is likely nothing there to fetch right now anyway -- all messages would have expired (beyond the "leave for so-many days"). But at least one account (at GMAIL) fails because of log-in issues and it is quite obvious when it does -- yet this account hasn't popped up any errors, so its setting must be working. (Or TB is smart enough to bypass it.)

In the STR, "out of the blue" happened while I was active at the keyboard. TB was running in its own window as usual when it decided to pull down some mail. At the time it didn't quite register with me what had happened -- looked so normal -- but of course mail came in (and notice popped up), contrary to the settings. Later, unattended, the machine went to sleep. When awakened, within seconds TB started polling -- as it usually does under normal circumstances -- and immediately two more messages came down.

So now I know for sure that the automatic/timed GET MESSAGES process is alive and working -- and misbehaving by fetching messages when it shouldn't -- whereas the manual GET MESSAGES seems to behave and polls only the one account which is set for it (see "device-specific account" in the STR).

There is a "Check for new messages every _ minutes" setting for each server, did you uncheck that as well?

No I did not, but I notice that the accounts which worked correctly in fact did have this unchecked as well. I'll uncheck them all.

Perfectly clear in hindsight: "Include when getting new mail" means literally include in the GET MESSAGES button and not in the automatic/timed fetches. The "Check every..." is specifically for the timed fetches. Duh!

Perhaps the wording should be changed slightly to say something like "Include this server when getting new messages", which sounds more like when the buttom is used. Getting new mail could be -- and obviously has been -- taken both ways. (I now recall tripping over this in the past...)

Thanks!