From: Liam Hupfer <liam@hpfr.net>
To: Kyle Meyer <kyle@kyleam.com>
Cc: misc@inbox.kyleam.com
Subject: Re: From header mangling for some debbugs mail to yhetil.org
Date: Sun, 10 Nov 2024 12:35:53 -0600 [thread overview]
Message-ID: <878qtr7x86.fsf@hpfr.net> (raw)
In-Reply-To: <87mslb69vt.fsf@kyleam.com>
[-- Attachment #1: Type: text/plain, Size: 2213 bytes --]
Hi Kyle, just getting back to this now.
Kyle Meyer <kyle@kyleam.com> writes:
> Liam Hupfer writes:
>> I noticed some messages involving debbugs end up with “via <list name>”
>> in the From header, but not others.
>
> My understanding is that this From rewriting is due to how the admins
> have configured Mailman.
>
> <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/docs/dmarc-mitigations.html>
>
> Here’s a previous discussion related to this on guix-devel:
>
> <https://yhetil.org/guix-devel/87pn2kyo2c.fsf@kyleam.com/T/#u>
>
>> As far as I can tell, these rewritten From headers don’t show up in
>> the archives at lists.gnu.org or debbugs.gnu.org.
>
> I don’t know what the underlying setup is there, but my guess is that
> those services get the messages before the rewrite. yhetil.org receives
> messages as any regular list subscriber would.
>
> If you look through other archives (e.g.,
> <https://www.mail-archive.com/bug-guix@gnu.org/>), you’ll spot some
> “via” senders.
Yup, I see them on emacs-devel as well. I think you’re exactly right about all
of this (as well as the bit about different configurations (no DKIM)
likely causing the differing behavior given a particular sender).
I did some more digging and found that Konstantin Ryabitsev’s [Subspace
mailing list server announcement] discusses appeasing DMARC. He argues
that mailing lists shouldn’t have to munge the From header assuming they
set the envelope-from address to the list domain and don’t fiddle with
any DKIM-signed content. I’m inclined to take the kernel.org list
administrator at his word on the subject.
So I guess I would have to convince the Mailman 2 maintainers to expose
this DMARC mitigation policy (or lack thereof) as an option, and then
convince the GNU sysadmins to upgrade. No idea how feasible that is.
For now, I set `p=none' in my DMARC record. Not ideal, but I don’t think
I’m at much risk of impersonation anyway.
Thanks for pointing me in the right direction!
—Liam
[Subspace
mailing list server announcement] <https://people.kernel.org/monsieuricon/subspace-mailing-list-server>
prev parent reply other threads:[~2024-11-10 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 3:08 From header mangling for some debbugs mail to yhetil.org Liam Hupfer
2024-08-17 4:39 ` Kyle Meyer
2024-11-10 18:35 ` Liam Hupfer [this message]
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://git.kyleam.com/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878qtr7x86.fsf@hpfr.net \
--to=liam@hpfr.net \
--cc=kyle@kyleam.com \
--cc=misc@inbox.kyleam.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).