![mozilla thunderbird email parser mozilla thunderbird email parser](https://user-media-prod-cdn.itsre-sumo.mozilla.net/uploads/images/2016-07-08-15-55-51-213ade.png)
That the ones who got it right were wrong. If we use workarounds instead ofĬorrecting the problem then they *will never* correct it and eventually assume If the only reason for these quotes is to work around bugs in other MUA than I I hope you won't mind if I have a different opinion on this (especially after > 2047 encoded-words and then parse the resulting text. > might help to work around bugs in some recipients' MUAs that try to decode > On the other hand, if a sender's MUA adds double quotes before encoding it > lots of annoying things that MUAs do to people's names - this is just another > wrong, but it can produce annoying cruft on a recipient's display. > Adding quotes to a name before encoding that name using 2047 is not strictly I use Mozilla, I like it and I wanted it to get it right.
#Mozilla thunderbird email parser code
Reports as, even though the issues are are related, this surely affects two veryĭifferent part of the code (I do believe that they should be corrected at the I will begin by saying that I should indeed have opened two different bug If what I copiedĪbove doesn't provided you with the answers you seek I can forward your question There seems to be a small interpretation problem of that RFC. I'm very familiar with this topic and I don't Yes, I meant to say "undecoded message headers". > *entirely* sure that we use the exact same 2047 encoding. > mean "encoded message headers" (that would be the only way to be Your reply (or at least my interpretation of it) suggests that you might There was a small typo in what he said above so I asked for precisions: > Do I have your permission to quote your reply when contacting the companies in > part when replying (keeping only what's between the ""). > - Use the RFC 2047 encoded message for display but remove the RFC 2047 encoded > encoding it using RFC 2047 (once again, this is to please these MUA address > That quoting would actually be temporary as it would have to be removed before > about syntax for display but quoting it, as necessary, when using it to reply. > - Convert RFC 2047 encoded messages to an unencoded message without bothering (or maybe, this is a last-resort option for patching legacy code where > necessary to make it look like RFC (2)822 compliant (except for the presence of > - Convert RFC 2047 encoded messages to an unencoded message, quoting it as So in the case of the "From:" line, what should MUA authors do?
![mozilla thunderbird email parser mozilla thunderbird email parser](https://d22blwhp6neszm.cloudfront.net/9/81651/10579484361.png)
In the next part, the questions are by me, the answer is given by him: These are quotes from the emails we exchanged (used with permission): This is what Mozilla generates when sending an email:įrom: =?ISO-8859-1?Q?=22Martin=2C_Andr=E9=22?= This is an example of an email address Mozilla has trouble with:įrom: =?iso-8859-1?Q?Martin=2C_Andr=E9?= ĭue to the presence of an unquoted "," (comma) when we try to reply it thinks It also expects to see that quoting when it receives emails and if it is missingĪnd the "From:" line contains a comma (",") it think that the "From:" lineĬontains two email address (which cause problem when replying and whenĭisplaying the list of messages (only one email adddress is shown)). The email address using RFC 2047 (which unfortunatly Mozilla does). In that case, it is believed that quoting should not be added before encoding Quoted but because they contain non-ASCII characters must be encoded using RFC 2047. The problem is only apparent because of the issues with commas (",") but it isīelieved that it might be caused by a slight interpretation problem as to how toĭeal with email address which contain things which under RFC (2)822 should be This bug is related to Bugzilla Bug #249626. The syntax used by Mozilla when sending an email which contains accents andĬommas was confirmed *not* RFC 2047 compliant by its author, Keith Moore. The syntax used by the other MUA (and with which Mozilla has problems) wasĬonfirmed RFC 2047 compliant by its author, Keith Moore. It should have considered it to be one email address. Mozilla thinks the "From:" lines contained two email addresses. This causes problems with MUAs which correctly encode or decode "From:" lines.ġ.Send an email from Outlook Express (6.x?) with a name which contains accents Then apply RFC 2047 (which it shouldn't do). It quotes an email address which contains a comma and (",") or similar characters), Mozilla doesn't decode it properly and thinks When an email contains a "From:" line encoded with RFC 2047 which containsĬharacters which should, per RFC (2)822, be quoted (because it contains commas