Due to some issues arising out of the use of GPG with mutt, I added
this recipe (from mutt's website) to my .procmailrc:
:0
* !^Content-Type: message/
* !^Content-Type: multipart/
* !^Content-Type: application/pgp
{
:0 fBw
* ^-----BEGIN PGP MESSAGE-----
* ^-----END PGP MESSAGE-----
| formail \
-i "Content-Type: application/pgp; format=text; x-action=encrypt"
:0 fBw
* ^-----BEGIN PGP SIGNED MESSAGE-----
* ^-----BEGIN PGP SIGNATURE-----
* ^-----END PGP SIGNATURE-----
| formail \
-i "Content-Type: application/pgp; format=text; x-action=sign"
}
This accomplished its nominal purpose, but it seems to introduce some
linewrapping. Some PGP 'Version:' lines are very long, for instance:
-----BEGIN PGP MESSAGE-----
Version: PGPsdk version 1.7.1 (C) 1997-1999 Network Associates, Inc. and its
affiliated companies.
Since the addition of the above recipe, this line comes through now as:
-----BEGIN PGP MESSAGE-----
Version: PGPsdk version 1.7.1 (C) 1997-1999 Network Associates, Inc. and its
affiliated companies.
And GPG bombs out on the new - illegal - line:
[-- PGP output follows (current time: Sun Apr 22 12:27:16 2001) --]
gpg: invalid armor header: affiliated companies.
A couple of questions:
Is formail wrapping the line?
Should a recipe like the above come before, or after, the other
recipes in .procmailrc? (Mine are simple, and just sort one user's
mail into folders.)
--
Bob Bernstein | Public Key: http://www.ruptured-duck.com/GnuPG.html
at |
Esmond, R.I. | GnuPG 115B 8AA0 D418 F33B F0B1 6230 8014 B8D5 4A93 E562
USA |
pgpfLjBF5WURs.pgp
Description: PGP signature