Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Inaccurate Unread Message Counts

  • 4 odgovori
  • 0 ima ovaj problem
  • 3 views
  • Posljednji odgovor poslao seth_goldman

more options

The Thunderbird icon is always badged with 99+ unread emails regardless of the true number. My inbox sometimes displays the right number but sometimes shows a random number in the mid 30's. Restarting TB temporarily resets the values but the bad and inbox counts go wrong again after a few minutes. I think this started with the 115 update.

With both of these issues, I can't see when I actually have unread mail. Any advice on how I can fix this?

TB = 115.3.1 M1 Mac with Ventura 13.6. Owl for Exchange plugin to get mail from MS Outlook.

thanks

The Thunderbird icon is always badged with 99+ unread emails regardless of the true number. My inbox sometimes displays the right number but sometimes shows a random number in the mid 30's. Restarting TB temporarily resets the values but the bad and inbox counts go wrong again after a few minutes. I think this started with the 115 update. With both of these issues, I can't see when I actually have unread mail. Any advice on how I can fix this? TB = 115.3.1 M1 Mac with Ventura 13.6. Owl for Exchange plugin to get mail from MS Outlook. thanks

All Replies (4)

more options

What do you have for App Icon Options in Settings/General/Incoming Mail? If it's Count of new, change it to Count of unread.

more options

I checked and the App Icon is already set to "count of unread". I also looked at the console and there are a bunch of errors of complaining about the server being unavailable. All of them mention Owl for Exchange but it's not clear whether the would have anything to do with my issue.

thanks,

more options

You could test that by temporarily disabling Owl, if you have other accounts. If it turns out Owl causes the issue, you would have to contact the Owl developer. It seems something like this has happened before.

more options

Thanks, I'll follow up with Owl and see if I can sort it out.