Hi, * Thorsten Haude [02-07-13 15:24:58 +0200] wrote: > We have two cases: One is verified by GPG but not by Mutt,
Well, I've been asking in a de.ALL newsgroup for help on this issue. The solution (which works, whoooohooo! ;-) is: + set pgp_good_sign="^\\[GNUPG:\\] VALIDSIG" + add '--status-fd=2' to the following commands: pgp_decode_command pgp_verify_command pgp_decrypt_command The disadvantage is that this extends the GPG output with status output. This contains "[GNUPG:] VALIDSIG ..." if a signature is valid and this output matches $pgp_good_sign. Maybe this isn't new since the value for $pgp_good_sign is Debian-only, what I didn't know is that I have to add '--status-fd=2' to those commands. I'm thinking about sending a mail to mutt-dev with a patch to suggest including it in the official release. It definitely looks better than the ugly hack: ,----[ /tmp/mutt-1.4/contrib/gpg.rc ]- | # pattern for good signature - may need to be adapted to locale! | | # set pgp_good_sign="^gpg: Good signature from" | | # OK, here's a version which uses gnupg's message catalog: | set pgp_good_sign="`gettext -d gnupg -s 'Good signature from "' | tr -d '"'`" `- Left are mails which cannot be verified at all. And I guess this is not mutt-related. bye, Rocco