IETF Logo Mail Archive

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

Dave Crocker <dhc@dcrocker.net> Thu, 01 February 2024 20:52 UTC

Return-Path: <dhc@dcrocker.net>
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 9E842C14F6FB for <ietf-dkim@ietfa.amsl.com>; Thu, 1 Feb 2024 12:52:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=dcrocker.net
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 go0YapkmvcY4 for <ietf-dkim@ietfa.amsl.com>; Thu, 1 Feb 2024 12:52:05 -0800 (PST)
Received: from hedgehog.birch.relay.mailchannels.net (hedgehog.birch.relay.mailchannels.net [23.83.209.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5CEFC14F5EE for <ietf-dkim@ietf.org>; Thu, 1 Feb 2024 12:52:04 -0800 (PST)
X-Sender-Id: hostingeremail|x-authuser|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id D289D803CDE for <ietf-dkim@ietf.org>; Thu, 1 Feb 2024 20:52:03 +0000 (UTC)
Received: from uk-fast-smtpout4.hostinger.io (unknown [127.0.0.6]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id E99E5803B03 for <ietf-dkim@ietf.org>; Thu, 1 Feb 2024 20:52:01 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1706820722; a=rsa-sha256; cv=none; b=EvhyiB8m2b3sezmm+yFqhM0iZpL6jHEDUO8Cp1WsNNsCUtCT1sbVhiF7nejy+zqPWviRgj cfnsBIpwz85zNm/tIQwbtblDYVQkoMeZmowOW17T+UGIqFah+n61RlOZXrvX/T+Wf0W33W zTHlS9gDLL0/3Pp/U1h8mfGv49OWgQuqWUkhERdeEVuh+Qz/ttlnNsiiggS7GCr030uRci zk0nNwCrmEkkfjZ10Zg0k6n6sPKk4+pFAg7z9AjYTb6cwDZGI6ktDPtTOkc9Jtr7AtRGzc oPQN4AD+i45LhOCn9ASsJdAT7T85ydPs8U5u32FUCH+jri9w8RPQuP2V9i6R8Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1706820722; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:dkim-signature; bh=FDw0szb3RZGr2UPSk4hp6eH8wkUuGHpcbWChgY245QM=; b=niwRcRHdkb7WsEjEzhnwiMGI7GMOZsxqw024eYCTg/SdbWoSNOVIKLcpOyhH1ItGX4X/qP AfFfuLdmRoewXCmgU8nQhS/TuTkQiRO/fomlmNaaZee6/Pqk0wjl/pWFAOJ9YPm6usPzX9 Pzi9rHPbMtquXvFzjTnFUd2n9rihSpIoWGelOj4Wrh3/Y+RNPHMhrVqZa4q9PA/f6R1qyw KRwhiyLqyt1j6mVsdbyIzuFctdFQ/BySCC0XU1yfdiTk1qqwmFM+C8U/Q/HvJyx/BKk18u gQxGXYjH8S60DHrNZxI0XOcdF56SX8X7Vs/wMb3cHOUy81y6xJFz4G1izmDmfA==
ARC-Authentication-Results: i=1; rspamd-55b4bfd7cb-wlhgf; auth=pass smtp.auth=hostingeremail smtp.mailfrom=dhc@dcrocker.net
X-Sender-Id: hostingeremail|x-authuser|dhc@dcrocker.net
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authuser|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Broad-Broad: 195351fe67b7832a_1706820722455_1575215791
X-MC-Loop-Signature: 1706820722455:3161511834
X-MC-Ingress-Time: 1706820722455
Received: from uk-fast-smtpout4.hostinger.io (uk-fast-smtpout4.hostinger.io [31.220.23.38]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.109.86.237 (trex/6.9.2); Thu, 01 Feb 2024 20:52:02 +0000
Content-Type: multipart/alternative; boundary="------------HxmK4IAoyNWKLMKCVsaIoOhy"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcrocker.net; s=hostingermail-a; t=1706820719; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=FDw0szb3RZGr2UPSk4hp6eH8wkUuGHpcbWChgY245QM=; b=DfZFewhOewUa8XSMHNliHH1qytEto0waNWaOmOMARKLXVimI0vYbYHd/9BX417GkpQG8AM R8L+PNphI6c8Fp2PEan8SG/37tbyeSWlWK7Lj54ki94QbJJqF6gaSFAuDIh3L3FA49Znld v2wpGx/7mcpK074iehWJFpHiKwFh3z8/E4DX76BBq9f81nzamc44uj3rH8AfjLZTBMPRZd 2CV6HV31KGD925TANgicnCo9OSUZIYs7O6J37pLHTM6rivbV5l22pRKrAe2HPfsaR+3KC+ ixjxZ5n/YiuKfZK3ofwgAFng4ogBjsCOF7l9WVUI8fsjqoT9BJpa4qbmeKE2ag==
Message-ID: <95f2ba17-a81e-4adc-97d0-6c7387ade5f5@dcrocker.net>
Date: Thu, 01 Feb 2024 12:51:58 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Reply-To: dcrocker@bbiw.net
To: Jon Callas <jon@callas.org>
Cc: ietf-dkim@ietf.org
References: <20240201180340.852B6820560B@ary.qy> <E8C1422D-4A9C-412A-BF5E-D07CABD2BFE2@callas.org>
Content-Language: en-US
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
In-Reply-To: <E8C1422D-4A9C-412A-BF5E-D07CABD2BFE2@callas.org>
X-CM-Envelope: MS4xfNnS5mrcjkgOeXNEasj4j/SaoNkNZUAxJFndsUJh1C/rQvQt1l12IweLHGQ9qjR5rjhVVedwhl5lX1sicYa7JSWZcc5UXaqeqfY3KlvkNHNP1Yzt+gLF fTTe0pOjqDLT0FliNfTIS5pDGBasiTF5l5XK0ntE2+m8gmy2vuV7BiaqP0yKs9CP4KXuYoOGFVv6I6LXE9y7Qc+8qA0rj9edqrY=
X-CM-Analysis: v=2.4 cv=RsPDLjmK c=1 sm=1 tr=0 ts=65bc046f a=+kgR5M8LJXiVXXtdxEupWA==:117 a=+kgR5M8LJXiVXXtdxEupWA==:17 a=r77TgQKjGQsHNAKrUKIA:9 a=k7Ga1wGzAAAA:8 a=Gw8dODc7563fop5eHwsA:9 a=3ZKOabzyN94A:10 a=QEXdDO2ut3YA:10 a=WWphp1IlAAAA:8 a=SYVeg2sfhFScj2tVakUA:9 a=Rj2jkZBzbGGK-KKm:21 a=_W_S_7VecoQA:10 a=lqcHg5cX4UMA:10 a=ijMaxGghyylP-n2pFjDB:22 a=y63BXlxotgJeFQvDPf5N:22
X-AuthUser: dhc@dcrocker.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/bFTQ0BF0NvEDGDu74GXAG8bJHu8>
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 20:52:10 -0000

On 2/1/2024 12:28 PM, Jon Callas wrote:
> So that gets to the tacit question -- what should a DKIM implementor do? Me, I would*not*
>   put in code looking for bare CRs or LFs. My major rationale is an
> appeal to layering, or bluntly, it's not my job to enforce RFC 5322
> syntax. Someone else in the pipeline is supposed to do that, and all I
> can do is screw things up.

This.

A 5322 processor gets to decide what is a valid message.  That's not 
DKIM's job.  And DKIM has no inherent reason to care about CR or LF on 
their own, as distinct from any other character on its own.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net
mast:@dcrocker@mastodon.social

v2.23.0 | Report a Bug | By Email