From: Sanel Zukan <sanelz@gmail.com>
To: notmuch@notmuchmail.org
Subject: Issue with verifying cleartext signed messages
Date: Fri, 01 Jul 2016 12:16:07 +0200 [thread overview]
Message-ID: <87oa6hbr4o.fsf@darkstar.example.net> (raw)
Hi,
I'm using epa-verify-cleartext-in-region to verify cleartext signed
messages and noticed it will sometimes fail with notmuch, especially
when target mail message is part of longer thread.
For example, when signed mail is first in thread, body will look like:
-----BEGIN PGP SIGNED MESSAGE-----
<content>
-----BEGIN PGP SIGNATURE-----
<signature>
-----END PGP SIGNATURE-----
and epa-verify-cleartext-in-region will correctly capture and verify it.
However, when the message is second or third in thread, notmuch will
append spaces in front of it, making it looks like this:
-----BEGIN PGP SIGNED MESSAGE-----
<content>
-----BEGIN PGP SIGNATURE-----
<signature>
-----END PGP SIGNATURE-----
epa-verify-cleartext-in-region will fail here with: "Invalid cleartext
signed message".
Error is reproducible - copy the body of message with signature in new
buffer, remove starting spaces and epa-verify-cleartext-in-region will
work.
Any idea how to solve this? Or even better, is it possible to display
messages flat, without tree view.
If you can, please CC me with reply as I'm not member of this list.
Thanks in advace.
Best,
Sanel
next reply other threads:[~2016-07-01 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 10:16 Sanel Zukan [this message]
2016-07-01 11:58 ` Issue with verifying cleartext signed messages Tomi Ollila
2016-07-01 14:57 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oa6hbr4o.fsf@darkstar.example.net \
--to=sanelz@gmail.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).