From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "David Bremner" <david@tethera.net>,
"Łukasz Stelmach" <l.stelmach@samsung.com>,
notmuch@notmuchmail.org
Subject: Re: [FEATURE] indexing arbitrary headers
Date: Thu, 30 May 2019 16:27:15 -0400 [thread overview]
Message-ID: <87k1e7it7g.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87d1alrq69.fsf@tethera.net>
[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]
On Sat 2017-06-03 13:28:46 -0300, David Bremner wrote:
> Łukasz Stelmach <l.stelmach@samsung.com> writes:
>
>> I'd like to ask for a new feature: indexing of arbitrary headers. Not
>> all headers but a few selected by users.
>>
>> For example, I get a lot of mails from a Gerrit system. I'd like to keep
>> them for a while and remove them when they are old enough. Although
>> these messages are distinguishable in my inbox, they've got subjects
>> like "Change in ..." and are from "nobody". But these may happen in
>> other e-mails too. The only 100% sure way to distringuish those e-mails
>> is to look for headers Gerrit adds.
>>
>
> Thanks for writing this up. Similar requests have been around for a
> while, but it's good to have a note in nmbug.
>
> There are two main blockers I'm aware of (other than someone writing and
> reviewing the code).
>
> 1) We need to index all copies of a message (e.g. using
> something like the series at id:20170507124012.30188-2-david@tethera.net)
>
> 2) we need to decide what happens when someone changes the list of
> indexed headers.
I just wanted to point out that this specific request has now been added
to notmuch, thanks to David Bremner! It will hopefully be part of the
forthcoming 0.29 release:
NEWS currently says:
Add support for indexing user specified headers (e.g. List-Id). See
notmuch-config(1) for details. This requires reindexing after changing
the set of headers to be indexed.
Bremner, i'm not sure how/when you want to clear the notmuch::wishlist
tag on the OP here, but it's nice to be able to reduce the stack listed
at https://nmbug.notmuchmail.org/status/#Wish-list
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-05-30 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170602071817eucas1p240c62e754f95c4dba776c1e400b02299@eucas1p2.samsung.com>
2017-06-02 7:18 ` [FEATURE] indexing arbitrary headers Łukasz Stelmach
2017-06-03 16:28 ` David Bremner
2019-05-30 20:27 ` Daniel Kahn Gillmor [this message]
2019-05-30 21:32 ` Carl Worth
2019-05-31 0:09 ` Ralph Seichter
[not found] ` <CGME20190531092827eucas1p21397cd9dcc8329eb5790cf7d4921c7a0@eucas1p2.samsung.com>
2019-05-31 9:27 ` Łukasz Stelmach
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=87k1e7it7g.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=david@tethera.net \
--cc=l.stelmach@samsung.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).