IETF Logo Mail Archive

Re: [ietf-smtp] Stray <LF> in the middle of messages

John C Klensin <john-ietf@jck.com> Sat, 06 June 2020 20:09 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 455D93A0B3E for <ietf-smtp@ietfa.amsl.com>; Sat, 6 Jun 2020 13:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id muxIYrMqwL6O for <ietf-smtp@ietfa.amsl.com>; Sat, 6 Jun 2020 13:09:21 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30A9D3A0B3D for <ietf-smtp@ietf.org>; Sat, 6 Jun 2020 13:09:21 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1jhf83-000MYu-C1; Sat, 06 Jun 2020 16:09:19 -0400
Date: Sat, 06 Jun 2020 16:09:13 -0400
From: John C Klensin <john-ietf@jck.com>
To: Paul Smith <paul@pscs.co.uk>
cc: ietf-smtp@ietf.org
Message-ID: <BF6CF0B1838F9C073CD18162@PSB>
In-Reply-To: <31B7F8BC2C3B2436DD7D8E83@PSB>
References: <87ftb8p1ii.fsf@llwynog.ekleog.org> <1bf01c85-3276-270b-a517-70bf15e09043@dcrocker.net> <4efb92cb-9657-15eb-11f5-b6057f691505@pscs.co.uk> <31B7F8BC2C3B2436DD7D8E83@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/RnKKpHbI7bYTgjRP9pXGoVE38P8>
Subject: Re: [ietf-smtp] Stray <LF> in the middle of messages
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Jun 2020 20:09:22 -0000

Sorry, that should have been a reference to the next-to-last
paragraph of Section 8 of RFC 6409.  But the principle (and,
with the exception of handwaving about extensions, the text) are
unchanged.

  john


--On Saturday, June 6, 2020 16:03 -0400 John C Klensin
<john-ietf@jck.com> wrote:

> 
> 
> --On Saturday, June 6, 2020 19:36 +0100 Paul Smith
> <paul@pscs.co.uk> wrote:
> 
>> ... 
>> I suppose with a submission server you could be more flexible,
>> but, to be honest, I've *never* come across a case where not
>> treating a lone LF as a line break has been a problem.
>> ...
> 
> And that is exactly why the last sentence of the introductory
> paragraph of Section 8 of RFC 4409 says:
> 
> 	"Any message forwarded or delivered by the MSA MUST
> 	conform to the requirements of [SMTP-MTA] and
> 	[MESSAGE-FORMAT]."
> 
> In other words, perfectly reasonable for a submission server to
> reach a local agreement that bare LFs are to be treated as line
> terminators but, by the time the message reaches the public
> Internet, it needs to have fixed those.
> 
>     john
>

v2.23.0 | Report a Bug | By Email