270847 - Threaded view mixed unrelated mail.

Status: RESOLVED EXPIRED

(Thunderbird :: Mail Window Front End, defect)

Description

[bupkus]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Thunderbird 0.9+ (20041119 )

I have a thread about "Fry's" and found "Installing Firefox" inside that thread.
Both are from a PLUG (Phoenix Linux Group) mailing list. I just now upgraded to
the most recent version and still occurrs.

Reproducible: Always
Steps to Reproduce:
1.Upgrade
2.
3.

Actual Results:  
Same results

Expected Results:  
Created a seperate thread

Default config.

Comment 1

[David :Bienvenu]

look at the message headers, in particular the references: and/or in-reply-to
header. Sometimes people press reply and then change the subject, but we thread
by the references headers...

Comment 2

[Clint Olsen]

(In reply to comment #1)
> look at the message headers, in particular the references: and/or in-reply-to
> header. Sometimes people press reply and then change the subject, but we thread
> by the references headers...

In my case, the messages were completely unrelated.  The only common thing
between them was that they had the same subject line.  What are the odds that
the one in-reply-to somehow got the same hash value as the original message?

Comment 3

[Derek]

I am having the same problem.  Here's a break-down:

Message A is unrelated to B or C, but C is in reply to B.  I have the following
thread hierarchy:

Message A
  |==> Message B
         |==> Message C

Message A
=========
Subject: check this out
From: Sender A
To: Me
Date: 8/12/2004 10:34 AM
MessageID: <[e-mail]>

Message B
=========
Subject: check this out
From: Sender B
To: Me
Date: 2/15/2005 11:00 AM
MessageID: <00e301c51377$77a53980$0a86a8c0@COMPUTERNAME>

Message C
=========
Subject: Re: check this out
From: Me
To: Sender B
Date: 2/15/2005 11:23 AM
MessageID: <[e-mail]>
References: <00e301c51377$77a53980$0a86a8c0@COMPUTERNAME>
In-Reply-To: <00e301c51377$77a53980$0a86a8c0@COMPUTERNAME>

Thanks for your help in fixing this!

Comment 4

[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 5

[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.