User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030507 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030507 sometimes messages are sorted under incorrect parents. I get things like: msg1 -msg2 when I expect msg1 msg2 (there is no relation betwxeen the messages). Reproducible: Sometimes Steps to Reproduce: 1.download messages Actual Results: the threads are incorrectly sorted. if I move the messages to a different box, the problem disappears , the thread sort gives correct order.

Sorry, I did not keep a copy of my inbox in this state :-(

I have kept a copy of my inbox in this case, I can send it to you if it helps (54 k zipped)

This seems like a duplicate of bug 93426. I'm NOT marking it as such for now. Reporter: Please help differentiate your bug from bug 93426 (to see if it is or is not a dupe) Things that may help better define this bug: 1. is this bug only in e-mail or also newsgroups? 2. is it an IMAP or POP3 inbox? 3. do you always have your inbox in "threaded" view? 4. Is the threading fixed if you select another mail folder and then go back (or by selecting another sort order and then threaded again)? 5. Does this bug only occur in one of your inboxes (if you have more than one). 6. Have you tried deleting your "INBOX.msf" file to see if the problem goes away?

I looked to bug 93426, but this one is slightly different: I can collapse the thread and re-expand it, the problem remains. Actually, even if I close completely the mail window and re-open it, the problem remains. 1. Sorry, the only way I get mails is individually (I asked Yahoo groups to send me individual messages for 2 groups, in two different mail accounts. I have been Mozilla Mail for 2 weeks and I saw the bug twice (I may have missed it, I discovered the thread view recently), both times were with messages coming from the same Yahoo group. I am not using a newsgroup in a traditional way. 2. I use a pop3 box 3. Since the bug appeared, I have kept these boxes mainly in threaded view. 4. Collapsing doesn't change anything (see first paragraph above). I even put the inbox in date sort mode, leaved completely Mozilla, reloaded it, put back the inbox in thread mode, and the bug reappeared. 5. This bug only occurs in one of my inboxes, but I think it is too early to say if this is significant. This box is the most active (because the corresponding group is the most active currently). 6. I have tried to delete inbox.msf. After re-activating the thread mode, the bug reappears again. Do you want a copy of the my inbox (nothing secret inside, and the bug has gotten more spectular, Mozilla now mixes three different threads in one)?

The bug appeared on a second account, where I collect mails from another Yahoo group. So it seems it does not come from the account itself.

Perhaps the threading is (necessarily?) based on something in the e-mails (subject, Message-Id?) and that Yahoo may not be sending the correct info. Therefore correct threading might not be possible. Can you reproduce the error in another e-mail client (OE, Netscape 4.x) or with non-Yahoo e-mails? If you give me EXACT steps to reproduce your bug (e.g., the yahoo group), I would verify and "confirm" this bug, which would get it moving a bit more. PS. As a possible workaround: Is it possible to participate in these groups via newsgroup (NNTP)?

Sorry, I would really like to help you pinpoint the problem, but the only other mail clients I have (OE, Opera), don't do thread sorting. The only other mail account I have is my personal-private-hidden account, and on this one I don't receive enough mails to require a thread sorting. I will activate it from now on, though, just to check. The two are: http://groups.yahoo.com/group/delphi-en (the one where the errors appear most frequently) and http://groups.yahoo.com/group/eac. In both cases, to reproduce the bug, you must ask for "Individual mails" type of message delivery. I suggest you create a mail account for the test, mails from these lists arrive pretty frequently. And I checked, there is no mention of NNTP on Yahoo Groups. I am going to attach my inbox (12k zipped).

I compacted the mailbox before zipping it, and the bug remained.

After one day of receiving the reporter's forum's posts, here is what I see. Note the the "Find Error" thread doesn't seem to belong inside the "Problems with access Violations" thread. I don't know whether someone just OT posted into another thread and renamed the subject, or if Yahoo! doesn't provide the needed info for threading, or if mozilla is screwing up. I'll post the message sources of these posts so someone with more understanding of threading can look at them...

From e-mail from reporter: "I did my test on the Delphi-en Yahoo group. I just changed the subject to a simple "a" before posting my (empty) reply. As expected, my "New" post went in the old thread, "[delphi-en] Re: Delphi 5 and HTML Help"." Assuming he posted via e-mail, it seems that even changing the subject doen't cause breakage of the threading (that's good). I'm almost certain that either other e-mail clients or people entering their replies into the web-based form are causing the threading to be broken (In-Reply-To: ???). However, my knowledge of threading is limited. I would prefer that someone more knowledgeable could confirm this before marking this bug INVALID.

That was the choice of Horia Tudosie to send a message using the reply button instead of clicking an email address to start a new original message. This created an "in-reply-to: (msgid)" header that put it in some other thread. It was probably done in ignorance but that is a matter between him and his mailer. Due to the relative featurelessness of Outlook, I'm sure that he is totally unaware that there is a reference (in-reply-to: msgid) header that is sent. If it really bothers you, you might want to tell him privately not to do it that way. I do not feel this way but I am aware that many users prefer the subject-based threading, or some complicated heuristic looking at (was: old subject) and then keeping them together or splitting them apart, and I'm sure their opinion is colored by whatever long usenet threads they happened to be reading that week. Its really a matter of whether the burden of thread sorting should be on the sender or the recipient. Having it both ways is a mess. Personally I prefer it to be on the sender and will tolerate erratic threads assembled from the haphazard mailings of people who don't understand how it should work, rather than try and play a guessing game of whether two hypothetical messages would really feel like they go together. I think that there should be two options, one where mozilla handles the threading in some complex way that other people like but that I dont care about, and another where it just follows the references sent by the sender, good or bad. I think this really affects the message composition feature as well - I think we should have the option to do a "reply," with the previous message inline, and purge the in-reply-to: header when appropriate. There is another consideration and that is the correctness of other email programs. If mozilla continues to compensate for people doing crazy things, people who do crazy things will never be able to see that there is a better way. Most people don't know that composing a new message and hitting reply (then changing the subject as they please) will actually send the message differently, and they never will unless there is some strictness available in the interpretation.

I agree with comment #14. I have several emails in my inbox that are incorrectly appended to an older, unrelated thread with the same subject. I'm here because I wanted to file a bug about this behaviour, but apparently this is it. This happens with POP3 and IMAP folders. In some cases the mails are BCC's sent to myself, so I'm sure it's not a case of replying to an existing message. I think that Mozilla Mail should *not* put an email in a thread if there are no references or in-reply-to's that match.

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/