Re: [ietf-smtp] Endless debate on IP literals

Keith Moore <moore@network-heretics.com> Wed, 01 January 2020 16:30 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 0B188120045 for <ietf-smtp@ietfa.amsl.com>; Wed, 1 Jan 2020 08:30:31 -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 GFyf8_sMfAIU for <ietf-smtp@ietfa.amsl.com>; Wed, 1 Jan 2020 08:30:29 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB01A12000F for <ietf-smtp@ietf.org>; Wed, 1 Jan 2020 08:30:29 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 79A852239B; Wed, 1 Jan 2020 11:30:27 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 01 Jan 2020 11:30:27 -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=cY5o/R9IqsrdjeO2y7MT+urhZeClr5bdtEV1ACeFZ 30=; b=cy+QlZof9Tt2Vd0ZHEEllrUKVccYGBecFDSZTsxRTe+Yb4u6gHZR4Zbkg jv223b6PigDmtnZx7iJTERkU8KPMmQUPg38arII8rhlJvOcW6UDomIECuG9kUcLi u/bBxH0I13FsIqsob39XWvxWfT8InD3a2zwFVENirNrNhKkD/g4WPgEki5LHFrX6 OC7jcbiHaNyZuU+F1EGPILu9hk1sSdayoOnTc1Sk1iXNrWGgtfbCcohAj1Np2x+c KQjyTf7wTeNp9ZS8b/TBTAkge9SbC3dU0WfrJR4KskWHPPw5s9o9fK1lmqDXoHGu RTDTOD+rmLGwPaXXEGwejVMpXqerA==
X-ME-Sender: <xms:IskMXqIe7Hmuf2qELfblNtHCDajv4T2ATMunePrCEfJFVLqeu5ISlA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvdefledgkeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtke ertddtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucfkphepuddtkedrvddvuddrudektddrud ehnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghr vghtihgtshdrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:IskMXlaPyJPcWdIcVt1vBA-NYZoAFR24781GO9Beicn_ghRp4jKGjw> <xmx:IskMXiMol1icw_pG4rPeaE6mVuC2O8vDtri9nBwu0dnePRY94TZ0Ew> <xmx:IskMXtCbxOLhHvQR45FQQX0HpbCBKjtVGJlUGVXaa4BGBQitNTmr4g> <xmx:I8kMXlPoTUk_kRIm8-ta_aGebCSJP-UjnleCdIZLEPEW052QnoWezQ>
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 7ACA680059; Wed, 1 Jan 2020 11:30:26 -0500 (EST)
To: ietf-smtp@ietf.org
References: <alpine.BSF.2.21.99999.352.2001011101090.45428@gal.iecc.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <482744ba-3a37-1fd8-48dd-0d8f58524abe@network-heretics.com>
Date: Wed, 01 Jan 2020 11:30:25 -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: <alpine.BSF.2.21.99999.352.2001011101090.45428@gal.iecc.com>
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/ou2hdJ06_6_EU5sP4yOvCGakyp8>
Subject: Re: [ietf-smtp] Endless debate on IP literals
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: Wed, 01 Jan 2020 16:30:31 -0000

On 1/1/20 11:01 AM, John R Levine wrote:

> I'm thinking, for example, of DMA (Dragonfly Mail Agent), a small
> almost MTA that I use on my small server boxes.  Even though DMA can
> technically do all the things that 5321 says an MTA is supposed to do,
> I have it configured to relay everything to the submission server on
> my real MTA rather than trying to send mail directly. 

I've been wondering if there's a need to talk about (for lack of a 
better term) "pre-submission relaying" which happens when a message is 
(for whatever reason) not initially submitted to a real submission 
server that does whatever sanity checking and fixup are needed to make 
the message suitable for relaying into the global email system.

The next thing I wonder is what port should be used for pre-submission 
relaying, or whether there should be a separate port for that, or 
whether there's a need for in-band signaling to tell an MTA which role 
it is supposed to play for a particular transaction.   (Somehow I don't 
think yet another port is a good idea, as I suspect that it just has the 
effect of giving people more confusing configuration choices to make).

But part of the notion of submission is to do all of that fixup in one 
place, so you don't have multiple MTAs in the signal chain mucking with 
the message.   It would be convenient if that fixup were unambiguously 
to be done at the first hop, but it seems that we might not have the 
luxury of being able to mandate that.   So to my mind the question then 
becomes, how do we unambiguously indicate where that fixup is to be 
done, so that it is only done once?

Keith