practical compatibility GnuPG/PGP

[David T-G]

--nYySOmuH/HDX6pKp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Jeroen --

=2E..and then Jeroen Valcke said...
%=20
% On Wed, May 15, 2002 at 05:27:31PM +0200, Jeroen Valcke wrote:
% > However my mailclient mutt doesn't seem to recognize the message as an
=2E..
%=20
% I just discovered this on the mutt site.
% Q: "People are sending PGP messages which mutt doesn't
%     recognize.  What can I do?"
%=20
%     The new way is to leave headers alone and use mutt's
%     check-traditional-pgp function, which can detect PGP messages at
%     run-time, and adjust content-types.

Right.  Folks used to use procmail to tweak the headers, but that isn't
infallible.


%=20
% But I find no further reference for this 'check-traditional-pgp'
% function. What is it? Where must I specify it?

RTFM, grasshopper :-)


%=20
% Actually just realized this might be off-topic since it is purely a mutt
% thing. Sorry

It is; see my other reply for full details.


%=20
% -Jeroen-

HTH & HAND


%=20
% --=20
% Jeroen Valcke               jeroen@valcke.com  =20

I find it interesting that when I reply to your message it simply puts up
your address, without your full name, and silently drops the gnupg-users
list from the recipients.  What are you doing? :-)  I can't see anything
in your headers that would cause such behavior and I'm confused...


:-D
--=20
David T-G                      * It's easier to fight for one's principles
(play) davidtg@justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork@justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!


--nYySOmuH/HDX6pKp
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE84oh4Gb7uCXufRwARAlztAKDaeCOzQkh8KsU+DpGx0CoPkbrvmQCeKQSl
VtHsfWRl5EKc5aGVWYyeTqc=
=Llzk
-----END PGP SIGNATURE-----

--nYySOmuH/HDX6pKp--