Open
Bug 697376
Opened 14 years ago
Updated 1 year ago
Incorrect parsing of Message-Id header with CFWS (Comments, Folding, Whitespace)
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
REOPENED
People
(Reporter: al-mozilla-bugzilla, Unassigned)
References
Details
(Keywords: testcase)
Attachments
(2 files)
Relation between messages msg1.eml (parent) and msg2.eml (child) is not detected in the threaded view.
I think that reason is incorrectly handling of Message-Id header with comment field. Let's see at the header of msg1.eml:
Message-ID: <1319452010.3981.1.camel@krishna> (sfid-20111024_142558_138515_6F63A54F)
Comment was added by CRM114 mailreaver and AFAIK does not violates RFC 5322 because Message-Id header defined by the following grammar:
message-id = "Message-ID:" msg-id CRLF
in-reply-to = "In-Reply-To:" 1*msg-id CRLF
references = "References:" 1*msg-id CRLF
msg-id = [CFWS] "<" id-left "@" id-right ">" [CFWS]
id-left = dot-atom-text / obs-id-left
id-right = dot-atom-text / no-fold-literal / obs-id-right
no-fold-literal = "[" *dtext "]"
| Reporter | ||
Comment 1•14 years ago
|
||
Updated•14 years ago
|
Attachment #569619 -
Attachment mime type: application/octet-stream → text/plain
Updated•14 years ago
|
Attachment #569620 -
Attachment mime type: application/octet-stream → text/plain
Comment 2•14 years ago
|
||
confirming based on RFC 5322 - there are a lot of places where we don't handle CFWS, from what I can tell.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•3 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Status: NEW → RESOLVED
Closed: 1 year ago
Duplicate of bug: 1259430
Resolution: --- → DUPLICATE
Summary: Incorrect parsing of Message-Id header with CFWS → Incorrect parsing of Message-Id header with CFWS (Comments, Folding, Whitespace)
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Comment 4•1 year ago
|
||
I disagree with closing this bug. This bug is older and contains more information than #1259430.
Updated•1 year ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•