295667 - The list views a lot of unread mesages for one acount but there are just a few, the total number of messages are also wrong.

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[Martin Johansson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.7.6) Gecko/20050318 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.7.6) Gecko/20050318 Firefox/1.0.2

The number of unread messages in the list is far far to high. Like 70 000 but
there are only like 20 unread messages. 
The same problem with the total number of messages, thunderbird says 950 000 but
there are like 100.
see 
http://www.gunnang.se/thunderbird.gif

Reproducible: Always

Steps to Reproduce:
1.Open thunderbird
2.It's allways wrong for one specific acount
3.



Expected Results:  
It should displayed correct number of messages.

Comment 1

[Dra Jenic Rycr]

I have the same problem. When opening thunderbird it says the total number of
unread messages is 294 when I click view unread messages there is only 10
displayed. It also says that the total number of emails in the inbox is 24,000
something. That is clearly not the correct number and after tweaking things
(marking all unread to read and switching folders then returning to inbox)
everything is back to normal. 764 is the real number of messages in the inbox
but as soon as I get a few more unread ones the problem starts all over again. I
am running Windows XP Professional with Thunderbird 1.0.6. (however this same
bug was also in 1.0 when I then upgraded thinking it was the old version) I also
run Ubuntu Linux 5.04 and so far I have not encountered this problem with it
however to be fair that system only has about 100 messages (perhaps less)
whereas this system has much more. 

Comment 2

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur with the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported Thunderbird version 2 is 2.0.0.16)

Comment 3

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to the last question. If you feel this change was made in error, please respond to this bug with your reasons why.