191726 - Wrong threading view on mails with somwhat wrong References: header

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[J.Pietschmann]

User-Agent:       Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.2.1) Gecko/20021130

There appears to be a mail client which sends a correct In-Reply-To header but
a slightly incorrect References header (IIRC Pegasus Mail, but I
don't have the reference at hand, sorry). It violates RFC2822 sect. 3.6.4.:
   The "References:" field will contain the contents of the parent's
   "References:" field (if any) followed by the contents of the parent's
   "Message-ID:" field (if any).
The Message-ID of the parent is missing in the references. This causes Mozilla
Mail to thread the message to the parent of the parent, i.e. the message
identified by the Message-ID in the last References header. However, because
the In-Reply-To header is correct, Mozilla could use this information, perhaps
with some sanity checks (the parent referred by In-Reply-To should have
References or In-Reply-To matching the bogus References).
The misrepresentation of the message parent can be quite irritating, therefore
I set bug severity to "Normal" rather than "Minor"

Reproducible: Always

Steps to Reproduce:
1.
2.
3.




Maybe related, but apparently not identical to Bug #173486.

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.