From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: List change - munging for From addresses
Date: Fri, 2 Aug 2024 11:54:06 -0400 [thread overview]
Message-ID: <20240802-agile-manipulative-dog-df4487@lemur> (raw)
In-Reply-To: <20240802130347.383a1b49@canb.auug.org.au>
On Fri, Aug 02, 2024 at 01:03:47PM GMT, Stephen Rothwell wrote:
> As more and more sites are using DKIM signing or emails (and DMARC),
> more and more of the list traffic is not being delivered due to Mailman
> altering messages in subtle ways (so the DKIM signature is no longer
> valid). The easiest thing to do is to tell Mailman to munge the From:
> address so that the messages come from the mailing list itself. It
> also adds a Reply-To: header with the original sender's address.
>
> So a message from me to the list will now have
>
> From: Stephen Rothwell via Linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
> Reply-To: Stephen Rothwell <sfr@canb.auug.org.au>
>
> The only real downside to this (I think) is that if you take a message
> from the list containing a patch and apply that to a git tree you will
> have to fix up the Author appropriately.
>
> Konstantin, I assume (hope?) that b4 may have some way of fixing the
> authorship up?
Not really, for two reasons:
- X-Original-From is widely used, but isn't really a standard header.
- From-munging breaks end-to-end attestation, so we consider x-original-from
and similar headers a potential impersonation attempt and ignore them.
I would generally say that From-munging isn't a great option for any list that
receives patches. A much better approach is to just not modify the message
headers or message body. This should be possible with mailman.
-K
next prev parent reply other threads:[~2024-08-02 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 3:03 List change - munging for From addresses Stephen Rothwell
2024-08-02 3:19 ` Stephen Rothwell via Linuxppc-dev
2024-08-02 15:54 ` Konstantin Ryabitsev [this message]
2024-08-05 2:42 ` Stephen Rothwell
2024-08-05 14:54 ` Konstantin Ryabitsev
2024-08-12 5:54 ` Stephen Rothwell
2024-08-12 6:19 ` Stephen Rothwell
2024-08-12 6:32 ` Michael Ellerman
2024-08-12 13:53 ` Konstantin Ryabitsev
2024-08-25 22:41 ` Stephen Rothwell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240802-agile-manipulative-dog-df4487@lemur \
--to=konstantin@linuxfoundation.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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.
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 NNTP newsgroup(s).