App Icon Showing new messages
I am currently using Thunderbird 140.6.0esr (64-bit). Operating system is Windows10, my computer doesn't meet Windows11 requirements.
I use Thunderbird to receive messages from both my Orange.fr and Gmail.com accounts. I use the Message Filters tool on both accounts to sort the incoming messages into different folders to make it easier to follow threads. I have Thunderbird running in the background all the time that my computer is active.
The Thunderbird Icon on the taskbar is set to show new messages. It used to show the total of all incoming messages, but now (I think just since the latest update) it only shows those new messages that have remained in the main inbox of either account, any messages that have been sorted into sub-folders are not included in the number shown on the icon. This means that when I have been away from the computer leaving Thunderbird running I now have to enter Thunderbird to see if any new messages have been sorted rather than just glancing at the taskbar.
What setting have I missed or is this a "bug".
More an annoyance than big issue. Thanks in advance for any guidance you can provide.
John Shelley
redacted@orange.fr
由Wayne Mery于修改
所有回复 (4)
I don't recall the icon showing all messages; the options are for either unread or new. Possibly, you had an addon that did that?
Thanks for your response David. I don't recall ever having installed an addon that did that, in any case if I did then it should still be operational, unless something deleted it without my agreement.
John S
Well, I only keep prior versions back to ver 91, and it has same options as 140: new or unread. And thunderbird would never remove addons.
Once again thank you for your input David.
My view of what happened previously, icon showing the number of all new messages, and what happens now, icon only showing the number of the new messages remaining in the main inbox, when messages are automatically sorted before being read is that they are different, why I don't know, but as nobody else is reporting seeing this it must be down to something in my computer.
It seems to me that the change within version 140 has caused the change in the display rather than a change to version 140. Unless someone else reports the same problem don't waste any more term on it, my thanks for what you have already done. It looks like I'll just have to live with the current version (140.6.0esr ).
John S