using a key without self-signature
Thu May 16 17:14:01 2002
Content-Type: text/plain; charset=us-ascii
Cal, et al --
=2E..and then Calum Selkirk said...
% * David T-G [email@example.com] [2002-05-15 11:12 -0500]:
% > > On Wed, May 15, 2002 at 05:27:31PM +0200, Jeroen Valcke wrote:
% > >
% > > 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.
% David pretty much covers the mutt specific aspects of this problem.
% Basically mutt isn't seeing these messages as signed/encrypted etc
% is due to the content headers. My ~/.procmailrc reads:
[snip] ---8<--- [snip]
FWIW, you might want to check into upgrading your mutt to a recent
version that can handle traditional PGP directly so that you don't have
to use the procmail method, which has been known to break messages.
% As David points out mutt can be patched to create_pgp_traditional (using
% David's mutt patch coctail is one soluton). You would then be able to add=
% message-hook to set mutt to send traditional/inline signed/encrypted mess=
You probably mean send-hook here. It might be interesting to try writing
a message-hook that automatically checks for traditional pgp, though...
% to firstname.lastname@example.org or ~h "^X-Mailer: Microsoft Outlook Express".
% Again this is covered in detail in the mutt-users list archive:
Yes. Please don't start another discussion of it :-)
HTH & HAND
David T-G * It's easier to fight for one's principles
(play) email@example.com * than to live up to them. -- fortune cookie
http://www.justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----