Showing DKIM verified by gmail when the signature is broke in the Authentication Results

Again, this is just using the auth-res header not the online verifier. This is a message going through the dmarc ietf mailing list. it shows that the original signature is broken from gmail, but re-signed by ietf.org what I'm in the plugin is:
"DKIM Valid(signed by gmail.com) SPF: pass DMARC: fail
I suspect that it might be getting tripped up by the mailing list signature? because it passes but not the original signature.
Received-SPF: pass (google.com: domain of dmarc-bounces@ietf.org designates 4.31.198.44 as permitted sender) client-ip=4.31.198.44;
MIME-Version: 1.0
References: <20201218023900.E73B82ACBB2B@ary.qy>
 <a8281e16-9417-5189-df73-79ea0a865fbd@tana.it>
 <c713b9ae-a364-1ae0-e79-55f61624aa3d@taugh.com>
 <3034face-b6fc-0ce2-fa1b-f59210bd6f5b@tana.it>
 <46339b38-3b24-bcb7-5e73-8a97038ed69@taugh.com>
 <3997c81d-3b30-0823-a752-fb1d60a44593@tana.it>
 <74a5c37-19a6-6f6f-a51d-6e5cca5b29e8@taugh.com>
 <CAJ4XoYdXWTgADpdL1eJuYGnpSY038vj-FW_x1f2rEp1JL0r2oA@mail.gmail.com>
 <01RTICXKLL3E0085YQ@mauve.mrochek.com>
 <c5f7413e-52c1-6710-16e5-63f59d2c24b9@taugh.com>
 <CAL0qLwYDeV9CmFg9qCCGPse00JV30WRiSC4orC-EitK=hiahgA@mail.gmail.com>
 <a79dd75-4d73-d1dc-d6b1-272de866b950@taugh.com>
 <CAL0qLwZXu3FxH7QGBS7PGbeDwfDTGmC=rbPEQidVV4eDJNHLUA@mail.gmail.com>
 <CAJ4XoYeK2cJb+easc=mqCi4ap1932LmbDdfxM1dFZKrdo2a2mw@mail.gmail.com>
 <acfe3d9e-97eb-50ee-26a2-568fdd8359dd@taugh.com>
 <CADyWQ+GJ62jt=dL9Gzuw_O7USNbS=86BqAzu8Rdv9sCb5OpCdw@mail.gmail.com>
 <d4a00be5-bd61-0c05-3431-8d56b39a3550@tana.it>
 <8813331f-f5e4-faa5-c6d-11212fc25797@taugh.com>
 <5d150251-427c-5c44-a0c3-ad2e7f24b692@tana.it>
 <01RTP8I70EYI004QVR@mauve.mrochek.com>
In-Reply-To: <01RTP8I70EYI004QVR@mauve.mrochek.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 28 Dec 2020 23:03:46 -0800
Message-ID: <CAL0qLwafqVOGtzfM=2N6fB1pHcQJ6RRXpJeFBGh9qkTQ0wbnTw@mail.gmail.com>
To: Ned Freed <ned+dmarc@mrochek.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/FbukWojN8qmdsCqBZR8b6bm0Dek>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy
 implications of failure reports
Precedence: list
Cc: Tim Wicinski <tjw.ietf@gmail.com>, IETF DMARC WG <dmarc@ietf.org>,
 John R Levine <johnl@taugh.com>, Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/mixed; boundary="===============1237676303638430357=="
Errors-To: dmarc-bounces@ietf.org
Sender: "dmarc" <dmarc-bounces@ietf.org>

--===============1237676303638430357==
Content-Type: multipart/alternative; boundary="00000000000097be1f05b794fecb"

--00000000000097be1f05b794fecb
Content-Type: text/plain; charset="UTF-8"

On Mon, Dec 28, 2020 at 7:23 AM <ned+dmarc@mrochek.com> wrote:

> P.S. I hadn't looked at RFC 6589 before, and I  have to say I find its
> standards-track status to be nothing short of astonishing. How on earth do
> you
> assess interoperability?
>

With the benefit of hindsight, that's a great question.  I'd have been
happy with Informational.  Indeed, the IESG evaluation record shows several
ADs brought that up, but none of them insisted, and thus it didn't get
changed.

-MSK

--00000000000097be1f05b794fecb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Dec 28, 2020 at 7:23 AM &lt;<a hr=
ef=3D"mailto:ned%2Bdmarc@mrochek.com">ned+dmarc@mrochek.com</a>&gt; wrote:<=
br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">P.S. I hadn&#39;t looked at RFC 6589 before, and I=C2=A0 have to=
 say I find its<br>
standards-track status to be nothing short of astonishing. How on earth do =
you<br>
assess interoperability?<br></blockquote><div><br></div><div>With the benef=
it of hindsight, that&#39;s a great question.=C2=A0 I&#39;d have been happy=
 with Informational.=C2=A0 Indeed, the IESG evaluation record shows several=
 ADs brought that up, but none of them insisted, and thus it didn&#39;t get=
 changed.<br></div><div><br></div><div>-MSK<br></div></div></div>

--00000000000097be1f05b794fecb--

--===============1237676303638430357==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc

--===============1237676303638430357==--
lieser / dkim_verifier

Showing DKIM verified by gmail when the signature is broke in the Authentication Results #233
