IETF Logo Mail Archive

[Ietf-dkim] Re: Concerns about the recipe/rollback mechanism and deployment architecture in draft-clayton-dkim2-spec

John Levine <johnl@ietf.email> Wed, 25 March 2026 17:15 UTC

Return-Path: <johnl@iecc.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 7725FD153F56 for <ietf-dkim@mail2.ietf.org>; Wed, 25 Mar 2026 10:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 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, FROM_FMBLA_NEWDOM14=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="0A6+iSPs"; dkim=pass (2048-bit key) header.d=ietf.email header.b="fjQu229U"
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 ePQ8rmxXRzA3 for <ietf-dkim@mail2.ietf.org>; Wed, 25 Mar 2026 10:15:54 -0700 (PDT)
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 (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 0C61BD153F51 for <ietf-dkim@ietf.org>; Wed, 25 Mar 2026 10:15:53 -0700 (PDT)
Received: (qmail 11597 invoked from network); 25 Mar 2026 17:15:52 -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=2d4b69c41848.k2603; t=1774458942; x=1774804542; bh=oWkMKmkHa61G1t4CW3hbd4cCYbn6dNHE6SLzmLPqeeI=; b=0A6+iSPsbKrrzKs+16pFoPVdrADOJaRiEsf9LGV6mAxLvxr9Cz0cy17frc78f69ry9revtEnhoPCQtZbnU+my4VvgCd9ydikXvYDXVEk5qmh9ZGrOx+I9G/3Y26ayeRjw0053z5zbRVGyR4iqxRhT2MoK9p55JRfymdRYvt3q6SCOmywlqtk37wuZw3nwqFWnxxjFRdb8ChA5Ws9ErnatifApb3ZufsnbuYxrSz0mWEww+1sz67OZO3mTJ6uXXCQwRZoG6UnBVXPx2xcftrqp6qYk7fh24lUgBf+xey4WbtRCFP2xCZWebAqnFkaX0vi92ArGhP5EBiZXegjOHFGXg==
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=2d4b69c41848.k2603; bh=oWkMKmkHa61G1t4CW3hbd4cCYbn6dNHE6SLzmLPqeeI=; b=fjQu229UNWvTLj3yeiTI8QSU9+1txFYY4DdYrUiIhLYkTTafS9E9ygq740Ghd6M3KKJwThJb4TmDjKZEp8g6Wh2K1QD1ZWZFHsMwGGxaYKM1zbxdmpQbx5sfp/u9xR5fiEO6LN89RxAbrSZThSQpXrjY4BkZLxqkNdCoKHEtuQiKLw0fx5O0dWiFYE21az/ILOvpGy+j0ahQFmXIJDDn8lbWNq3Q8YZUdvEIoM4f1Mxt8/wLkhWQlLwWEj3+ngFJIfgdCf2GL+x5ekV/tZthENz/B9fwBSW9Zt0XYN8WOXDxw0gfv/P0bfvT4Lp+sITwcNVaTUb3mnYDtbT68fQYCQ==
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; 25 Mar 2026 17:15:52 -0000
Received: by ary.qy (Postfix, from userid 501) id 0F5B4FE90A7F; Wed, 25 Mar 2026 13:15:51 -0400 (EDT)
Date: Wed, 25 Mar 2026 13:15:51 -0400
Message-Id: <20260325171552.0F5B4FE90A7F@ary.qy>
From: John Levine <johnl@ietf.email>
To: ietf-dkim@ietf.org
In-Reply-To: <c67e862-94c7-aaac-766c-3559d0f4f2af@jubileegroup.co.uk>
Organization: Taughannock Networks
References: <e68f89452178831fca6f4137e19d4c35@itb.it> <da87fc77-cd45-41fe-be3b-8bf2477959d3@app.fastmail.com> <f2d1390155092b4b89811f5d1f98abb5@itb.it> <6f02a636-7ab4-4e7f-aa73-a4407963ac77@app.fastmail.com> <3c2db52d617020f5196b364ce60a033d@itb.it> <10178f6a-ab54-4e38-b097-8286e70bdb88@inveigle.net> <0A972C82-6808-4BFD-9A85-DB68B0155C7A@episteme.net> <9d9388135235d47df170798200655c6e@itb.it> <CAL0qLwZ8Xpe0i+EsJdPOcGYFr2TkJ7aWOV0CBQV0aq2+WAu-Gw@mail.gmail.com> <19beac01-33dc-41e0-bafd-36ceadb781eb@inveigle.net> <c67e862-94c7-aaac-766c-3559d0f4f2af@jubileegroup.co.uk>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: TWE2MRYVQ3X7HVGQBGDL3SDKJ3ED7XDB
X-Message-ID-Hash: TWE2MRYVQ3X7HVGQBGDL3SDKJ3ED7XDB
X-MailFrom: johnl@iecc.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
CC: ietf@jubileegroup.co.uk
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Ietf-dkim] Re: Concerns about the recipe/rollback mechanism and deployment architecture in draft-clayton-dkim2-spec
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/yTpL4ktKkDMwgTkhvA30RFO0ZwI>
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 G.W. Haywood  <ietf@jubileegroup.co.uk> said:
>> All approaches necessitate MTA core modifications to some extent, with some 
>> less extensive than others, but I strongly believe these changes need to be 
>> closely aligned with filters, not entrenched in SMTP itself.
>
>What do you think would need to be added to and/or changed in the
>milter protocol to implement DKIM2?

The main difference from existing DKIM is that DKIM2 needs to be able to see the envelope
addresses.  But when I look at the perl module it looks to me like SMFIC_MAIL and SMFIC_RCPT
provide them, so it should be a SMOP.

R's,
John

v2.46.0 | Report a Bug | By Email | System Status