IETF Logo Mail Archive

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

Keith Moore <moore@network-heretics.com> Thu, 26 December 2019 19:23 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 5B3851208FA for <ietf-smtp@ietfa.amsl.com>; Thu, 26 Dec 2019 11:23:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 VDLiUXinTUqA for <ietf-smtp@ietfa.amsl.com>; Thu, 26 Dec 2019 11:23:44 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEBA9120884 for <ietf-smtp@ietf.org>; Thu, 26 Dec 2019 11:23:43 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id E54C421E92; Thu, 26 Dec 2019 14:23:42 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Thu, 26 Dec 2019 14:23:42 -0500
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=fm1; bh=R7rcqLYPDLqUVgMEZO8hmmyI9ENTcXlv9UHL85A50 xE=; b=kqncJbPqA7FVfTYrNhtQOZsT+G8/nvZT9hIXW4R3iPrN5R+gkXjnoy4AH vXdrDv4ufz7g+M9MEkC3375NJglp+7UJzaQ7RhSpO1+oqXMOWntfKJqYtBL0Wbij Tid/zPOBA3yGbYHk0l7kdY8hgWSewQSpdyESlfGZiyLBZjuUncOIxxQqiOQGsmJE YE6pDNc6Ci+X91frI1pWCBVK2fan7tqdpKSJSr4LLNHYQA0q2swiYqWN7E6P8GOl KplLGm5W5sqJINvgleI6S5OPRa3x9A4ADObChXdXqHkv4hurtyiQtnTNEREh4LDA YdYrK6pyrVcEfKDxRU3RbXXJJar1w==
X-ME-Sender: <xms:vggFXsCx-QgHdMpQIVxUMOOJT5h8FcZtfhMZvBYhDhSfHcQWl3GTNA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvddviedguddvvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesth ekredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecukfhppedutdekrddvvddurddukedtrd duheenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgv rhgvthhitghsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:vggFXtU6ytalC6SlFNPl8FffKyDw1-qYVNPhdP3kRM00EYKDNHrd3A> <xmx:vggFXqTlRYT8STXHnpguzlT2pdUX3JbdgCqjDo9m02M2UludcHGImA> <xmx:vggFXp2RnggvDjEspULRY7K1evqYi-kMQCQSyWX69-vux7VVQOBbYQ> <xmx:vggFXvg3Few7V2zD0H0CIIRlkpMz5XuL1dpIftPGBS_5Bn9ddf3cLA>
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 4ED64306080E; Thu, 26 Dec 2019 14:23:42 -0500 (EST)
To: ietf-smtp@ietf.org
References: <FCDE38AEA7DDB9BB0FB206F9@PSB>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <0cbf23be-dbfc-f78f-8e63-d92d6e34fbf0@network-heretics.com>
Date: Thu, 26 Dec 2019 14:23:39 -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: <FCDE38AEA7DDB9BB0FB206F9@PSB>
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/99caZBE_yvVJMiD1D4kkDE_EC8Q>
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, 26 Dec 2019 19:23:45 -0000

John,

Just to clarify my point-of-view, I don't see the recent spam 
discussions as resulting in significant new text in RFC5231bis. What I 
imagine for RFC5321bis is at most some very slight tweaking of the 
wording.    As far as I can tell it was just a coincidence that the 
issue with the IETF MTA cropped up at about the same time you started to 
ask about 5321bis.

Keith

v2.23.0 | Report a Bug | By Email