From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 779E6385DC09; Fri, 21 Oct 2022 14:13:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 779E6385DC09 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1666361618; bh=/1sfNOA0nUfxz971jhcrNBHi4hOu0CVEc3H9r5JfRww=; h=From:To:Subject:Date:In-Reply-To:References:From; b=malsWVKxTsxsi4qqP5AbnTgoIN8t/VO6nTxISbtYnKsG3Z19Xc09swz03IXDwz4K/ RSFr6bav+Bdc8m3dBBWNCRsUcaxLkdUaCBWezY11PJm3RwvUtJ1brlpc+YCL7qvFCP f+XI7WEfOyAFAVxNJaKicyZR0uK/9QALOB6OFqBc= From: "fweimer 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:13:38 +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: fweimer 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: cc 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 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com --- Comment #4 from Florian Weimer --- (In reply to Frank Ch. Eigler from comment #3) > > If we don't modify the message to invalidate the original DKIM signatur= e we > > don't have to do From rewriting. [...] >=20 > That still breaks SPF, which some mailing systems use to detect fraudulent > senders. Mailman puts its bounce processor address into the SMTP envelope MAIL FROM: (sometimes also called return path), and that's what's being checked by SPF. There is no way around that, obviously. The request here is about the user-visible From: header, not the envelope sender. --=20 You are receiving this mail because: You are the assignee for the bug.=