Re: [ietf-smtp] Possible contribution to moving forward with RFC5321bis SMTP

Viktor Dukhovni <ietf-dane@dukhovni.org> Fri, 27 December 2019 21:08 UTC

Return-Path: <ietf-dane@dukhovni.org>
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 EDB4D12006F for <ietf-smtp@ietfa.amsl.com>; Fri, 27 Dec 2019 13:08:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 Vwbrx4vrA9Nv for <ietf-smtp@ietfa.amsl.com>; Fri, 27 Dec 2019 13:08:33 -0800 (PST)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C26112002E for <ietf-smtp@ietf.org>; Fri, 27 Dec 2019 13:08:32 -0800 (PST)
Received: from [10.200.2.180] (sdzac10-108-1-nat.nje.twosigma.com [8.2.105.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by straasha.imrryr.org (Postfix) with ESMTPSA id C3D62299F81 for <ietf-smtp@ietf.org>; Fri, 27 Dec 2019 16:08:30 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\))
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <C620BDD6C0C346E6E9651168@PSB>
Date: Fri, 27 Dec 2019 16:08:29 -0500
Content-Transfer-Encoding: 7bit
Reply-To: ietf-smtp@ietf.org
Message-Id: <ABD7357F-D6B4-4E0A-807A-90DCBD6DB5CB@dukhovni.org>
References: <FCDE38AEA7DDB9BB0FB206F9@PSB> <0605ee67-86eb-3e27-26b0-7a1c16a37bee@tana.it> <553FE6792AFBD83DA7DFE7F0@PSB> <2BB1805D-05F3-47B6-9897-45C4AE05EB08@dukhovni.org> <C620BDD6C0C346E6E9651168@PSB>
To: ietf-smtp@ietf.org
X-Mailer: Apple Mail (2.3608.40.2.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/G9cdD17O4tEPCRQAQ5fIYFM39xk>
Subject: Re: [ietf-smtp] Possible contribution to moving forward with RFC5321bis SMTP
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: Fri, 27 Dec 2019 21:08:35 -0000

> On Dec 27, 2019, at 1:42 PM, John C Klensin <john@jck.com> wrote:
> 
>> It seems that the -02 has not yet been uploaded, did you mean
>> for it to be already available?
> 
> Sorry... meant -01.  Been thinking about and working on -02 too
> much.   It should be up in the next couple of hours.

Thanks, I see it now.  Thanks for including the "552 -> 442" issue,
much appreciated.

I'd also like to see a similar placeholder for clarifying the semantics
of a "554" greeting.  Is the client expected to immediately bounce the
message, or look for a better MX host?  The spec is not clear and
implementations vary.

Past behaviour by some MTAs (returning a 554 banner under load) made
the second choice more appropriate, but I've not seen recent reports
of whether that's ongoing.

More recently some users are running into policy-based 554 greeting
rejects, and don't want to keep retrying message that will be
consistently rejected.

I'd like to know which is the expected client behaviour, and which
is a work-around for particular unexpected circumstances a client
may encounter.

-- 
	Viktor.