Mutt and old-style encrypted and signed messages

[Wayne Chapeskie]

On Tue, Sep 25, 2001 at 02:54:14PM +1000, David K. Trudgett wrote:
> 
> On Tuesday 2001-09-25 at 13:19:43 +1000, David K. Trudgett wrote:
> 
> > Hi!
> > 
> > Many of you who use Mutt will no doubt be aware that it takes the 
> > OpenPGP/MIME route to message encryption. Fine. I have no problem with
> > that, since that is the way it should be. But how do I configure Mutt
> > so that it will also automatically invoke GnuPG to decrypt/verify
> > old-style messages received? At the present time, if I receive such a
...


On Tue, Sep 25, 2001 at 11:51:12AM +0200, Andreas Siegert wrote:
> Found that on a mailing list ages ago for my .procmailrc:
> 
> # ----------------------------------------------------------------------
> # PGP to PGP-MIME conversion
> # Add a "Content-Type: application/pgp" header so Mutt will know the
> # mail is encrypted.
> :0
> * !^Content-Type: message/
> * !^Content-Type: multipart/
> * !^Content-Type: application/pgp

I had one correspondent who would send everything, included PGP mail,
with an added HTML formatted attachment.  Since his messages were
already "Content-Type: multipart/", the procmail recipe didn't fix
them.  Fortunately, the 1.3.* versions of mutt (beta) have a new
command, "check-traditional-pgp".  Bound by default to "ESC-P", it
checks a message, and all attachments, for old style PGP format,
substitutes a temporary Content-Type header, and enables mutt to
automatically decrypts or verify the message.

If you can't use procmail, or have older messages which were never
checked by procmail, this can be handy.  It is also useful when you
put the PGP procmail recipes at the end of your .procmailrc, and never
catch the messages handled by all the recipes which appear before the
PGP recipe...

-- 
Wayne Chapeskie
GPG/PGP KeyID: 0xB9D2D272