Hi, * David T-G [2002-06-06 00:22:02 CEST] wrote:
> I had the same problem recently and we traced it to the > gpg exit code. It turns out that I had a bogus entry in > my options file that caused gpg to not fail but not exit > cleanly, and mutt noticed that. Wow, just to be curious, your solution is? I remember that discussion and the effects quite well, and in my case it only happens with messages which have inline instead of MIME-declared pgp signatures. I don't see any reason why GnuPG should return another exit status. And, what is why I gave up thinking GnuPG is the reason is the manpage: ,----[ gpg(1) ]- | RETURN VALUE | The program returns 0 if everything was fine, 1 if at | least a signature was bad, and other error codes for fatal | errors. `- Mutt reports a non-verified signature if PGP's or GnuPG's return code was non-zero. According to the manpage, at least a signature has to bad to make this happen. But the signatures are okay. I already gave up on this issue, but maybe I'll spend some time using check_pgp_traditional instead of a procmail rule. Cheers, Rocco
