IETF Logo Mail Archive

Re: [ietf-smtp] EHLO domain validation requirement in RFC 5321

Keith Moore <moore@network-heretics.com> Mon, 28 September 2020 21:41 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 0CC403A0CEA for <ietf-smtp@ietfa.amsl.com>; Mon, 28 Sep 2020 14:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.213, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 IMq_Wg4g6qoj for <ietf-smtp@ietfa.amsl.com>; Mon, 28 Sep 2020 14:41:38 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02D033A0CC3 for <ietf-smtp@ietf.org>; Mon, 28 Sep 2020 14:41:37 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 32086B3D for <ietf-smtp@ietf.org>; Mon, 28 Sep 2020 17:41:37 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 28 Sep 2020 17:41:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding: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=fm3; bh=JIJYjK5A5xUUt+xYNMc4AnuT4Mxslifyg3kRGQCZ9 fg=; b=Eek8ynET//9QgIBw0Xe6tpE1IHLidZVx1PhatYC5ax0QK207lOaw73WFj rp8CcFFwUI5XED9T+z4R8y5SRGSkJP4pcQYpP+5wyfgiYeQvMqH1I84uUjRSqHdo F61pRpf3RSIEjpvRTx/3jLIk/lHcPfF0LN+0LACfo/4p5ZrBCdKD7PL+RJy+FJ6T FFl4RZ0gaSWxJx17N/rjueRYKwqD0CcghdMjR67HoSb5uBnZhgiqt1TOcTU/Z8sT FRW0JusZaH+F67O+IpwFr5iUoEx9u6Mw8gt2QV+saNQic3gMpMoVlAwMeCwo1Rgf YJlKbHFa8JVE9pMsQuwAxpIqzNtNw==
X-ME-Sender: <xms:kFhyXz8fVNzDq0teAI8p4mWeAiI1UPGa-JFFsGr6FWnRUfSM2-GQiQ> <xme:kFhyX_sD7htNA78raKMOTClzBq536hB046sl8BAO5z3qFyn_BrrJsqXCNwdGHecLV -UxMQedmGOXJQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrvdejgddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhephefhuedtheefgf efgffhkeehgfeugfeiudeugeejkeefleelueeiffetfeeuudeunecukfhppedutdekrddv vddurddukedtrdduheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:kFhyXxCMrwi1hr6f8cQ6dpL24ioqlULoZdeNZjTtKooJJZx0QxE8_Q> <xmx:kFhyX_duOK6q-g1lis05ICqRWv6aTgiF2L8P5pE7-zgDZvKpbxjV5Q> <xmx:kFhyX4PtsJuI-YkPJhATLu563fbFqrnay5CCbCU9tflamrPtbJPVDg> <xmx:kFhyXyuyjXEi6ajupU0Ck1JpWH0-nau17_VHsxvClS3GMcGOj74kPw>
Received: from [192.168.1.85] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id DB2593280064 for <ietf-smtp@ietf.org>; Mon, 28 Sep 2020 17:41:35 -0400 (EDT)
To: ietf-smtp@ietf.org
References: <20200928142758.E9FE5229F6DE@ary.qy>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <b47992c5-17dc-f461-c1cd-1e4277f52c00@network-heretics.com>
Date: Mon, 28 Sep 2020 17:41:34 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <20200928142758.E9FE5229F6DE@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/3DGcTny8SMjitxgKXAXQxRecUVg>
Subject: Re: [ietf-smtp] EHLO domain validation requirement in RFC 5321
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: Mon, 28 Sep 2020 21:41:40 -0000

On 9/28/20 10:27 AM, John Levine wrote:

> Keith is asking us to expect that mail clients will move behind NAT64
> even while their associated servers do not,

No, I expect IPv4 to go away.   Gradually at first, and then much more 
quickly.    Are people here really going to insist that operators have 
to maintain IPv4 servers (or ALGs or whatever they need to maintain the 
illusion that the client and server see the same source IP address?).   
Architecturally it seems like an extremely shortsighted viewpoint.

v2.23.0 | Report a Bug | By Email