IETF Logo Mail Archive

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

Steffen Nurpmeso <steffen@sdaoden.eu> Thu, 01 February 2024 16:40 UTC

Return-Path: <steffen@sdaoden.eu>
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 9B88FC14F70E for <ietf-dkim@ietfa.amsl.com>; Thu, 1 Feb 2024 08:40:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 E6a8K0DXm4o5 for <ietf-dkim@ietfa.amsl.com>; Thu, 1 Feb 2024 08:40:38 -0800 (PST)
Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (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 E34C9C14F6FE for <ietf-dkim@ietf.org>; Thu, 1 Feb 2024 08:40:10 -0800 (PST)
Date: Thu, 01 Feb 2024 17:40:06 +0100
Author: Steffen Nurpmeso <steffen@sdaoden.eu>
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: ietf-dkim@ietf.org
Message-ID: <20240201164006.wLVuTVY0@steffen%sdaoden.eu>
In-Reply-To: <CAL0qLwaiYddreLQjkTXXdVKBP+sF7p2Mq9jqeQrfiX95GZRrtg@mail.gmail.com>
References: <20240201005955.nE7URvcd@steffen%sdaoden.eu> <CAL0qLwaiYddreLQjkTXXdVKBP+sF7p2Mq9jqeQrfiX95GZRrtg@mail.gmail.com>
Mail-Followup-To: "Murray S. Kucherawy" <superuser@gmail.com>, ietf-dkim@ietf.org
User-Agent: s-nail v14.9.24-596-g7894190075
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs.
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/jI3jTfwFzixbT1CSf5MnHkeHzdE>
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: Thu, 01 Feb 2024 16:40:42 -0000

Murray S. Kucherawy wrote in
 <CAL0qLwaiYddreLQjkTXXdVKBP+sF7p2Mq9jqeQrfiX95GZRrtg@mail.gmail.com>:
 |On Wed, Jan 31, 2024 at 5:44 PM Steffen Nurpmeso <steffen@sdaoden.eu> \
 |wrote:
 |
 |> But i cannot read this from RFC 6376.
 |>
 |
 |Sections 2.8 and 3.4.4 don't answer this?

These were why i was coming here.
It is one thing to write a 5322/I-M-F parser who documents RFC
5234, B.1. Core Rules "WSP", but simply skips over anything
whitespace related, effectively, but the other to digest a lone LF
or CR in the data stream.
So the answer is this they are not.

Thank you very much for this confirmation, i was very unsure.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

v2.23.0 | Report a Bug | By Email