I have a source hack that leaves PGP Encrypted and Signed messages as inline
text/plain text instead of PGP/MIME'ing them up. This allows PGP messages generated
in mutt to be easily decrypted/verified in {perhaps broken] clients like Outlook and
Eudora.
The reason I did this was because the PGP/MIME stuff was garfing up the official PGP
Outlook plugin. It can't seem to handle PGP/MIME attachments elegantly.
I don't know who is on higher moral ground, the PGP/MIME folks for the NAI folks. All
I want is a solution that works on more clients as painlessily as possible.
I wouldn't mind seeing a .muttrc variable along the lines of "set pgpmime = yes/no"
that does this functionality.
If anyone wants the source hack, email me offline.
On Tue, Oct 03, 2000 at 09:11:17AM +0200, Thomas Roessler wrote:
> On 2000-10-03 01:45:02 +0300, Eugene Paskevich wrote:
>
> > Can you explain what do you mean? app/pgp is Content-Type;
> > but what is PGP/MIME? And is it the way decide my problem?
>
> PGP/MIME is what mutt uses to send pgp-encrypted and -signed
> messages. The idea is basically this: You take the message, then
> MIME-encode it entirely. The result looks like this (for example):
>
> Content-Type: text/plain; charset=iso-8859-1
> Content-Transfer-Encoding: quoted-printable
>
> This attachment contains umlauts: =E4=F6=FC=DF
>
> Now, this entire MIME body part is encrypted/signed, and eventually
> put into some more MIME sugar. Here, PGP only ever touches us-ascii
> text (with which it deals nicely); the actual character set
> conversions are left to the software which interprets the inner MIME
> layers.
>
> - --
> Thomas Roessler <[EMAIL PROTECTED]>
> - --pWyiEgJYm5f9v55/--
>
> ------------------------------
