>> No, email clients not conforming to RFC 2822 section 3.6.4 is what is
>> screwing up the thread tracking.
>
> I don't know enough to verify this. I know that when people continue
> threads with new subjects, thread tracking works fine. However, when
> this popped up, it appeared to start a new thread in both instances I've
> seen it.
Conforming email clients include a "References" header and/or an "In-Reply-To" header with the messageid of the previous message in the thread when responding. This is the behaviour specified in RFC 2822, and that header is used by the receiving email client to properly thread email.
When the email that is being sent does not include such a header, the receiving email client can still try to thread it by matching the subject (and it is usually included at the bottom). But if the subject is changed too, there is no way to tell to which thread it belongs, and a new thread is started.
> And, again, if you look at what I wrote, I said that it screws up thread
> tracking "in Thunderbird", which is all I know about for sure.
Not just in Thunderbird, also in the archives. But the problem is not caused by Thunderbird, but by the sending email client.
Jochem
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
