* Issue with verifying cleartext signed messages
@ 2016-07-01 10:16 Sanel Zukan
2016-07-01 11:58 ` Tomi Ollila
0 siblings, 1 reply; 3+ messages in thread
From: Sanel Zukan @ 2016-07-01 10:16 UTC (permalink / raw)
To: notmuch
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Issue with verifying cleartext signed messages
2016-07-01 10:16 Issue with verifying cleartext signed messages Sanel Zukan
@ 2016-07-01 11:58 ` Tomi Ollila
2016-07-01 14:57 ` David Bremner
0 siblings, 1 reply; 3+ messages in thread
From: Tomi Ollila @ 2016-07-01 11:58 UTC (permalink / raw)
To: Sanel Zukan, notmuch
On Fri, Jul 01 2016, Sanel Zukan <sanelz@gmail.com> wrote:
> 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.
Does pressing '<' in show buffer help ?
Tomi
>
> Thanks in advace.
>
> Best,
> Sanel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Issue with verifying cleartext signed messages
2016-07-01 11:58 ` Tomi Ollila
@ 2016-07-01 14:57 ` David Bremner
0 siblings, 0 replies; 3+ messages in thread
From: David Bremner @ 2016-07-01 14:57 UTC (permalink / raw)
To: Tomi Ollila, Sanel Zukan, notmuch
Tomi Ollila <tomi.ollila@iki.fi> writes:
>
> Does pressing '<' in show buffer help ?
>
> Tomi
>
Alternatively, 'V' gives a raw message view.
d
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-07-01 14:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-07-01 10:16 Issue with verifying cleartext signed messages Sanel Zukan
2016-07-01 11:58 ` Tomi Ollila
2016-07-01 14:57 ` David Bremner
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).