From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D46983858C20; Mon, 9 Jan 2023 09:07:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D46983858C20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1673255241; bh=jfz7NI04JPqvhalOpnuyaTZ0lSFrgr75cYXLHHunzk8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ld1SjgjXSxOHfrkWLB+VX5L1gdukqqCG6I9DG3zCydURbJoB/VgE/xMEsWisJdJjX Fk6MZfdSBhdXKxBbT/MTFnhjwSIsTinLIDZQOJUXISyUo99xW7xxGrS7NT5h9qyaf3 GaE+qZYPRjkU7PP93V1nhrp0YH8FFpX9B690zr0s= From: "fweimer at redhat dot com" To: overseers@sourceware.org Subject: =?UTF-8?B?W0J1ZyBJbmZyYXN0cnVjdHVyZS8yOTcxM10gUGxlYXNlIG1ha2Ug?= =?UTF-8?B?bGliYy1hbHBoYSBtYWlsaW5nIGxpc3QgY29tcGF0aWJsZSB3aXRoIOKAnGdp?= =?UTF-8?B?dCBhbeKAnQ==?= Date: Mon, 09 Jan 2023 09:07:11 +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: 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 #39 from Florian Weimer --- (In reply to Mark Wielaard from comment #37) > (In reply to Florian Weimer from comment #36) > > Asserting the non-existence of these headers is what breaks DKIM signat= ures > > with mailing lists. I reported this upstream-upstream here: > >=20 > > Signed header defaults break mailing lists > > >=20 > Thanks. There is also a Exim and Debian bug for this: > https://bugs.exim.org/show_bug.cgi?id=3D2394 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D939808 >=20 > It looks like a workaround is to not rely on the default exim setting of = the > dkim sign headers, but explicitly set it to: >=20 > DKIM_SIGN_HEADERS =3D > From:From:=3DSender:Reply-To:Subject:Subject:Date:To:Cc:Message-ID:In-Rep= ly-To: > References:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-ID: > Content-Description:=3DResent-Date:=3DResent-From:=3DResent-Sender:=3DRes= ent-To: > =3DResent-Cc:=3DResent-Message-ID:=3DList-Id:=3DList-Help:=3DList-Unsubsc= ribe:=3DList- > Subscribe:=3DList-Post:=3DList-Owner:=3DList-Archive" =E2=80=9C=3D=E2=80=9D for the mailing list headers disables nested mailing = lists (or forwarding mail to lists with =E2=80=9CS D r=E2=80=9D in Gnus, =E2=80=9Cb=E2=80=9D in = mutt). It should be much more compatible with the default. > > If Exim (or pdkim really) are unwilling to fix this, Mailman (or someth= ing > > in front of Mailman) needs to be taught to strip such anti-mailing-list= DKIM > > signatures. >=20 > The problem with getting this fixed seems to be that some people are > convinced dmarc and dkim will just break mailinglists always, so they don= 't > see a point in fixing the defaults. Some of them even have the power to change the defaults. It might be tricky= to convince them to make the change that proves them wrong. > Stripping can only be done if the dmarc policy for the domain doesn't > require DKIM signatures, otherwise we will either have to bounce them bef= ore > they reach the list or do From munging anyway (as suggested in comment #6= ). Right, it's non-trivial logic, and not going to be implemented for Mailman = 2. --=20 You are receiving this mail because: You are the assignee for the bug.=