Closed
Bug 257540
Opened 21 years ago
Closed 19 years ago
Trash and Junk (and sometimes Inbox) wrongly claim to contain unread messages
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: reuven, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040817
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040817
I have been using Mozilla for all of my e-mail for about eight months now, and
it has worked pretty much flawlessly during that time. However, since
downloading and beginning to use Mozilla 1.8a3, I have found at least one
annoying bug: Folders often claim to contain unread messages, but don't. That
is, the folder's name is displayed in boldface and is followed by a number in
parentheses. But (a) no unread messages appear to be in the folder, (b)
pressing "n" doesn't move me to another message, and (c) deleting and/or
compacting all of the messages in the folder doesn't appear to have any effect.
This happens most often with the Junk and Trash folders, but occasionally
happens with the Inbox folder, as well.
I'm using POP to retrieve messages, and Mozilla retrieves messages every five
minutes. I have four filters on my Inbox, each of which moves new messages to a
different folder. (In one of those cases, messages are moved to the Junk folder.)
Reproducible: Always
Steps to Reproduce:
1. Open Mozilla mail.
2. Notice that there are new messages in the Junk folder.
3. Switch to the Junk folder.
4. Press "n" to move to the next new message.
Actual Results:
The message view doesn't change.
Expected Results:
If there is really a new message in the Junk folder, then the message pane
should display the next unread message.
If there isn't any new message in the Junk folder, then the folder name
shouldn't be boldfaced, and the number of unread messages shouldn't be displayed
(since it's 0).
Trash part: related to Bug 257104
other parts with filtered messages: related to Bug 116181 (and Bug 222068)
See also Bug 224823, Bug 200447.
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Comment 2•19 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 3•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•