From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5EABF3856974; Fri, 21 Oct 2022 14:52:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5EABF3856974 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1666363964; bh=yKIja/DZ5xOnIyiy8KAblawrPPbqlNsl4HEfCKuVYoY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=YdtV74LPghB27tByyudsmwJg5zBcFJssWHDtJkvYVGRkI0Rs6Mf6ZJ4i2xvX/w1cu cWXKhu9aAtMrVL5CgMXPONPjgQf4DSJYj/0nCQ9pvJVxviM20E9rCL6AqcA4+gnM1m tEyWoi8eWS6I1ekoVVr1DVEBsYvqVV6wdJC0vLhE= From: "fche at redhat dot com" To: overseers@sourceware.org Subject: =?UTF-8?B?W0J1ZyBJbmZyYXN0cnVjdHVyZS8yOTcxM10gUGxlYXNlIG1ha2Ug?= =?UTF-8?B?bGliYy1hbHBoYSBtYWlsaW5nIGxpc3QgY29tcGF0aWJsZSB3aXRoIOKAnGdp?= =?UTF-8?B?dCBhbeKAnQ==?= Date: Fri, 21 Oct 2022 14:52:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: sourceware X-Bugzilla-Component: Infrastructure X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fche at redhat dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: overseers at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29713 --- Comment #5 from Frank Ch. Eigler --- > The request here is about the user-visible From: header, not the envelope > sender. OK, but DMARC then adds From: header alignment checking. Anyway, mailing list admins are already able to change the relevant mailman2 setting for their own lists. I would advise against that in isolation ("from_is_list" change "Munge From" to "No"), because other mailing list processing may well corrupt whatever remaining authentication info is in the messages. This would result in drops or rejections & DMARC reports. There may be recipes for additional mailman2 options to reliably minimize those risks, and will let you know when/if we find them. (Note that google-groups does the same From: munging for reflected traffic for DMARC participant domains.) In the mean time, the raw mailing list traffic may be processed via imap, nntp, or http via inbox.sourceware.org. --=20 You are receiving this mail because: You are the assignee for the bug.=