From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EF4CF3858C27; Sat, 31 Dec 2022 15:58:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EF4CF3858C27 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1672502304; bh=mOFGppKZ5X/WqCEYE+aiufyyOMty1YfLq6tKOzaBsRk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=AaI83HgsnWoXni5lYFDvMpzVH6oPOikFsYB6GZ2h7HJp5lfoOHetVh1w54W2DD3nB l10G3LUgTz8Su45aNKueMUocqE24NKe/bXso+ZxvLU37hnb3DgtOxbqJeqX9V+6rOL CF70QUzZiI5wiP0XxiySvd/KH4xHBec8UfbgCroY= From: "mark at klomp dot org" To: overseers@sourceware.org Subject: =?UTF-8?B?W0J1ZyBJbmZyYXN0cnVjdHVyZS8yOTcxM10gUGxlYXNlIG1ha2Ug?= =?UTF-8?B?bGliYy1hbHBoYSBtYWlsaW5nIGxpc3QgY29tcGF0aWJsZSB3aXRoIOKAnGdp?= =?UTF-8?B?dCBhbeKAnQ==?= Date: Sat, 31 Dec 2022 15:58:23 +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: mark at klomp dot org 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 #31 from Mark Wielaard --- We really need some people with strict dmarc policies and/or who use dkim signatures to subscribe to the test-list to see if all settings are correct now. One remaining problem is what I believe Ian described in comment #6, people= who sign dkim messages in a way that we cannot avoid to break. e.g. when people include List-* or Sender headers in their dkim signature. I am unsure what = to do about this. Should we reject such messages? It seems that is signaling t= hey don't want their messages on a mailinglist or forwarded by a different send= er because they "protected" those headers. But maybe it isn't done deliberatel= y? Frank your domain, elastic.org, seems to be configured to sign (empty) list headers (Sender:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Me= ssage-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-O= wner:List-Archive) on all your messages. How would you like us to handle that? --=20 You are receiving this mail because: You are the assignee for the bug.=