So, a couple of things...

On Fri, Nov 27, 2009 at 11:55:52AM +0100, martin f krafft wrote:
> You won't see this text if mutt automatically verifies signed text
> (if pgp_auto_decode is set). Run ':exec
> check-traditional-pgp<return>' if you see it to get the described
> effect.

I have pgp_auto_decode set, and additionally I unset it and manually
executed check-traditional-pgp, and I saw the above text in all cases.
So unless I misunderstood you, it seems my Mutt behaves differently
from yours...

But besides that, check-traditional-pgp is not intended to work with
MIME messages...

   <check-traditional-pgp> (default: Esc P)
          This function will search the current message for content signed or
          encrypted with PGP the “traditional” way, that is, without proper
          MIME tagging. Technically, this function will temporarily change the
          MIME content types of the body parts containing PGP data; this is
          similar to the <edit-type> function's effect.

The pgp-auto-decode variable is meant to be set only if you primarily
receive mostly non-MIME PGP messages.  Which is to say that
check-traditional-pgp is only meant for non-MIME messages, and setting
pgp_auto_decode makes mutt run that on every message.

   3.153. pgp_auto_decode

   Type: boolean
   Default: no

   If set, mutt will automatically attempt to decrypt traditional PGP messages
   whenever the user performs an operation which ordinarily would result in the
   contents of the message being operated on. [...]

This variable was added (by me, in fact) for folks who (like myself at
the time) mostly received mail signed or encrypted in non-MIME
fashion, which is to say all the signed/encrypted text and the
signature itself was in the body of the message.  For example, Pine
for the longest time (and possibly still, but I have no idea) was only
capable of using PGP in such a mode, and as it happened literally
everyone I knew who used PGP also used pine at that time.

So, you may not like the behavior, but it's not a bug.  The solution,
as already noted, is to unset pgp_auto_decode.  It's neither
appropriate nor required for MIME-based PGP mails, as mutt already
does the right thing there without it if the messages are marked
properly.  The option is probably obsolete or headed there, and
probably should not be set by default.

-- 
Derek D. Martin    http://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail due to spam prevention.  Sorry for the inconvenience.

Attachment: pgphAGWbNtKnt.pgp
Description: PGP signature

Reply via email to