-----BEGIN PGP SIGNED MESSAGE----- On Mon, 15 Jul 1996, David Sternlight wrote:
At 6:01 AM -0700 7/15/96, Simon Spero wrote:
On a very similar note - could people who are using clear-text PGP signatures with mime use text/... instead of application/...; that way people without pgp will see the message text without having to mess with their mailcaps (that's the way text/* is supposed to work)
It's kludgy, I agree, but that's the way the example PGP translator for our mailer that some of us are using works right now. If someone rewrites that part of it, I'm sure we'd all be happy to switch. Dunno if there's an easy patch with ResEdit. (It's for the Mac.)
I think Simon was referring to the obsolete draft that defined the content type "application/pgp". The multipart/signed content type, IMHO, is hardly kludgy and is the best way to MIME encapsulate data. "Application/pgp" is definitely kludgy. BTW, those of you who do use PGP/MIME signing software should tweak the configuration a bit so there isn't an apostrophy in the MIME boundary. This makes it very difficult to verify the signature using metamail and possibly other MIME interpreting programs. - -- Mark =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= markm@voicenet.com | finger -l for PGP key 0xe3bf2169 http://www.voicenet.com/~markm/ | d61734f2800486ae6f79bfeb70f95348 "Freedom is the freedom to say that two plus two make four. If that is granted, all else follows." --George Orwell, _1984_ -----BEGIN PGP SIGNATURE----- Version: 2.6.3 Charset: noconv iQCVAwUBMerp+7Zc+sv5siulAQHm1gP8CnOUcwZfaQNMU0pZCo3k2efQTsfQaNGJ pjp3/ZycF3woyT8AST+fTqJjJrmFjJ5OLmqld3phzRJ8ANk7hHJzLQ+Sef9pwDl/ n1df6Tg8crtrxPfPSF6JR9XDGEjpbBqWBsxlH9T4aA1Ra7d78DC3sUvRzhCQWOnz dlgL/3aV4Bg= =Y9TP -----END PGP SIGNATURE-----