222891 - The first message in thread indicates that one of the childmessages is unread but that's not the case.

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: POP, defect)

Description

[Martin Bagge / brother]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007

When I downloaded my mails this night I was out of HDD space and Moz started
complaining that it couldn't move junkmails but that's not the issue. As you can
see in the URL I have an uread message in a thread, or have I? When the messages
ar sorted by Thread it indicates one unread message, when they are sorted in any
other type (sender, date or subject) it doesn't indicate any unread messages. 

The folderlist says nothing about the unread messages, the statusbar says 0
unread. When I move the thread to another folder it says all read (or nothing
but that's the same thing) but when moved back to the original folder (which
isn't the inbox but the messages are placed there using filters) the
unreadindicator shows up again. Even after I have turned Moz off and started it
back again, I haven't tried to move them out of the folder and then turned Moz
off and then started and moved them back but I can sure do.

Reproducible: Couldn't Reproduce

Steps to Reproduce:



Expected Results:  
It shouldn't displayed any ureadindicator nor the number for unradmessages
because I have read all the messages.

Comment 1

[Gervase Markham [:gerv]]

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 2

[Gervase Markham [:gerv]]

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.