2000-07-20-01:49:15 Dennis Robertson:
> When I open that attachment I see:
> ----BEGIN PGP MESSAGE----
> (pgp text) garbage garbage garbage etc
> ----END PGP MESSAGE----
What's happening is that the message you're receiving doesn't have
the MIME headers that mutt needs to be able to notice that it's
encrypted.
There are recipes in PGP-Notes.txt for procmail and maildrop, which
recognize the old-style PGP messages and add MIME headers, but
neither procmail nor maildrop is a MIME processing tool, and so the
recipes take a very simple approach: they make sure the message
isn't already a multipart of any sort. This message is a multipart,
you indicated that you're seeing this as attachment #3, which means
that those recipes can't help you.
The upshot is that you have only a couple of choices.
You can do a smarter recipe, using a tool that includes a full MIME
parser, to adjust the MIME types properly even for parts of existing
multiparts. I've no clue how to pursue that one.
Or you can just live with it, and manually pipe the offending
sections through gpg and then into a pager. Or you can save 'em out
into external files, gpg 'em, and few the results. You might be able
to simplify these things with macros, but I don't know any way of
telling mutt to peek into the body and Do The Right Thing completely
automatically; that'd require changes to the source. I haven't heard
of anybody pursuing those changes, and since mutt is continuing to
try to change the world on this point, by adamantly (or perhaps
even "stridently") insisting on supporting nothing but RFC 2015
PGP/MIME and demanding that the rest of the world follow suit, I
wouldn't expect patches like that to be written by anybody who is
following mutt's party line, nor would they be accepted into the
main line of mutt.
-Bennett
PGP signature
