On Thu, Apr 30 2020, Daniel Kahn Gillmor wrote:
> This series applies after the "Add tests for S/MIME PKCS#7 messages"
> series, which was introduced in
> id:20200428185723.660184-1-...@fifthhorseman.net
>
> With this series applied, notmuch handles standard PKCS#7 S/MIME
> messages (using
Hello,
I was wondering whether anyone who previously read mailing lists via
NNTP has stopped doing this after starting to use notmuch.
I've not yet used NNTP to read mailing lists myself, but I think there
are limitations to the way I currently read lists, and was wondering
whether it is worth
In a previous email (about `thread:...` field in JSON output of
`notmuch show`), I described one of my use-cases for notmuch.
Now extending upon that, if one would to implement an email client
that provides the user with search, there are two approaches:
* use `notmuch search -- {query}` and
On Fri, May 1, 2020 at 3:09 PM David Bremner wrote:
> Ciprian Dorin Craciun writes:
> > I know that one can use `thread:{id:MESSAGE_ID}` to achieve the same
> > result, however:
> > * it is somewhat cumbersome for the integrator;
>
> Out of curiousity, what is harder about it? In both cases you
David Bremner writes:
> Offhand I have no strong objection to someone (who is not me) adding
> this. I think it's important to be aware that thread id's are ephemeral,
> and subject to change e.g. if the database is re-built from
> scratch.
I guess a more common/interesting case is that two
Ciprian Dorin Craciun writes:
> I know that one can use `thread:{id:MESSAGE_ID}` to achieve the same
> result, however:
> * it is somewhat cumbersome for the integrator;
Out of curiousity, what is harder about it? In both cases you have to
extra one value from the JSON.
> * having the thread
Ciprian Dorin Craciun writes:
> On Wed, Apr 29, 2020 at 8:08 PM David Bremner wrote:
>> > I've also read the FAQ:
>> > * https://notmuchmail.org/faq/#index8h2
>>
>> Oops, that needs to be updated.
>>
>> It is implemented. See notmuch-config(1), under "index.header"
>
>
> That's perfect.
