On Thu, Mar 10 2016, David Bremner wrote:
> Tomi Ollila <tomi.ollila@iki.fi> writes:
>
>> 2016-03-08 (Tue) 14:16:01: reply --format=sexp --format-version=1 --reply-to=sender thread:0000000000004a6f
>> 2016-03-08 (Tue) 14:16:01: show --format=raw --part=2 id:56DDE706.6060702@bubblegen.co.uk
>> 2016-03-08 (Tue) 14:16:01: show --format=sexp --include-html --part=3 id:56DDE706.6060702@bubblegen.co.uk
>> 2016-03-08 (Tue) 14:16:01: show --format=raw --part=3 id:56DDE706.6060702@bubblegen.co.uk
>>
>> when replying from show:
>>
>> 2016-03-08 (Tue) 14:16:37: reply --format=sexp --format-version=1 --decrypt --reply-to=sender id:56DDE706.6060702@bubblegen.co.uk
>> 2016-03-08 (Tue) 14:16:37: show --format=raw --part=2 id:56DDE706.6060702@bubblegen.co.uk
>>
>> there's no --decrypt when from search ... and interestingly there are other
>> differences, too...
>
> That's useful log info, thanks Tomi. With dme's series
> id:1457457179-4707-1-git-send-email-dme@dme.org I get the ciphertext
> when replying from search-mode, which suggests there are at least two
> bugs here.

That's related to "notmuch reply --decrypt thread:something" I believe,
which didn't seem to decrypt when I did a quick test (but I wasn't
concentrating on that aspect of things).