Re: RFC 2015 messages

[Frank T. <ft...@ui...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Trevor Johnson, at 13:10 -0400 on Mon, 17 Jul 2000, wrote:

> How can I use pgpenvelope with messages that use the RFC 2015 MIME types
> (described at ftp://ftp.isi.edu/in-notes/rfc2015.txt)?  My setup looks
> like this:

Unfortunately, Pine doesn't appear to support processing multi-part
messages yet by its standard display-filtering mechanism.  There is hope,
however, to succeed by using Pine's pipe-filtering mechanism, or via
procmail.

> I've configured pine to use pgpenvelope according to the examples in the
> man page.  I tried editing a message I'd received, changing the MIME type
> to text/plain, and pgpenvelope could decrypt it afterward (not
> beforehand).  I tried sending a message, and it was given a text/plain
> MIME type.  I'm told that for users of Mutt (an MUA for Unix--see
> www.mutt.org), such messages are more difficult to decode than ones
> constructed according to the RFC (the author of the RFC is also the author
> of Mutt).

Yes, Mutt does currently have PGP/MIME support.  Pine does not support
multi-part MIME's such as PGP/MIME yet.  Something, unfortunately, is
going to have to evolve in Pine, I feel, for pgpenvelope to get PGP/MIME
supoprt.

- -- 
Frank Tobin		http://www.uiuc.edu/~ftobin/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (FreeBSD)
Comment: pgpenvelope 2.8.10 - http://pgpenvelope.sourceforge.net/

iEYEARECAAYFAjlzdDEACgkQVv/RCiYMT6MleQCgjgVD36wZz/VfNEkOI+kWe8Iw
v54AnA8lNuDvr0ez5NGYo7S6WgSb4h+A
=f4bS
-----END PGP SIGNATURE-----