搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Thunderbird Tray Icon Says I Have 4 Billion Unread Messages

  • 3 个回答
  • 1 人有此问题
  • 4 次查看
  • 最后回复者为 craigsteeland

more options

Windows 10. Thunderbird 115.8.0 While trying to figure out why my taskbar badge says I have 99+ unread emails (for the record, I only have 7), I hovered over the tray icon, and it says I have over 4 billion (with a B!) unread emails. That's not even possible with the email address I'm using it for. Why would this be like this, and how do I get it to be accurate?

Windows 10. Thunderbird 115.8.0 While trying to figure out why my taskbar badge says I have 99+ unread emails (for the record, I only have 7), I hovered over the tray icon, and it says I have over 4 billion (with a B!) unread emails. That's not even possible with the email address I'm using it for. Why would this be like this, and how do I get it to be accurate?
已附加屏幕截图

所有回复 (3)

more options

I do not remember having a start menu or desktop in Windows that looked anything like what you have in that image. How do I go about making it the same so I can reproduce your process?

more options

Well I cropped that original shot to only show the notification popup from the tray. But I use Rainmeter to customize my desktop. Here's a second screenshot that shows my taskbar (and the 99+ badge), along with the popup that has the over 4 billion emails.

more options

I also have this problem. All of my efforts to come up with replication steps have failed. Restarting Thunderbird temporarily fixes the problem, but it soon returns. I thought it might be a synchronisation problem resulting from accessing my emails on a different device, but that doesn't seem to be the case.

The number 4,294,967,295 is a whole number equal to 2 to the 32nd power − 1. See: https://en.wikipedia.org/wiki/4,294,967,295

This may or may not provide a clue to what is going on. Apparently some Outlook users also have this problem.

This is completely baffling and frustrating. Has this bug ever been reported so that Mozilla coders can have a look?