From: David Bremner <david@tethera.net>
To: Tomi Ollila <tomi.ollila@iki.fi>,
Firmin Martin <firminmartin24@gmail.com>,
notmuch@notmuchmail.org
Subject: Re: Query emails sent to undisclosed-recipients
Date: Tue, 23 Mar 2021 16:26:41 -0300 [thread overview]
Message-ID: <87o8f9pt72.fsf@tethera.net> (raw)
In-Reply-To: <m28s6dk9dz.fsf@guru.guru-group.fi>
Tomi Ollila <tomi.ollila@iki.fi> writes:
> On Tue, Mar 23 2021, Firmin Martin wrote:
>
>> Hi,
>>
>> I have emails whose the "To" field is undisclosed recipients. In JSON:
>>
>> ```
>> "To": "undisclosed-recipients: ;"
>> ```
>>
>> I would want to tag such email as spam, but I can't query them
>> using
>>
>> ```
>> notmuch show --format=json to:"undisclosed-recipients: ;"
>> ```
>>
>> or any variation (regex etc.).
>>
>> This question has already been addressed in 2013 [1]. Are there any plan
>> to implement this feature or available workaround ?
>
> Tried. many things. did not work. notmuch-search-terms(7) tells
>
> to:<name-or-address>
>
> (so no regex syntax...)
>
> I don't know why that doesn't work. IIRC no plan, but patches welcome >;D
The (light) technical background is that regex syntax in notmuch
requires value slots, and someone (TM) would need to evaluate how much
adding a value slot for to: would cost in terms of database size / speed
of queries.
I think there's a separate question about address groups being ignored,
discussed in the linked thread.
d
next prev parent reply other threads:[~2021-03-23 19:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 13:11 Query emails sent to undisclosed-recipients Firmin Martin
2021-03-23 18:33 ` Tomi Ollila
2021-03-23 19:26 ` David Bremner [this message]
2021-03-23 20:03 ` Tomi Ollila
2021-03-24 0:24 ` [PATCH] test: add known broken test for indexing RFC822 group names David Bremner
2021-03-24 0:37 ` David Bremner
2021-06-07 23:33 ` David Bremner
2021-04-15 2:46 ` Query emails sent to undisclosed-recipients NeilBrown
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=87o8f9pt72.fsf@tethera.net \
--to=david@tethera.net \
--cc=firminmartin24@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).