95510 - Total/Unread column not updated for deleting msgs/getting new msgs

Status: VERIFIED WORKSFORME

(SeaMonkey :: MailNews: Message Display, defect)

Description

[sairuh (rarely reading bugmail)]

noticed this using 2001.08.15.08-comm bits on linux. after i read and delete the
contents of a mail folder, the Total column still displays a numeric value even
though it should be blank [zero].

i happen to be seeing this with a folder that receives filtered email, but not
sure if that'd be the cause. [in my case, it's my bugmail folder.] it reminds me
of bug 94329 --except that marking all read doesn't clear it up. nor does
exiting/restarting mail.

i'll attach a screenshot soon.

1. go to a folder that has new/unread messages.
2. read the messages.
3. delete the messages.
4. empty the Trash.

expected result: the Total count should go blank [zero].

actual result: non-zero value for Total remains.

Comment 1

[sairuh (rarely reading bugmail)]

Attachment: incorrect Total count for bugmail folder after msgs deleted

Comment 2

[Simon Young]

Also occurs under win32 build 2001081703 with my IMAP account. I also had some
trouble with getting an accurate "new messages" total. I reset this through
message->mark->all as read and have not had the problem since.

Comment 3

[Keyser Sose]

*** Bug 96090 has been marked as a duplicate of this bug. ***

Comment 4

[Karen Huang]

Updating the summary to include all related scenarios (include bug 96090)

message counters fail to update

Cause:
1) Delete all messages out of a folder.
2) Receive mail filtered to that folder.

Produced result: Unread and total message count are blank.
Expected result: They should have the correct numbers.

Work around:
1) Close mailnews.
2) Open mailnews.

Comment 5

[Sheela Ravindran]

*** Bug 98817 has been marked as a duplicate of this bug. ***

Comment 6

[Benjamin Mucci]

Same on Mac -> Should be All/All

Comment 7

[(not reading, please use [e-mail] instead)]

I believe this has gotten fixed along the way, as with 121660

sarah or laurel, can you verify?

this was a valid bug at point, but since I didn't do anything to fix it, I'm 
going to mark it works for me.

Comment 8

[sairuh (rarely reading bugmail)]

i no longer see this problem, at least as i had originally reported.

vrfy'd wfm. do reopen if there is [are] a particular scenario that exhibits this
issue, however.