You won't see this text if mutt automatically verifies signed text
(if pgp_auto_decode is set). Run ':exec
check-traditional-pgpreturn' if you see it to get the described
effect.
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hey folks,
I sent this message clear-signed on purpose to
Hello Martin,
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
You won't see this text if mutt automatically verifies signed text
(if pgp_auto_decode is set). Run ':exec
check-traditional-pgpreturn' if you see it to get the described
effect.
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello,
also sprach Michelle Konzack
martin f krafft wrote:
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
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-pgpreturn' if you see it to get the described
effect.
I have pgp_auto_decode
I sometimes see TOFU on lists where the sender is replying to a
message that was signed using traditional (inline) PGP. Their message
does not show up once check-traditional-pgp is called. Only the
original text from the quoted PGP signed section is displayed. I
don't think mutt has always
