46
edits
Changes
Added Internationalization section
* <span style="text-decoration:line-through;">Display of the message's own attachments are not right ([https://bugzilla.mozilla.org/show_bug.cgi?id=206278 bug 206278])</span><span style="background-color:lime;">Fixed for TB 2.0</span>
* It should be possible to file (import) the attachment or the .EML file directly into a mail folder ([https://bugzilla.mozilla.org/show_bug.cgi?id=11013 bug 11013] / [https://bugzilla.mozilla.org/show_bug.cgi?id=226877 bug 226877], [https://bugzilla.mozilla.org/show_bug.cgi?id=204612 bug 204612]). The menu action <tt> Message | Copy To | ''folder'' </tt> would be an elegant way to implement this.<br>For a .EML file, the Copy menu is enabled, but does nothing (the Move menu is disabled). However, for an RFC822 attachment, both menus are enabled, and an attempt to file the attachment using them '''puts the program into an unstable state''' that prevents normal message movement and other actions ([https://bugzilla.mozilla.org/show_bug.cgi?id=259522 bug 259522]).
== Internationalization bugs ==
[https://bugzilla.mozilla.org/show_bug.cgi?id=254519 Bug 254519]: Incorrect RFC 2047 encoding and decoding. This is one of the most-duped bugs in the mail domain. When replying to a message with an RFC2047-compliant header that happens to contain a comma in the name --e.g. <u><tt>Müller, Wolfgang</tt></u> -- the comma is interpreted as an address separator, and the reply goes to two different recipients, <u><tt>Müller</tt></u> and <u><tt>Wolfgang</tt></u> (and the actual mail address is only supplied to the second). A MIME-encoded name field is supposed to be treated as an atom; special characters contained within are to be treated literally.
== Filter bugs ==
