[Ietf-dkim] Re: removing "donotmodify" was: Call for Agenda Items: September 23 Interim
"Inveigle.net" <cs@inveigle.net> Tue, 29 September 2026 02:01 UTC
Received: from akl.inveigle.net (akl.inveigle.net [103.187.6.191]) (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 2F97D31 for <ietf-dkim@ietf.org>; Tue, 29 Sep 2026 02:01:07 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=inveigle.net header.s=thingamajig header.b=o7Td7oWX; dmarc=pass (policy=quarantine) header.from=inveigle.net; spf=pass (mx.ietf.org: domain of cs@inveigle.net designates 103.187.6.191 as permitted sender) smtp.mailfrom=cs@inveigle.net
Received: by akl.inveigle.net (OpenSMTPD) with ESMTP id 86b750cf for <ietf-dkim@ietf.org>; Tue, 29 Sep 2026 02:00:59 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=inveigle.net; h= message-id:date:mime-version:from:subject:to:references :in-reply-to:content-type:content-transfer-encoding; s= thingamajig; bh=493yWaNOL4VLcBIOxhUdu/2EribtWzTS0ppjUjYl1Kw=; b= o7Td7oWXTasduLLKzP8cJJb+wXKecREOiOU+9GxILY9il/SVDBkH4+EGGwSaLHB4 Scek3I+dtz2jK99E9NpkR9xewMb9oXEUZXxsKVwItz+1L53488d0/ZAffq4RayaK Xtx3VRyRD6drf8+UYu95p1BuXkn6aHL6qHuVAIxNz0BVXBg7movkO8k3wUYXL5Mw zpYwwidRrN8uz5gTT6M3Yj/OhCeufj/et5oTsJImeMIbJksEpUL7C5rHzSO/+GCp Jx2KEqzG4IevGj0kfVJN0c1dfJNR1kiEiYUkYx+8P9qbczH6DXX1trbbcgjlvRwz xUz+Kc1KBrdQ1Via8lnCFw==
Received: from [10.0.1.181] (<unknown> [10.0.1.181]) by akl.inveigle.net (OpenSMTPD) with ESMTPSA id 3ad1fe6c (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for <ietf-dkim@ietf.org>; Tue, 29 Sep 2026 02:00:59 +0000 (UTC)
Message-ID: <b2837906-f46a-4ce5-98e8-153229263ce6@inveigle.net>
Date: Tue, 29 Sep 2026 15:00:59 +1300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: "Inveigle.net" <cs@inveigle.net>
To: ietf-dkim@ietf.org
References: <CAL0qLwZHfgiJZ87Mn8XzFAZ=ep4TqbO--YcunvN296wpC2z5gQ@mail.gmail.com> <n4w64zBaH+tqFAM$@highwayman.com> <84803586-7186-4594-b3f7-a2d1ed15193a@inveigle.net> <Xg92uUCiOmuqFAzP@highwayman.com> <119dti4$2n63$2@gal.iecc.com>
Content-Language: en-GB
In-Reply-To: <119dti4$2n63$2@gal.iecc.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Spamd-Bar: -
Message-ID-Hash: IGT57YNG3SHFBTPX5WUUBRIFOMMRGQ7K
X-Message-ID-Hash: IGT57YNG3SHFBTPX5WUUBRIFOMMRGQ7K
X-MailFrom: cs@inveigle.net
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: removing "donotmodify" was: Call for Agenda Items: September 23 Interim
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/FgCy8wjx9aQGvIv-Z7iaqOtk8mU>
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>
On 29/09/2026 3:28 am, John Levine wrote: > According to Richard Clayton<richard@highwayman.com>: >> A very common arrangement is for the brand to set up a CNAME rather than >> sharing key material. > Huh? It needs to share the private key so the ESP can sign the mail. > The main benefits of the CNAME is that it's a lot shorter than the full > public key and so more likely to work with provisioning crudware that > can't handle long text strings, and it's easier for the brand to revoke > if they have a falling out with the ESP. Normally, only the ESP has the private key in this configuration. The main benefit of a CNAME is the ability to rotate keys without involving the customer. Neither is any more complex to revoke, but entering text fields can be a little trickier than a CNAME. Few are manually editing zone files directly these days. The difficulty comes from poor interface design and the common belief that there is a 255 byte limit on text records... crudware with a responsive UI. >> The suggestion that domain A could add a header field on a per-email >> basis that says "Domain B can make any changes to this email it wishes" >> might be workable. That is, give carte blanche permission rather than >> only allowing specific modifications. > Nobody thought much of that idea when I proposed it a decade ago. Perhaps > times have changed. I think there has been some quite significant change during that period. Senders are more aware of the need for DKIM, but not the specifics. The ill-informed may know they need DKIM for deliverability, but when informed that creating a CNAME allows a third party to sign any e-mail as if it had originated from their domain, they look very differently at the requirement. The ESP market has largely moved away from SMTP relay services, to API-based transactional e-mail. There seemed to be new services popping up every week when I was trialling these services to recommend to users. Because an API arrangement always requires the ESP to sign for the domain, use of SMTP services is often tied to DKIM-based domain verification, even though the customer doesn't necessarily want or require it. Due to the requirements of receivers, users experiencing deliverability issues feel they are being forced down the ESP route, even if they are perfectly capable of signing and delivering their own e-mail. Regardless of whatever role you believe DKIM should play in delivery, the power imbalance between senders and receivers needs addressing. Giving senders more say over what happens to their e-mail and relying less on heuristics would be advantageous. The pandemic in particular showed there was a need to support Appendix B.1 Alternate Submission Scenarios in order for e-mail to be delivered reliably. I added DKIM support to my client in support of this. I am aware of no ESP requiring CNAME record verification that caters specifically to those use cases. In terms of what this might look like, I previously proposed adding a one-time or limited public key for recipient binding independent of the DKIM-Signature. That same approach, including an Ed25519 public key signed by the (potentially PQ) DKIM-Signature, can be used to sign any additional header, including one granting authority for change to a specific domain. Regards, R. Latimer
- [Ietf-dkim] Call for Agenda Items: September 23 I… Murray S. Kucherawy
- [Ietf-dkim] Re: Call for Agenda Items: September … Wei Chuang
- [Ietf-dkim] Re: Call for Agenda Items: September … Wei Chuang
- [Ietf-dkim] Re: Call for Agenda Items: September … Bron Gondwana
- [Ietf-dkim] Re: Call for Agenda Items: September … Richard Clayton
- [Ietf-dkim] Re: Call for Agenda Items: September … John Levine
- [Ietf-dkim] Re: Call for Agenda Items: September … Tero Kivinen
- [Ietf-dkim] Re: Call for Agenda Items: September … John R Levine
- [Ietf-dkim] Re: Call for Agenda Items: September … Tero Kivinen
- [Ietf-dkim] removing "donotmodify" was: Call for … Richard Clayton
- [Ietf-dkim] Re: removing "donotmodify" was: Call … R. Latimer
- [Ietf-dkim] Re: removing "donotmodify" was: Call … Richard Clayton
- [Ietf-dkim] Re: removing "donotmodify" was: Call … John Levine
- [Ietf-dkim] Re: removing "donotmodify" was: Call … Richard Clayton
- [Ietf-dkim] Re: removing "donotmodify" was: Call … Inveigle.net
- [Ietf-dkim] Re: removing "donotmodify" Tobias Herkula
- [Ietf-dkim] Re: removing "donotmodify" Bron Gondwana
- [Ietf-dkim] Re: removing "donotmodify" David Conradie
- [Ietf-dkim] Re: removing "donotmodify" was: Call … Emanuel Schorsch