jonas hedman wrote: > "Content-Type: text/plain; charset=iso-8859-1 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Secret =E5=E4=F6 =C5=C4=D6"
As the header shows, the =E5 characters are quoted-printable encoding. Mutt is encoding the characters because the PGP/MIME RFC (3156) says all 8-bit characters for pgp/signed message MUST be encoded. (I am guessing you are both signing and encrypting the messages.) Email clients should generally deal with this correctly, and decode the content before displaying it. If for some reason, the recipients are viewing the content outside of a MUA, they may want to use the qprint utility to decode and view the content. > 2. Why doesn't this problem show up when encrypting inline style? Inline style has no such mandate. If allow_8bit is set and you are also encrypting the message (which ascii-armors the output), then Mutt allows the 8-bit encoding. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA http://www.8t8.us/configs/gpg-key-transition-statement.txt
signature.asc
Description: PGP signature
