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)

enhancement

Tracking

(Not tracked)

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
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.
Agreed. Feel free to add these :-)
Depends on: 697927
No longer depends on: 697927
Depends on: 733810
No longer depends on: 733810
Depends on: 1142691
Summary: [meta] Make Thunderbird RFC 2047 compliant → [meta] Make Thunderbird RFC 2047 compliant - MIME Part Three: Message Header Extensions for Non-ASCII Text
Hi,

May the bug #1089333 should be marked as depends on.
Depends on: 1146099
Assignee: ludovic → nobody
Status: ASSIGNED → NEW
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.