Open
Bug 673092
(RFC2047)
Opened 13 years ago
Updated 2 years ago
[meta] Make Thunderbird RFC 2047 compliant - MIME Part Three: Message Header Extensions for Non-ASCII Text
Categories
(MailNews Core :: MIME, enhancement)
MailNews Core
MIME
Tracking
(Not tracked)
NEW
People
(Reporter: Usul, Unassigned)
References
(Depends on 8 open bugs, )
Details
(Keywords: intl, meta)
Tracking bugs for RFC 2047 related issues. MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
Reporter | ||
Updated•13 years ago
|
Assignee: nobody → ludovic
Status: NEW → ASSIGNED
Per discussion in bug 672424, this meta should also cover cases where a "mild" violation of the standard by incoming messages leads to unparsed headers, though such syntactical issues could be resolved where they are unambiguous and in turn wouldn't introduce problems with parsing correctly formed headers.
Reporter | ||
Comment 2•13 years ago
|
||
Agreed. Feel free to add these :-)
Updated•9 years ago
|
Summary: [meta] Make Thunderbird RFC 2047 compliant → [meta] Make Thunderbird RFC 2047 compliant - MIME Part Three: Message Header Extensions for Non-ASCII Text
Comment 4•9 years ago
|
||
Hi, May the bug #1089333 should be marked as depends on.
Reporter | ||
Updated•8 years ago
|
Assignee: ludovic → nobody
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•