Re: [Ietf-dkim] Question about lone CR / LF

John Levine <johnl@taugh.com> Fri, 02 February 2024 04:34 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf-dkim@ietfa.amsl.com
Delivered-To: ietf-dkim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EACF9C14F61A for <ietf-dkim@ietfa.amsl.com>; Thu, 1 Feb 2024 20:34:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.858
X-Spam-Level:
X-Spam-Status: No, score=-1.858 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="omC33Taw"; dkim=pass (2048-bit key) header.d=taugh.com header.b="Jl7DSuCa"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GHgMmR9Rk3us for <ietf-dkim@ietfa.amsl.com>; Thu, 1 Feb 2024 20:34:50 -0800 (PST)
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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08A88C14F601 for <ietf-dkim@ietf.org>; Thu, 1 Feb 2024 20:34:49 -0800 (PST)
Received: (qmail 65706 invoked from network); 2 Feb 2024 04:34:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=100a865bc70e7.k2402; bh=tfzYa8oG1UiPb+4XXwo9AW1o1A8cuSPyUixFBy3BB/0=; b=omC33Taw1A2RdEnk0LkXkepMnxA8rrfQmh4O1PiosHc3TZlzD1JYNC7iHEfJabDsNDYsB/87wFdDMtyHUsgc9eCkuApgKAzFROJkYlYPvQ6cik2A/7jeVSjhxNxN6crnMYlh8hEgoeabyDS621EWaecMfzYNmk9797f1fx6PYgf6zpZr5Se/iiee1Xpx5oe+e31M7xnOODeeLcuEu1mPUPrpTlpzIzv/btc6uXlVSeduiXTYXks4Uykil+5Tn1SjD/ppCG2Nkh6z6Ii2Ce9S8IXGo8aflkCeXEdTPhWBtwqX7MRoWSqi7PU502rwyzPAK0ARQkV4ix3lOmsgiVqcFA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=100a865bc70e7.k2402; bh=tfzYa8oG1UiPb+4XXwo9AW1o1A8cuSPyUixFBy3BB/0=; b=Jl7DSuCahO3DMuJpb+7XWyfjM6hhO8GRUuN1606x/Ol1Jz0TbeZ2SlyUB1IYRdsAs9XQdasjIE2yKfze9Jxu7yafBrwrie+u03qxQ0+pF3T6y6mgN9REmVbzoTsplB6u6Qr622Q+mibmtoj54mW5V5v6EYrGjju5NcUqmHD43izLhk0X2k/TY4l00WOBgkJ2KpcI8vj4Hj8hPZQFwtOmFl+yUeO4txGX9lwgZ1TCbYmNTS3FwowHKhleHPSC6K6IGLl6KJjiO+6WToCSkI9Bbk27/ZOUk5PcCmobJsYETFgPBs3vY4iI0hONAhkNxaWiTQyr4Qzw8EONEVdY4bgohw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 02 Feb 2024 04:34:47 -0000
Received: by ary.qy (Postfix, from userid 501) id AAF26820F0AD; Thu, 1 Feb 2024 23:34:46 -0500 (EST)
Date: Thu, 01 Feb 2024 23:34:46 -0500
Message-Id: <20240202043446.AAF26820F0AD@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-dkim@ietf.org
Cc: dcrocker@bbiw.net
In-Reply-To: <4b2babc1-5c83-4e4b-82f0-76c2763dbaa3@dcrocker.net>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/L9robvI1LoIX1Is95MNxa-0Smk4>
Subject: Re: [Ietf-dkim] Question about lone CR / LF
X-BeenThere: ietf-dkim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim/>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Feb 2024 04:34:55 -0000

It appears that Dave Crocker  <dcrocker@bbiw.net> said:
>The prohibition is not in DKIM. So the violation is not within DKIM.  
>And why should DKIM care?

RFC 6376 says what to do with 5322 messages. It says nothing about
what to do with blobs of bytes that are sort of like but not quite
5322 messages. It even has a few places that remind us of that, e.g.,
in section 5.3 it reminds us that if the local file convention uses
just CR or LF, change them to CRLF before doing anything else.

I can see that you have strong opinions about what a DKIM verifier
should do with those non-5322 blobs, but I don't see what the basis
for that is, and for that matter, I don't really understand what you
expect code to do with them.  Why is "stop and report failure" any
less valid than anything else?

R's,
John