unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Charles Cazabon <charlesc-notmuchmail.org@pyropus.ca>
To: Notmuch mailing list <notmuch@notmuchmail.org>
Subject: user.other_email wildcard config?
Date: Fri, 1 Mar 2024 14:34:59 -0600	[thread overview]
Message-ID: <593124eb-b77b-4452-b407-37fc5ecbc890@pyropus.ca> (raw)

Hi,

To get notmuch to correctly identify me as the sender or recipient of
messages, I need to configure my primary and alternate email addresses -
however, I use extension addresses extensively (such as for subscribing to
this list...).  So in theory, I have an indeterminate number of addresses that
are "me", and in practice, it's at least several hundred I've actually used
(and adding new ones a few times a month on average).

Listing all of these addresses in the other_email configuration would be
painful, and would require constant maintenance as I use new addresses with
new businesses, mailing lists, etc.

I've searched the list archives but have only found references to setting
user.other_email to a list of actual addresses.  Is there a way to have a
wildcard, glob, or regex serve as the configuration for other_email?  Have I
missed something in the documentation?

Thanks,

Charles
-- 
------------------------------------------------------------------
Charles Cazabon              <charlesc-notmuchmail.org@pyropus.ca>
Software, consulting, and services available at http://pyropus.ca/
------------------------------------------------------------------

             reply	other threads:[~2024-03-01 20:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 20:34 Charles Cazabon [this message]
2024-03-03 15:36 ` user.other_email wildcard config? David Bremner
2024-03-03 17:02   ` Charles Cazabon
2024-03-03 17:21     ` David Bremner

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=593124eb-b77b-4452-b407-37fc5ecbc890@pyropus.ca \
    --to=charlesc-notmuchmail.org@pyropus.ca \
    --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).