[Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Proposal

John Levine <johnl@ietf.email> Wed, 11 November 2026 22:02 UTC

Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id A71C446 for <ietf-dkim@ietf.org>; Wed, 11 Nov 2026 22:02:36 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=iecc.com header.s=185846af4e5f5.k2611 header.b=KP7d09Mc; dkim=pass header.d=ietf.email header.s=185846af4e5f5.k2611 header.b=llB4Lq6B; spf=pass (mx.ietf.org: domain of johnl@iecc.com designates 2001:470:1f07:1126:0:43:6f73:7461 as permitted sender) smtp.mailfrom=johnl@iecc.com; dmarc=pass (policy=none) header.from=ietf.email
Received: (qmail 99718 invoked from network); 11 Nov 2026 22:02:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=185846af4e5f5.k2611; t=1794434539; x=1794780139; bh=5b9Xxa6GRCVYYe8wYFPwadt7am6E3K5HGqqLIJFrHo8=; b=KP7d09Mc4Bc6Paq3c1ItFkxj9qq2VvTBuh7dFIVmkamqIcHkcAnUve2DT6u3bg7Ejl4T/iydazFU43LHR2bSBGrmGlnuviyKaeyguPRb5BapXJJyzz1o+kpetMG7mFTETOEF3QVarogco9jDbnCQZ3khOdHsrNRF5mpNE1TdnwldKXsQXTT/qsisqczrmGGwn1z/O9DQj8gGkOk0553EV+CVigaieD36YLYvCk5OWhHHPSL/6nhXAe4rdRIciYbJTUopBhyqVLxOX2I8bYWjPQP0eop9wbaNUJILBA38gcdSlwOvSXmaUYOl3d0q0I/1R/iisuWjxI4gMoSWNfjXrA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=ietf.email; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=185846af4e5f5.k2611; bh=5b9Xxa6GRCVYYe8wYFPwadt7am6E3K5HGqqLIJFrHo8=; b=llB4Lq6BSi1Qe4TAbQxL1yEKH0FC+6HbHagIgHTNfHeVZIE+43hZtHGMwoTuU9Rnbr+kyv5er58ag16GBrFEveCYXV3BNPmn//nrYEI2z0ZKq33XBdzDjbXT8q/NxIC8QKmDMgQfb5o1ojkZwOh0ACyyB2iChvP5YkOtGDGiXSch3C1MpGoSkWr3NzJh/RQRO6NcFBTW9qXo1eYWZbzMQTDB7dhVoqT2g1VoWtni1xDjbZmw0VWRXnosmG8froD+a7D/hVFvTRb7stXQq/qICLkDMX9LcVqbAxalE4270TjpvYMwcGjaZXMpNNLScA6zTPcL46QrBg9Z2qarDILq2w==
Received: from ary.qy ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 11 Nov 2026 22:02:29 -0000
Received: by ary.qy (Postfix, from userid 501) id 161EA12828BBD; Wed, 11 Nov 2026 17:02:28 -0500 (EST)
Date: Wed, 11 Nov 2026 17:02:28 -0500
Message-Id: <20261111220229.161EA12828BBD@ary.qy>
From: John Levine <johnl@ietf.email>
To: ietf-dkim@ietf.org
In-Reply-To: <CAHEDGu-GFi5aeWJySSsmWpmnsrehvU2ayVnwUcVJDktjROqoOA@mail.gmail.com>
Organization: Taughannock Networks
References: <CAAFsWK1M--tCPj=Nhz8jB-9uaoeiJcdmfBZKaJsAXFaT4Z9fgQ@mail.gmail.com> <CAHEDGu8h9wyukuj+yDT+LQH-hk32iPbdrQ4sxny6KoKMYYyzxQ@mail.gmail.com> <CAAFsWK3jepdeMzQi5Whs4chDF2daAR0-5ED672WaLP73MG1VTw@mail.gmail.com> <CAAFsWK1K-1br3fOrr5=tc-GahaJwki8=cGH2g=pxfKre=auViw@mail.gmail.com> <CAMhUCqLk3+hZbqKOZ5234BJo=dhX0Gn8VV1xRNAOQenjFZvdxg@mail.gmail.com> <CAAFsWK0FLF2zb06Uc_UmhsWT3tNTkhLBYAu_qLLtjpowr5N93A@mail.gmail.com> <PR3P193MB050519ADCD0C265556254325D1BE2@PR3P193MB0505.EURP193.PROD.OUTLOOK.COM> <CAAFsWK1ucEx2uDqQq9zSAQtYdZb5gqeAizwQczNryNug6H6dhA@mail.gmail.com> <CAAFsWK3-S9krHyGBBJ6hkUROfyXGsGsNqddyjfkez8=4qw0A_g@mail.gmail.com> <CAMhUCqJxq_22UU3kGew2GoedcxpAgUMFxq7o1M5GcmdFb=_H0w@mail.gmail.com> <CAHEDGu_jzhmoY4U+OreBp3PbvS4cb-LExNrY+vjXQ8Ddx=gKYQ@mail.gmail.com> <CAAFsWK2Td43CdLa9=XnEBb2Uuy2bfCcAuO2y3=THkESw0yzh1w@mail.gmail.com> <CAHEDGu-11sgVCWoFYPVvxLdjO7GatboW7d03+DwZf0O0qqHTJg@mail.gmail.com> <CAHEDGu-GFi5aeWJySSsmWpmnsrehvU2ayVnwUcVJDktjROqoOA@mail.gmail.com>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
X-Spamd-Bar: -------------------
Message-ID-Hash: 2SC2LGKSZ2K64VG56FGDRYHTH6PLBMT6
X-Message-ID-Hash: 2SC2LGKSZ2K64VG56FGDRYHTH6PLBMT6
X-MailFrom: johnl@iecc.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ietf-dkim.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: emschorsch@gmail.com
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Proposal
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/IucDaPbHG63Mm60JnFTJ_BBNapA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-dkim-owner@ietf.org>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Subscribe: <mailto:ietf-dkim-join@ietf.org>
List-Unsubscribe: <mailto:ietf-dkim-leave@ietf.org>

It appears that Emanuel Schorsch  <emschorsch@gmail.com> said:
>-=-=-=-=-=-
>
>On Wed, Nov 11, 2026 at 8:09 AM Pete Resnick <resnick=
>40episteme.net@dmarc.ietf.org> wrote:
>
>> I basically agree with both Pietro and Richard here: I suspect that in
>> the end, common practice is going to be "If the change recipe only
>> modified the Subject and added a minimal (amount TBD) to the end of the
>> body, then by policy I'll accept the message without a change to the
>>  From. Otherwise, by policy I'm going to bounce it unless I have a
>> pre-existing trust relationship with the intermediary who did it." This
>> is why I think the who discussion of From alignment and donotmodify is
>> really kind of moot and not worth mentioning in the spec: If the changes
>> are deemed to be "minimal", then the end system is going to let it
>> through, and if the changes are more than "minimal" (which would include
>> absolutely any deletion of bits of the body) by an unknown intermediary,
>> they'll be rejected, regardless of a donotmodify or canmodify flag.
>>
>
>Pete I agree with you that that seems like a likely prediction. That seems
>like a chaotic and unpredictable arrangement. Isn't it better to have a
>consistent way of handling it? 

Probably not because experience tells us that senders will put stupid
conditions on their mail to make it "more secure" which sensible
receivers will ignore because it's mail their users want.

Cynically,
John

PS: See for example, all the places that send DMARC p=reject to mailing lists.