This indeed sounds like a bug. What (essentially) happens is that mutt has to convert the original message to quoted-printable format. In doing so, mutt should definitely not even attempt to recode (or re-charset-label) the body parts it touches. If you don't see a fix for this in the next unstable release, please complain again. (Unfortunately, I will be traveling for the next two weeks, so I may not get around to take a stab at fixing this.) -- Thomas Roessler · Personal soap box at <http://log.does-not-exist.org/>. On 2005-02-18 18:23:23 +0100, Laurent Fousse wrote: > From: Laurent Fousse <laurent@xxxxxxxxxx> > To: Mutt Developers <mutt-dev@xxxxxxxx> > Date: Fri, 18 Feb 2005 18:23:23 +0100 > Subject: Bad charset conversion with gpg-signed mime-forward. > X-Spam-Level: > > Hi, > > I've seen some talks about gpg handling in mutt recently so I thought > it might be appropriate to report a bug I encountered with > mime-forwarded message when I gpg-sign the forward. > > Full report is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=295528 > > Summary: the charset declared in the header of the forwarded email are > changed from an original value of iso-8859-1 to utf-8 without actually > converting the message body. I don't know why this charset conversion > is necessary, but it does not seem to occur properly anyway. > > In the original bugreport you can see an "latin small letter e with > grave" that gets converted from its 8bit iso-8859-1 representation to > its quoted-printable encoding (but still iso-8859-1 where the new > headers say utf-8). > > I could reproduce the bug with latest CVS, but now my é letter > is encoded in quoted-printable by the folowing sequence: "=EF=BF=BD" > instead of "=E9" previously.
Attachment:
pgp5aWSfVuVbg.pgp
Description: PGP signature