Problems with the writing a new email or replying to one including using the autocomplete feature. Generally, problems found are within the compose window before sending a message. A few examples: 1. User interface and functionality problems with the html compose window and the plain text compose
window. 2. Problems with addressing a mail message or adding an attachment.

If you have a header reply-to field in a mail like this:
Reply-to: =?ISO-8859-1?Q?Lars_H=F8jberg?= <laho@int.tele.dk>
Mozilla doesn't decode the header when you press Reply to the mail.
The To field after pressing Reply becomes:
=?ISO-8859-1?Q?Lars_H=F8jberg?= <laho@int.tele.dk>
Richard is this MIME bug yours?

it's not only with the reply-to header but with any 8bits recipients. BAD BAD
BAD. We must fix that for RTM. Looks like I forget to translate the recipient!!!
It's a dogfood problem as you cannot reply to 8bits recipient.

This seems much to rare to be called dogfood, so I'm marking it dogfood-minus.
The work-around is to edit the to-field. The worst case result is some bounced
mail resulting from some of the extra chars... but you can resend etc.
From the description of the fix, we should very likely consider this for rtm,
and the nomination is already in place.

I applied the patch (original one), I tested the Latin1 header in the bug and
it's fixed by the patch. I also tested Japanese name in reply to, also worked fine.
For the second patch, we can use AssignWithConversion() for the error fallback.