547110 - TB 8.0: New Mail Alert Message count incorrect (negative number); "-809844506" New Messages.

Status: NEW

(MailNews Core :: Database, defect)

Description

[mad.engineer]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1

TB 3.0.1 on Windows XP with IMAP setup. Starting today, the New Mail Alert pop-up window showed that I have "32582824" new messages. This is incorrect. This even showed up after compacting all folders. I only have 181 total messages in my InBox.

See attached screen shot.

Reproducible: Sometimes

Actual Results:  
See attached screen shot.


See attached screen shot.

Comment 1

[mad.engineer]

Attachment: Incorrect count

Comment 2

[Nathan Tuggy (:tuggyne)]

What happens if you re-index (right-click the folder in question, choose Properties, click the Rebuild Index button)?

Moving to MailNews Core on the assumption that it has something to do with the MSF files.

Comment 3

[mad.engineer]

Which specific folder I need to re-index?. The New Mail Alert pop-up do not say specifically which folder have this "x" number of new messages. All it says that "Account ABC has XX new messages". So, this makes the alerting window pretty much useless IMHO. I have my IMAP InBox and about 10-12 IMAP sub-folders within this main InBox. So, not knowing which folder to re-index makes it odd.

As for something related to MSF files, I found while searching the mozilla support forums a suggestion to delete all MSF files from the profile folder. All that did for me was to mess up my TB customization like message windows, columns that I've enabled on a per folder basis etc. It did not fix the issue.

If you can tell me any way to just make TB not show the "count" of new messages in the New Mail Alert pop-up, I'd be happy instead.

Comment 4

[mad.engineer]

Forgot to add earlier that I use TB for my work email, therefore I can't afford to "experiment" anything that would in turn break TB functionality or loose my mails.

Comment 5

[mad.engineer]

I tried doing re-build index and as mentioned all it did was mess up my folder view customization like column settings etc.

Comment 6

[mad.engineer]

I went through and re-build the index as you suggested. Now I don't get the message count as "32582824", but still the count is not accurate as I would expect it to be. Before I re-built the index I noticed that in my Profile->ImapMail folder I had two of each type of files. As an example, say IMAPFolder and IMAPFolder.msf. The re-build process removed all but the .MSF files. Is this normal?

Comment 7

[Nathan Tuggy (:tuggyne)]

(In reply to comment #6)
> The re-build process removed all but the .MSF files. Is this normal?

All *but* the .MSF files, or all the .MSF files? I would not expect it to remove the files with no extension.

Comment 8

[mad.engineer]

I'm attaching the screen shots here for clarity. As you can see in the Before_re-Index screen capture, that in my Profile->ImapMail folder, I've a whole bunch of IMAP folders, beside my InBox. The screen shot only show on IMAP folder as an example. You'll notice that there are two files with the same name. One with Zero Kb size, no extension and the other which is a .MSF file with the same name of 3Kb size.

I then launch TB, select this IMAP folder from the tree, right-mouse click->Properties and click on Re-build Index. This looses my customization for this particular layout like the columns that I've enabled/disabled to see.

I then go back to the same Profile folder. Now I only see the .MSF file with size 3Kb. The other file with the same name and no extension and size Zero Kb is gone. See the screen shot, after_re_index for this.

If I have to re-build the index to fix this issue frequently, I'd rather move back to my old email client.

Comment 9

[mad.engineer]

Attachment: Before IMAP folder re-index

Comment 10

[mad.engineer]

Attachment: After re-index

Comment 11

[David :Bienvenu]

Have you tried 3.02? http://ftp.mozilla.org/pub/thunderbird/nightly/3.0.2-candidates/build1/

Comment 12

[mad.engineer]

Not yet, but I will upgrade once 3.0.2 becomes officially available on 2/24

Comment 13

[mad.engineer]

I upgraded to 3.0.2 earlier and today I ran into the same issue that I reported in this bug. The New Mail Alert pop-up window all of a sudden indicated that I have a very high number (52582824) of message in my IMAP InBox. I had to re-build the Index to temp fix this issue. This to me is a bug with TB and must be fixed. Re-building on an on going basis is a poor workaround.

Comment 14

[mad.engineer]

Upgraded to TB 3.1 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1) and seeing the same problem again. TB is telling me that I have "100961185" New Messages, whereas when I check all my IMAP folders, I only see 3 new messages.

Comment 15

[mad.engineer]

Attachment: TB 3.1 showing incorrect new message count

Comment 16

[mad.engineer]

Upgraded to TB 8.0 earlier, compacted all folders. Now the new mail count show as a negative number. Is show "-809844506 new messages" !

Comment 17

[Wayne Mery (:wsmwk)]

Still see this problem when using a current version?

Comment 18

[Silas Parker]

I still see this on Thunderbird 52.9.1 64 bit on Fedora 28.

Comment 19

[Silas Parker]

Attachment: Screenshot from Thunderbird 52.9.1

Comment 20

[Phoenix]

What about Thunderbird 60.0?

Comment 21

[Silas Parker]

I've just managed to trigger it on TB 60.0 (64 bit) on Fedora 28 (RPM thunderbird-60.0-1.fc28.x86_64). It seems to be related to compacting the mailboxes.

I compacted all the mailboxes (using the Xpunge plugin), then when the next mail arrived, it had the message "received 1566318273 new messages".

I'm not sure if it's related, but in the error console there's a log line:
uncaught exception: 2147746065  autosync.js:206:13
Which is line: this.activityMgr.removeActivity(process.id);

Comment 22

[Wayne Mery (:wsmwk)]

Confirming based on two reports, but I don't see this myself, 

(The autosync exception is sort of "normal" and may be ignored.)