[Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Proposal
Richard Clayton <richard@highwayman.com> Sun, 20 September 2026 15:24 UTC
Received: from mail.highwayman.com (mail.highwayman.com [217.155.43.13]) (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 3074A30 for <Ietf-dkim@ietf.org>; Sun, 20 Sep 2026 15:24:18 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=highwayman.com header.s=rnc1 header.b=Al9Gp8nm; dmarc=pass (policy=none) header.from=highwayman.com; spf=pass (mx.ietf.org: domain of richard@highwayman.com designates 217.155.43.13 as permitted sender) smtp.mailfrom=richard@highwayman.com
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=highwayman.com; s=rnc1; h=MIME-Version:In-Reply-To:References:Subject:From: To:Date:Message-ID:Sender:Reply-To:Cc:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=g/9MShDHSFAMMsAI84V6kgJWVGRIe39U9bsYoD4NyWw=; t=1789917858; x=1790781858; b=Al9Gp8nm9VfhWhGaHR7MbndLN4OK1ZFo2fGLF40/5zFbqiTzNl5TheDgbPSGpxWVHxmHLZ1T84/ 3fgTyXQ0Tbmf3TKe0HiHCttFxguOeDEIvKJdVYvsrSfNTKF8J5mzMUEJVqiQ94SpcP9eK7OaPi82Q OufASAM+1+RaO+aXwA4x4b7KqbkJkoki/VIW5dSgfknH7f53a9VciLPVYWdw60IBlD2LIAtZua79c /RZB0gkOxAItm2WCnuiqSzIao5BVcoW4hlfcyb9DuFWsQb5XR19wciTxblHeGTINmLzkwU9XbKxgT 8Uo6/HTwUVQYDXr05gK/gjKdod0T6/PPOYZw==;
Received: from [127.0.0.1] (port=15384 helo=happyday.al.cl.cam.ac.uk) by mail.highwayman.com with esmtp (Exim 4.98.2) (envelope-from <richard@highwayman.com>) id 1x8JOr-0000000072d-0yHY for Ietf-dkim@ietf.org; Sun, 20 Sep 2026 15:24:17 +0000
Message-ID: <EZMiwEBwp$rqFAre@highwayman.com>
Date: Sun, 20 Sep 2026 16:23:28 +0100
To: Ietf-dkim@ietf.org
From: Richard Clayton <richard@highwayman.com>
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> <CAAFsWK3t=fMTF=CfhiwtvgVER9ieyjvCwT6Um7DNYU5LFmnY7Q@mail.gmail.com> <evvENQS7G9qqFAic@highwayman.com> <CAAFsWK26ugerMCQZPwRy=ic=CKFGoaiSiLDD1KZHs4p6wCgM4g@mail.gmail.com>
In-Reply-To: <CAAFsWK26ugerMCQZPwRy=ic=CKFGoaiSiLDD1KZHs4p6wCgM4g@mail.gmail.com>
MIME-Version: 1.0
X-Mailer: Turnpike Integrated Version 5.03 M <$Bz$+TGz77$sNMKLn2S+duLd+M>
X-Spamd-Bar: /
Message-ID-Hash: Y5I5BOGBGG722Z2FTAAVNZDNAUKG3Y4H
X-Message-ID-Hash: Y5I5BOGBGG722Z2FTAAVNZDNAUKG3Y4H
X-MailFrom: richard@highwayman.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
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/x3S_jEd98TkR0wh8Vc1uSq0MliQ>
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>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In message <CAAFsWK26ugerMCQZPwRy=ic=CKFGoaiSiLDD1KZHs4p6wCgM4g@mail.gma
il.com>, Wei Chuang <weihaw@google.com> writes
>On Thu, Sep 17, 2026 at 4:42AM Richard Clayton <richard@highwayman.com>
>wrote:
>> In message <CAAFsWK3t=fMTF=CfhiwtvgVER9ieyjvCwT6Um7DNYU5LFmnY7Q@mail.gma
>> il.com>, Wei Chuang <weihaw=40google.com@dmarc.ietf.org> writes
>>
>> > Also we can require the From header to be aligned at every SMTP
>> > transaction boundary which implies From header munging at those
>> > boundaries.
>>
>> to a first approximation no forwarding system does this today
>>
>> this is not going to fly
>>
>
>Not sure which part you disagree with.
I do not believe that forwarding systems change the RFC5322 From header
field when they forward email.
Mailing lists do ... but that is because they have altered the content.
Alumni forwarders that mangle the email may do so as well ... but the
type of forwarder that just takes everything arriving for an email
address and sends it on to somewhere else does not touch the RFC5322
- From header field
> But AFAIK having DMARC evaluation
>done at i=n will require relay forwarders to always mangle the From header
>field before being sent to a DMARC mail receiver that will perform the
>evaluation.
Why would DMARC evaluation be done at i=n ... no-one has proposed that.
There is an argument for doing DMARC evaluation at the highest i= where
the RFC5322 From header field is changed. That is what systems do today
because they are unable to recover the RFC5322 From header field as it
was set at i=1
In DKIM2 a received can use recipes to recover the original i=1 RFC5322
- From header field and so it can feed that to its "enhanced-for-DKIM2
DMARC" evaluator. It can also persuade an MUA that handles the email
thereafter to display that value.
>It's possible I'm overreading the relationship
>between draft-ietf-dkim-dkim2-spec and this proposal, and if fact what you
>are proposing is to support i=1. If so, as Pietro points out, evaluating
>DMARC at i=1 can simplify this proposal.
I am in favour of the "enhanced-for-DKIM2 DMARC" and relevant MUAs using
the i=1 value of the RFC5322 header field.
But whatever we decide, the notion that every hop rewrites the RFC5322
- From header field is nonsense. Your draft says that. If you think my
- -spec document says that then please cite the paragraph and will ensure
that the text is modified appropriately
- --
richard @ highwayman . com "Nothing seems the same
Still you never see the change from day to day
And no-one notices the customs slip away"
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1
iQA/AwUBaq/6cGHfC/FfW545EQJSlQCfVzscp5GK+GdDZWMp8z46bs+SKa0AoOM7
/rUlHyds65G5CamVUWbBAhuG
=fWf3
-----END PGP SIGNATURE-----
- [Ietf-dkim] DKIM2 / DMARC Sender Policy Proposal Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Todd Herr
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… John Levine
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Al Iverson
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Todd Herr
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] R: Re: DKIM2 / DMARC Sender Policy Pr… MCN-IETF
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Al Iverson
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] R: Re: DKIM2 / DMARC Sender Policy Pr… MCN-IETF
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Richard Clayton
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Richard Clayton
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… John Levine
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Tero Kivinen
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] R: Re: DKIM2 / DMARC Sender Policy Pr… MCN-IETF
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… John Levine
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… Vittorio
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… Wei Chuang
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… Vittorio
- [Ietf-dkim] R: Re: R: Re: DKIM2 / DMARC Sender Po… MCN-IETF
- [Ietf-dkim] Re: R: Re: R: Re: DKIM2 / DMARC Sende… Richard Clayton
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Pete Resnick
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… John Levine
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Pete Resnick
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Richard Clayton
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Bron Gondwana
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… G.W. Haywood
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Bron Gondwana
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Richard Clayton
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… John Levine
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Steffen Nurpmeso
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Steffen Nurpmeso
- [Ietf-dkim] Re: R: Re: R: Re: DKIM2 / DMARC Sende… John Levine
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… Taavi Eomäe
- [Ietf-dkim] Re: R: Re: DKIM2 / DMARC Sender Polic… John Levine
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Wei Chuang
- [Ietf-dkim] Re: DKIM2 / DMARC Sender Policy Propo… Emanuel Schorsch