[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] forcing a particular character set
From: |
Lyndon Nerenberg |
Subject: |
Re: [Nmh-workers] forcing a particular character set |
Date: |
Fri, 7 Nov 2014 15:14:53 -0800 |
On Nov 7, 2014, at 2:35 PM, Anthony J. Bentley <address@hidden> wrote:
> Sometimes I want to force a particular character set. Specifically,
> I send PGP mail by pasting ASCII armored encrypted GPG output into
> the editor brought up by comp(1)/repl(1).
And that's your problem. To pass along character set info you need to use the
correct MIME structure. What you want is a top-level multipart/encrypted
wrapping an application/pgp-encrypted containing a text/plain with the
appropriate character set attributes attached to it.
RFC1847 defines multipart/encrypted. RFC3156 documents
application/pgp-encrypted.
While you might be able to torture nmh into generating this directly, save your
sanity and write something outside of nmh that builds the encrypted message for
you. I'm sure a few minutes with duckduckgo will turn up a boatload of scripts
that solve this exact problem.
--lyndon
signature.asc
Description: Message signed with OpenPGP using GPGMail