On Fri 2025-08-01 16:05:34 +0200, Michael J Gruber wrote:
> Note that the way you describe it, the "petname function/mapping"
> would depend on the From: header value only, not on the message per
> se. This is what git does with its ".mailmap" file, or other MUAs with
> their address book - they rewrite displayed addresses.
I agree, i don't want the mapping to be per-message. It might not be
from the From address itself, either, though. I'd probably want to rely
on only the addr-spec part of the From header; that is, a message with:
From: Alice <b...@example.org>
Should ignore the "Alice" part.
Alternately, if there is a valid signature from a recognized certificate
or public key, the petname could be associated with the certificate or
public key instead.
> As such, it is not so much something to be stored in notmuch's xapian
> db; maybe a config which notmuch could use to rewrite addresses before
> displaying (header -> petname) or using (petname -> real address, then
> query; if the mapping is invertible) them.
Sure, that sounds plausible, though i'd love to keep everything in a
single database without having to worry about a config file getting
de-synchronized from the database.
Is anyone doing anything like this, or should i try to design it myself?
--dkg
_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
