Open
Bug 317068
Opened 19 years ago
Updated 2 years ago
mozilla those extends references by the MID, although she is contained at the end
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: bugzilla.alex, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
3.34 KB,
message/rfc822
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051104 SeaMonkey/1.1a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051104 SeaMonkey/1.1a
With the tests of defective Mails I determined, that Mozilla adds the MessageID again when I answering a Mail which already stands the own MessageID in the References.
I think that the MessageID stands only once in the references header.
Reproducible: Always
Steps to Reproduce:
Updated•16 years ago
|
QA Contact: backend
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Comment 1•16 years ago
|
||
Alex, Summary/description are quite unclear: do you mean that whenever a mail's References: already contain the MID of the message, replying will add it again, like this?
References: a b c
Message-Id: c
=>
References: a b c c
Message-Id: d
Can you attach an example mail producing the problem?
Actually, this an uncritical edge case anyway, hence reducing severity.
Severity: normal → minor
Reporter | ||
Comment 2•16 years ago
|
||
Yes, I meen your example.
I will search one of this mails.
Comment 3•16 years ago
|
||
I see this with Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4pre) Gecko/20090318 Shredder/3.0b3pre
Comment 4•15 years ago
|
||
I seem to recall seeing this fixed in v3. But I can't find the bug.
Comment 5•15 years ago
|
||
well, I just landed a change that makes us ignore a reference that's the same as the message-id for threading purposes, (bug 474790) but I'm not sure if that will fix this or not (or if this was fixed by some other change along the way)
Updated•2 years ago
|
Severity: minor → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•