This is the fourth draft of the series that enables indexing cleartext
of encrypted message parts.
previous versions start at:
v1: id:1449718786-28000-1-git-send-email-...@fifthhorseman.net
v2: id:1453258369-7366-1-git-send-email-...@fifthhorseman.net
v3:
On Sun, Jan 31 2016, Daniel Kahn Gillmor wrote:
> This is the third draft of the series initially announced in
> id:1449718786-28000-1-git-send-email-...@fifthhorseman.net (second
> draft was in
> id:1453258369-7366-1-git-send-email-...@fifthhorseman.net). It
> differs
This is the third draft of the series initially announced in
id:1449718786-28000-1-git-send-email-...@fifthhorseman.net (second
draft was in
id:1453258369-7366-1-git-send-email-...@fifthhorseman.net). It
differs from v2 in that it incorporates the recent improvements in
detecting and processing
This is the second draft of the series initially announced in
id:1449718786-28000-1-git-send-email-...@fifthhorseman.net:
> Notmuch currently doesn't index the cleartext of encrypted mail. This
> is the right choice by default, because the index is basically
> cleartext-equivalent, and we
On Wed 2015-12-09 22:39:37 -0500, Daniel Kahn Gillmor wrote:
> * the libnotmuch API is extended with
>notmuch_database_add_message_try_decrypt(). This should probably
>ultimately be more general, because there are a few additional
>knobs that i can imagine fiddling at indexing time.
On Fri, Dec 11 2015, Daniel Kahn Gillmor wrote:
> On Wed 2015-12-09 22:39:37 -0500, Daniel Kahn Gillmor wrote:
>> * the libnotmuch API is extended with
>>notmuch_database_add_message_try_decrypt(). This should probably
>>ultimately be more general, because there
Notmuch currently doesn't index the cleartext of encrypted mail. This
is the right choice by default, because the index is basically
cleartext-equivalent, and we wouldn't want every indexed mailstore to
leak the contents of its encrypted mails.
However, if a notmuch user has their index in a