From: Hannu Hartikainen <hannu@hrtk.in>
To: Michael J Gruber <git@grubix.eu>, notmuch@notmuchmail.org
Subject: Re: [PATCH] lib: consider all instances of Delivered-To header
Date: Wed, 23 Jun 2021 15:15:46 +0300 [thread overview]
Message-ID: <60d325f3.1c69fb81.dbc42.1809@mx.google.com> (raw)
In-Reply-To: <162444591341.4884.15473775974370085837.git@grubix.eu>
On Wed, 23 Jun 2021 12:58:33 +0200, Michael J Gruber <git@grubix.eu> wrote:
> Is an address from a received header (still) preferred over one from a
> delivered-to, or does the order of headers in the mail envelope play a
> role?
In my understanding the From: address is looked up in the following
steps (each step may have their own internal priorizing logic):
1. To, Cc, Bcc, Reply-To, From
2. Envelope-To
3. X-Original-To
4. Delivered-To
5. Received (for)
6. Received (by)
7. configured primary address
Obviously the patch doesn't touch this logic; it only affects the
handling of multiple Delivered-To headers.
Hannu
next prev parent reply other threads:[~2021-06-23 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 10:29 [PATCH] lib: consider all instances of Delivered-To header Hannu Hartikainen
2021-06-23 10:58 ` Michael J Gruber
2021-06-23 12:15 ` Hannu Hartikainen [this message]
2021-06-26 17:36 ` David Bremner
2021-06-28 7:11 ` Hannu Hartikainen
2021-07-02 9:13 ` [PATCH v2 1/2] reply: add test for multiple Delivered-To headers Hannu Hartikainen
2021-07-02 9:13 ` [PATCH v2 2/2] lib: consider all instances of Delivered-To header Hannu Hartikainen
2021-08-30 1:13 ` [PATCH v2 1/2] reply: add test for multiple Delivered-To headers 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=60d325f3.1c69fb81.dbc42.1809@mx.google.com \
--to=hannu@hrtk.in \
--cc=git@grubix.eu \
--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).