I am trying to get GPG inline signing to work. The signing process itself works fine, however, before passing the message to gpg mutt (specifically muttng-20030325, but I had this problem with plain old mutt as well) converts it to UTF-8, completely against my will. I am perfectly happy with ISO-8859-15 encoding, which is what the messages get (correctly) identified as when I do anything other than sign them inline (sign with PGP/MIME, not sign at all, and apparently sign/encrypt too). For reference, this message should be iso-8859-15, not utf-8. It would be us-ascii if it wasn't for my signature. I asked on gnupg-users and was pointed toward the MUA and editor. (See <http://lists.gnupg.org/pipermail/gnupg-users/2005-August/026353.html>.) Since the message is fine until passed to gpg, that leaves mutt. GnuPG only has a setting "charset iso-8859-15" in effect from the configuration file, and my mutt charset settings are (config_charset seems irrelevant and is left unset): charset="iso-8859-15" assumed_charset="us-ascii:iso-8859-15:iso-8859-1" file_charset="us-ascii:iso-8859-15:iso-8859-1" send_charset="us-ascii:iso-8859-15:iso-8859-1" I have added assumed_charset and file_charset this morning after looking through the manual for all charset-related settings, but that did not change anything. The message still gets re-encoded as UTF-8. My PGP sign commands are: set pgp_sign_command="/usr/bin/gpg --no-verbose --batch --quiet --output - %?p?--passphrase-fd 0? --armor --detach-sign --textmode %?a?-u %a? %f" set pgp_clearsign_command="/usr/bin/gpg --no-verbose --batch --quiet --output - %?p?--passphrase-fd 0? --armor --textmode --clearsign %?a?-u %a? %f" folder-hook . 'set pgp_encrypt_sign_command="pgpewrapng /usr/bin/gpg %?p?--passphrase-fd 0? --batch --quiet --no-verbose --textmode --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f"' (`pgp_encrypt_sign_command' is set by a folder-hook as it is overridden for some folders on a per-folder basis.) Given these settings, why does mutt still insist on converting the message to UTF-8 even when ISO-8859-15 is perfectly enough, and more importantly, what can I do to prevent this conversion from taking place? Grepping the manual case-insensitively for `utf' gave no clues other than the charset settings I listed above. And please don't tell me how bad inline signing is, that doesn't reduce the number of people using RFC-ignorant MUAs. -- Michael Kjörling, michael@xxxxxxxxxxxx - http://michael.kjorling.com/ * ASCII Ribbon Campaign: Against HTML Mail, Proprietary Attachments * * ..... No bird soars too high if he soars with his own wings ..... *
Attachment:
pgpjdy4DfNeN4.pgp
Description: PGP signature