181101 - Inbox reports phantom unread messages, but msg cannot be found

Status: RESOLVED DUPLICATE of bug 172815

(SeaMonkey :: MailNews: Message Display, defect)

Description

[John Peacock]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021118
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021118

Somehow I got a phantom message stuck in my Inbox which I could no clear.  My
Inbox always reported 1 unread message, but clicking the Next button merely
focused the message list window (top right) but did not select any message. 
Compacting the Inbox had no effect.  This is exactly what the old Netscape
"Update Message Counts" used to fix.

I did upgrade from 1.2b to 1.3a with new binary directory but the same user
profile.  Deleting the Inbox.msf and restarting Mozilla correctly rebuilt the
Inbox listing.  I cannot qualify this as a minor bug w/workaround, since the
user should not have to delete this file manually.  It seems like a menu item to
force a rebuild of the .msf file would be helpful.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[David :Bienvenu]

does mark all read clear the unread count? Are you using IMAP or POP3? If you
have any idea how to reproduce this, that would be great. As it is, we have no
idea how to recreate it.

Comment 2

[John Peacock]

I realize that the report is kind of sketchy, since I have already fixed it the
hard way (deleting the INBOX.msf).  If it happens again, I will dupe the .msf
files and try the Mark All Read trick.  I am using IMAP, though I doubt that
matters (as I said the mailbox was fine from another client).

Comment 3

[David :Bienvenu]

I suspect it does have to do with IMAP. Do you ever run two imap clients against
the same inbox, simultaneously? 

Comment 4

[John Peacock]

Hmmm, I think I did bring up Netscape 4.79 at the time as Mozilla (I was trying
to look at the way the IMAP displays out corp address book differently).  I
wonder if a rule fired in the Netscape client and moved a message, but only
after Mozilla noticed the message was there but hadn't moved the message yet.  

I realize that I do still have the old INBOX.msf file; would that be helpful?

Comment 5

[David :Bienvenu]

great, that's two people who've had this problem that had a second client
running, so that must be involved. No, I don't think your INBOX.msf file will
help (but I'm not sure yet so please don't throw it away!).

Comment 6

[David :Bienvenu]

so, there's a small chance I may have fixed this on 11/16 while fixing another
bug. Did this bug happen when you were running 1.2b, and then you upgraded to
1.3a and it didn't fix the problem? Or did it happen after you upgraded to 1.3a?

Also, do you have any filters that mark messages read?

Comment 7

[John Peacock]

Just FYI - it just happened again and I didn't have two IMAP clients running at
the same time.  I was able to clear the phantom message by using
Message/Mark/All Read.  

Also FYI, I am now running:
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021122

One additional datapoint is that at the same time I had an annoying message
which always looks New (i.e. I can read it and the next time MailNews checks for
new messages, this message is again highlighted as New).  The messages which
exhibit this behavior _always_ have an attachment.  This is long time thing
which may be actually due to our IMAP server (since I see no one has reported
anything like this except for POP servers).

Comment 8

[David :Bienvenu]

there was an existing bug about imap mail with attachments causing this problem
that was fixed. Perhaps your case is another manifestation of the bug. If
possible, could you forward me the annoying message?

Comment 9

[John Peacock]

Actually, there is nothing specific about the message/file.  It is always the
last message in the mailbox (even if it would be sorted somewhere else, i.e.
sort by thread).  Once another message comes in without an attachment to occupy
that last slot, the problem goes away.  This is nothing except a minor
annoyance, so I haven't been bothered enough to report it.

Comment 10

[Daniel Wang]

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

Comment 11

[Daniel Wang]

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

Comment 12

[Daniel Wang]

*** This bug has been marked as a duplicate of 172815 ***