unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Kevin Foley <kevin@kevinjfoley.me>, notmuch@notmuchmail.org
Subject: Re: Handling Email Addresses Without Name
Date: Sat, 15 Jan 2022 09:01:47 -0400	[thread overview]
Message-ID: <87lezhxidg.fsf@tethera.net> (raw)
In-Reply-To: <87pmouyoea.fsf@kevinjfoley.me>

Kevin Foley <kevin@kevinjfoley.me> writes:

> I realized I have a few messages, where the "from" address is missing a
> name.  For example, the from header is "jdoe@example.com" instead of
> "John Doe <jdoe@example.com>", which means the message won't show up if
> I search "from:John".
>
> Is there anyway to handle this?  Perhaps someway to annotate these
> messages so they would show up when searching "from:John"?

If you have want you can define a query

$ notmuch config set query.John from:jdoe@example.com

Then you can use

$ notmuch search query:John

----------------------------------------------------------------------
The next part is just me thinking out loud, not really an answer to the
original question.

Xapian has a synonym facility [1], but it is not currently used by
notmuch. This would work well for this particular application, but
(unlike query) it ORs the original term into the expansion (as makes
sense for synonyms). That would make it less useful for cases like
"from:me", where the query would match a literal "me" in the from
field. Thanks to Apple's cloud thingy, that actually matches quite a
lot.

[1]: https://xapian.org/docs/synonyms.html

  parent reply	other threads:[~2022-01-15 13:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 21:54 Handling Email Addresses Without Name Kevin Foley
2022-01-15 12:15 ` Ralph Seichter
2022-01-17 15:05   ` Kevin Foley
2022-01-15 13:01 ` David Bremner [this message]
2022-01-17 15:20   ` Kevin Foley
2022-01-17 18:14     ` David Bremner
2022-01-17 20:57       ` Kevin Foley
2022-01-18 13:15       ` Gregor Zattler

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=87lezhxidg.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=kevin@kevinjfoley.me \
    --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).