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.
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Hello, also sprach Michelle Konzack <linux4miche...@tamay-dogan.net> [2009.11.27.1538 +0100]: > It seems there is a misunderstanding from you of course the parser from > <debian> because normaly the "Debian Signature Parser" cut off the GPG > signed message and packe it into a new one with the signature attached, > which mean, it change te Header from "gpg-signed" to "multipart" put the > origial signed message body in the first part and then the Debian- > Signature in the second one. This has nothing to do with the case at hand. It is true that there seems to be a problem with the Debian list servers, and I am following up on that. For MIME messages, the list servers *must* attach a new part for they cannot edit existing parts which might be signed. The actual problem remains though. For some reason, the last message I sent was inline *and* PGP-mime signed, thus this one is simpler to exemplify the problem. There's a bit of text preceding the "Hello," up top of this mail, but if you configured mutt with pgp_auto_decode, then it filters the entire message through gnupg, which swallows all the unsigned text. - -- martin | http://madduck.net/ | http://two.sentenc.es/ "i always choose my friends for their good looks and my enemies for their good intellects. man cannot be too careful in his choice of enemies." -- oscar wilde spamtraps: madduck.bo...@madduck.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEAREDAAYFAksP6YQACgkQIgvIgzMMSnXzWgCgrgSe40w2i1Qwc3jKNMbh1cbU xysAoLerRS2pXJkT3E90TXAuH1l6KSr5 =Qt8M -----END PGP SIGNATURE-----
