old-www/HOWTO/Mutt-GnuPG-PGP-HOWTO-9.html

39 lines
1.9 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>Mutt-i, GnuPG and PGP Howto: Interchanging signed/encrypted messages with different MUAs and platforms</TITLE>
<LINK HREF="Mutt-GnuPG-PGP-HOWTO-10.html" REL=next>
<LINK HREF="Mutt-GnuPG-PGP-HOWTO-8.html" REL=previous>
<LINK HREF="Mutt-GnuPG-PGP-HOWTO.html#toc9" REL=contents>
</HEAD>
<BODY>
<A HREF="Mutt-GnuPG-PGP-HOWTO-10.html">Next</A>
<A HREF="Mutt-GnuPG-PGP-HOWTO-8.html">Previous</A>
<A HREF="Mutt-GnuPG-PGP-HOWTO.html#toc9">Contents</A>
<HR>
<H2><A NAME="s9">9. Interchanging signed/encrypted messages with different MUAs and platforms</A></H2>
<P>In the first days, the PGP sign was included inside the text to sign.
Later, it was included the <CODE>application/pgp</CODE> MIME type to show that
the next attach was the sign or the encrypted PGP message, and finally,
with the PGP/MIME specification, it was possible to isolate the sign from
the original affected, to not modify absolutelly and somebody that didn't
have PGP could view the message as it was originally (only for signed
messages), without any added text in the beginning or in the end from PGP.
<P>The actual situation is that only a few mail user agents (MUAs) are
capable to integrate PGP to use the PGP/MIME standard, and it is necesary
to send messages using the old time PGP sign when you know that the
recipient doesn't recognize PGP/MIME.
<P>In Linux, the available mail user agents that are PGP/MIME compliant are
mutt-i and pine. In Windows, only the Eudora mail client versions 3.x and
4.x can use PGP/MIME. If you know any other mail user agent that supports
it, tell us by mail, to include it here.
<P>
<HR>
<A HREF="Mutt-GnuPG-PGP-HOWTO-10.html">Next</A>
<A HREF="Mutt-GnuPG-PGP-HOWTO-8.html">Previous</A>
<A HREF="Mutt-GnuPG-PGP-HOWTO.html#toc9">Contents</A>
</BODY>
</HTML>