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

Keith Moore <moore@network-heretics.com> Thu, 02 January 2020 19:34 UTC

Return-Path: <moore@network-heretics.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 C127A12010D for <ietf-smtp@ietfa.amsl.com>; Thu, 2 Jan 2020 11:34:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 LYnEuDiMOuPJ for <ietf-smtp@ietfa.amsl.com>; Thu, 2 Jan 2020 11:34:17 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C21F51200D6 for <ietf-smtp@ietf.org>; Thu, 2 Jan 2020 11:34:17 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 0696D8FE; Thu, 2 Jan 2020 14:34:16 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Thu, 02 Jan 2020 14:34:17 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=XWxn3S fdQtmpjs9YiWBg/yUdYOHS2j5wY0zV8cEptzc=; b=hveFH5A/p8c5brl92kAwMr 761LRpJvYIomB4VbA2B5IrrdrcS/1NMc4GmJUBgF4lEphTFdjN/dX2fWKlAUVtDp ssoIc+MHk7YLXFvJNwLtBgM8YA6EPGpkWAdZTctiQK8bz0tGJBOWKHKeWIIJ+IUG K2z9SncbUs1j8OBkKOPlC8V1EXS4B0Q3R37ZTHIlTyHUJCQiHsIORCWwc27Irl6P OftVVATkOB9kir+pHDCyboTUQDvHcma4j/JtBxhAv5zv7EY1n0dyY8V1YBf8l1Wl Gqr2m8d48mOew/aC3Z6C+5ODAlB5xdbwOz3vHWrshyefh7KElnGCUdWWCNyn342Q ==
X-ME-Sender: <xms:tUUOXoC2rYHfjwmOvdhDKhxuM0nhaUcu3Yy9er_aK2cMNDxf9xHqVA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvdeguddguddvjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtsegrtd erredtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucfkphepuddtkedrvddvuddrudektddrud ehnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghr vghtihgtshdrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:tUUOXnMv4fNnwNUDf2RElmCqYTrKr0TDfId-lJ-_fYWFhuhrr8VsRg> <xmx:tUUOXsD44J7H3MCjuMgI4x9EBr1LfD0JrWQ7AUUhzEEkCaBn0laGPA> <xmx:tUUOXlWFgvppvltc9ZjZLdZeXvg-dMD2_ujZkQVoqCHFEFsqVaEx0g> <xmx:uEUOXtTe1DjhCbVHtMaKHkBryMAKQhtIviCiySDdK5P_4hyr5uYDYg>
Received: from [192.168.1.97] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id B75B430600A8; Thu, 2 Jan 2020 14:34:12 -0500 (EST)
To: dcrocker@bbiw.net, ietf-smtp@ietf.org
References: <20191230013034.2C3E111D376E@ary.qy> <f894c448-ac91-6d27-98d6-0803de4ea535@network-heretics.com> <alpine.OSX.2.21.99999.374.1912292129450.44159@ary.qy> <d3dc48b0-332b-c2fe-704a-d6dc69eb5424@network-heretics.com> <5E0B8658.2060703@isdg.net> <fc8d4d71-39a4-6ca0-608a-d2113b206c5f@network-heretics.com> <5E0E10AF.30808@isdg.net> <3a106d9d-7be9-f6d4-b6e6-0103372ae227@network-heretics.com> <de71c2ed-adb6-7cf7-8f6b-a933677dc89f@dcrocker.net> <ddad210b-90b7-1e51-281f-5fcca6c31ac0@network-heretics.com> <ce552773-c8d9-28a4-040d-7efad31fa51b@dcrocker.net>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <260da20f-454c-2368-c9c4-02e5a94b9c7b@network-heretics.com>
Date: Thu, 02 Jan 2020 14:34:12 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <ce552773-c8d9-28a4-040d-7efad31fa51b@dcrocker.net>
Content-Type: multipart/alternative; boundary="------------7ED06B7D1AC5233C7B7CAA4F"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/Kb23Ntk-FgnkviYXMEqdjvAec3w>
Subject: Re: [ietf-smtp] Possible cont4ibution 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: Thu, 02 Jan 2020 19:34:19 -0000

On 1/2/20 2:08 PM, Dave Crocker wrote:

>> I mean a server that accepts incoming mail on behalf of a mail 
>> domain.  Normally they are advertised using MX records.  Sorry if 
>> that wasn't clear; I thought "MX server" would be an unambiguous 
>> shorthand.
>>
>> To me the point at which a message crosses a boundary between mail 
>> domains
>>
>
> ahh.  ack.
>
> You meant something like: "the sequence of hops starting with the MSA 
> and ending with the receiving MTA at the destination site".

Actually I was trying to focus on the single hop between the last MTA of 
an originating domain and the first MTA of the destination domain.

> I'd misunderstood and thought you meant that the MSA interacted 
> directly with the receiving MTA. 

That is possible (and in some cases desirable IMO).   But it's neither 
required, nor what I understand to be typical of today's operations.

(At the same time I question the assumption that all uses of IP address 
literals in EHLO can reasonably be confined to submissions.)

Keith