Drew --
...and then Drew Bloechl said...
% Is there any way to force mutt to parse a message as containing PGP
% data? Often the Content-Type: is incorrect and mutt doesn't recognize
% it as signed/encrypted/whatnot.
Weell, yes and no; the proper answer is to change the Content-Type: and
there's even a procmail recipe in doc/PGP-Notes.txt (or, at least, there
was when I last checked at 1.0). Here it is from my cookbook:
# pgp recognition
# courtesy of Andrew Edelstein <[EMAIL PROTECTED]>
# and modified per PGP-Notes.txt [of 0.93.2i of 98/07/10 on 98/11/02 :-D]
:0 : pgp.lock
* !^Content-Type: message/
* !^Content-Type: multipart/
* !^Content-Type: application/pgp
{
:0 fBw : pgpencrypt.lock
* ^-----BEGIN PGP MESSAGE-----
* ^-----END PGP MESSAGE-----
| $FORMAIL -I "Content-Type: application/pgp; format=text; x-action=encrypt"
:0 fBw : pgpsign.lock
* ^-----BEGIN PGP SIGNED MESSAGE-----
* ^-----BEGIN PGP SIGNATURE-----
* ^-----END PGP SIGNATURE-----
| $FORMAIL -I "Content-Type: application/pgp; format=text; x-action=sign"
}
%
% --
% Drew Bloechl
% [EMAIL PROTECTED]
HTH & HAND
:-D
--
David T-G * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" starts at the beginning of 2001. There was no year 0.
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*
PGP signature
