User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 Sometimes when I go into one of my newsgroups new messages are downloaded with new subjects appearing at the top of my message list when they are supposed to appear at the bottom of my message list. This is not for new posts to a current thread - just to new subjects. If I close the mail application and open it again the messages that were previously shown at the top of the mail window now are correctly displayed at the bottom of the mail window. This appears to only occur in News section of the mail component. It also only appears to occur occassionaly. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3.

win32 trunk build 2003022308, w2k Sounds like a sorting problem that has been in existence from the beginning. There are several mail-news sorting bugs still open, I never did figure out if this was already part of an existing bug or not, but I don't know that this has ever been explicitly addressed: After a Mark All Read on a group with View Threaded/Threads With Unread, the top-level thread order apparently gets rearranged by date/time order of new posts. This creates what looks like a totally random order of top-level messages, new threads often end up at the top of the threadpane list instead of at the bottom. 1. Threaded View, Threads With Unread (default sort date ascending) 2. Pick the group in the folderpane, download headers 3. Read (selected) messages as seen fit, may or may not Kill any threads 4. Mark All Read 5. Leave that group (go to another group, switch to mail, or whatever) 6. After new messages are posted to the group in #2, return to that group (can collapse/expand the news server in the folderpane to check message count if need be) The top-level thread order is no longer in default ascending date order. The threads are now apparently in ascending date/time order of the _new_ posts, that is, the first thread listed has the oldest unread post (or something like that). This is often a new thread, so it can look like the top-level sort has switched to descending, but it more often looks random instead. After new headers are downloaded, clicking the Thread icon in the threadpane column header twice, or switching to another group and immediately returning to the problem group magically puts the threads in the correct ascending date/time order of top-level post. The only exception may be when new posts are received in between switching from/to the problem group. Is this, or some variation, what you are seeing?

Reporter, do you still see this problem with the latest nightly (or even 1.7.3)? If not, this bug has probably been fixed and can be closed. Thanks.

No bug / patch specified as the fix. -> WORKSFORME