From: Paul Jakma (paulj at domain itg.ie)
Date: Tue 04 Jul 2000 - 17:17:11 IST
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 4 Jul 2000, kevin lyda wrote:
>
> pgp4pine, or whatever it is pine uses to send pgp mail, doesn't
> correctly set up Content-Type headers. however this procmail
> recipie will solve the problem - it's from the mutt faq which
> is a wonderful document as all faqs are...
very nice of mutt to slap content-type headers on everything, but why does
it use "Content-type: application/octet-stream" for the actual encrypted
data? the "Content-type: application/pgp-encrypted" attachment is there
too, but just seems to have "v1.0" in it.
weird...
- --paulj
(who has never ever had problems with pgp4pine/pine except with kev's
mutt)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Made with pgp4pine 1.75
iEYEARECAAYFAjliDLAACgkQ4mUX5iYDSqmDkQCg1DmF8DAB3Uh+um+zoKxOI+UG
iQ4AmgLUExZVMoOiMONou8toqbKsVNIi
=mIdM
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:06:47 GMT