[Ietf-dkim] Insisting that From is authentic

Richard Clayton <richard@highwayman.com> Mon, 31 August 2026 14:33 UTC

Return-Path: <richard@highwayman.com>
X-Original-To: ietf-dkim@mail2.ietf.org
Delivered-To: ietf-dkim@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 1336E13241B3C for <ietf-dkim@mail2.ietf.org>; Mon, 31 Aug 2026 07:33:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1788186837; bh=ptRe+onkMyH3fGLNXI+EGTIAEhx3l/Zk3x+rt1NpI0w=; h=Date:To:From:Subject; b=mmRYY5KN1pw4HCduHHYEdPc4nWouTJTCCEHJ30tHkW/5s8ng8SYGIuMm+m1LmU7FS wVbfgABez8bTErixxX4LZAEvSvQRijIva/j3NeCqEFUOiYWD+l5WT2SPNKza+VK4Zk Lqw+QO0Hs+dub17DFtkHcg6u3WURu34IWZDkz6+k=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=highwayman.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K2OpFs8tKWql for <ietf-dkim@mail2.ietf.org>; Mon, 31 Aug 2026 07:33:55 -0700 (PDT)
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 (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D0C9F13241B37 for <ietf-dkim@ietf.org>; Mon, 31 Aug 2026 07:33:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=highwayman.com; s=rnc1; h=MIME-Version: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:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=zFyvCkFM7ZZnse7yG6m5qix1QtVfDgosDMDofWsXVPs=; t=1788186835; x=1789050835; b=pc+wFqkNa5ulZbvCdQfHwyhoVvTcy9e3VrIIiqpj1hWRs63fDONXw8MF0AgxsC9k4uDGRSSJkWG 4diidTMNbj9xkyzzo94nDXxPD2ThE9Vtj5UL37Hcj/yqq6snDJjAd/5FITFexU6xL1hjclDY7hQD0 +v997iN4QQeswsqQeZuhGQ2hHYlfOP9gK5GlGI7C41jN1tAPbhZ6xjUuCivfeyq17TdzUgMMvYkIX GwQLDIkdWdZR5D9JcTA/e+zkYQexIjNpicdXRQhYN5SRoiV59JuQNSFa+ntHWw1QTd6TISrIWpH2l mAMOb47iDT1QzVajkDbtDqRazGwkf9pQPQ6Q==;
Received: from [127.0.0.1] (port=17328 helo=happyday.al.cl.cam.ac.uk) by mail.highwayman.com with esmtp (Exim 4.98.2) (envelope-from <richard@highwayman.com>) id 1x1358-000000009kq-3lrs for ietf-dkim@ietf.org; Mon, 31 Aug 2026 14:33:54 +0000
Message-ID: <dfeERMCCCZlqFAY$@highwayman.com>
Date: Mon, 31 Aug 2026 15:32:34 +0100
To: ietf-dkim@ietf.org
From: Richard Clayton <richard@highwayman.com>
MIME-Version: 1.0
X-Mailer: Turnpike Integrated Version 5.03 M <DY2$+3bv77P9oPKLyKb+desIVt>
Message-ID-Hash: SOYL3YOW5RWOGA3H7EMTJDTKF5D6CQDO
X-Message-ID-Hash: SOYL3YOW5RWOGA3H7EMTJDTKF5D6CQDO
X-MailFrom: richard@highwayman.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-dkim.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Ietf-dkim] Insisting that From is authentic
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/HpoxBmsOxLlZ6L_PxlnRR6DjLz8>
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


Several people have spoken up about the interaction between DMARC and
DKIM2 -- and the issues that arise when the RFC5322 From header field is
changed by an intermediary.

There is a straightforward way to address this -- which I would commend
to the working group.

We update the spec to say that when a From field is first placed into a
message (ie it sits alongside an i=1 DKIM2-Signature) or when it is
changed by an intermediary (there is a recipe that shows that it has
been changed at a particular hop) then DKIM2 will insist that there is
match between the d= domain being used to sign and the domain in the
RFC5322 From header field.

The appropriate match would seem to be the "relaxed" match described in
#9.4 .. viz if d= and the domain in the RFC5322 From header field are
not identical then remove labels until the values are identical or until
there are no labels remaining in which case there is no match.

Since in the real world no-one can sign for .com (or whatever your
publicly used TLD may be) this is just as safe as the MAIL FROM match
already required (and we don't need to wander into the world of tree-
walks or the PSL).

Since this fits with what a number of people have been asking for,
unless there is outrage (or an important use case where this would be
impossible) I will put appropriate text into spec-07 so that the detail
of the wording (rather than just the concept) can be considered by the
Working Group.

- -- 
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/AwUBapWQgmHfC/FfW545EQIf0wCgjNlZqZ19T/R52pHjBh5PXsXeBSQAn1ya
ypqXc1AYxPSFiM+YIThRE5Dq
=iOeT
-----END PGP SIGNATURE-----