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

Keith Moore <moore@network-heretics.com> Wed, 01 January 2020 17:58 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 C33151200C4 for <ietf-smtp@ietfa.amsl.com>; Wed, 1 Jan 2020 09:58:41 -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 TiBLbeVa0pTn for <ietf-smtp@ietfa.amsl.com>; Wed, 1 Jan 2020 09:58:39 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64A6C1200A4 for <ietf-smtp@ietf.org>; Wed, 1 Jan 2020 09:58:39 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 90F1422375; Wed, 1 Jan 2020 12:58:38 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 01 Jan 2020 12:58:38 -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=l7bra6 0FDb47AmcMTOZ1+rd7x/5xp7cZ12Bd7cWGHXQ=; b=HrxLDctCi0tpFh36Eo+o7P XBTEGGPGnM3YxTAQYZSLPHtS6rMq0rYPGq4QMxgL2hDNUJb6IVtpKCJGIrG1WDrH wtsQumFOMIHESVwhzJOUFHypk2qH0i8AYcWXwFHm3L7MQGPR7qbxV7zNzNg7kJSp U8O9f/6AVtcbXZT8bc9ZtS4NfALytX1Y/MxbeBxWpYQmW//stnQqc55nXEh1l20Q 0qG9cwKeWBODqJAGFTgqohu3uQ3W4wYr7eBwXXMKaOSqL7fqLCm6mTAR2RGFeBc2 O1DD9DLIYDoGXCxIf1qcM0RP31+CwT4iYJBgERcF1nR5LC1bkiZMLN6ckyug0WPQ ==
X-ME-Sender: <xms:zt0MXiTmUC7NAKrzH9P91Pz5RwDCgra49scHv4gvxLZucPmERffWRQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvdefledguddtjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtsegrtd erredtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucfkphepuddtkedrvddvuddrudektddrud ehnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghr vghtihgtshdrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:zt0MXlYQBhYtF8HCnEDP_PnSiJpOopSbTFXdLjQb78XPICMADaUUMQ> <xmx:zt0MXnPKwkXHoIrEqBbBSOcxc6B60byvZTTL7j_gsbCJd3-HnYi7cw> <xmx:zt0MXmNR_-ObPxhRD4OQm-AAHXOUMd5Xzs0Lhge5fgKUbtC45zsdTw> <xmx:zt0MXuPq6ML9z1EO0O_d5JXTO0ayfj3C9vlEJ2EXNhs51F1s-S9LfA>
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 B686480059; Wed, 1 Jan 2020 12:58:37 -0500 (EST)
To: ietf-smtp@ietf.org
References: <20200101175510.8549A11E2905@ary.qy>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <8820eca1-c17d-0821-5fe4-8a46c22a3e7b@network-heretics.com>
Date: Wed, 01 Jan 2020 12:58:36 -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: <20200101175510.8549A11E2905@ary.qy>
Content-Type: multipart/alternative; boundary="------------9F4A9B0260D7483B368DCC17"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/1A5Za-LrhM-zACbS52jEPIUBXgU>
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: Wed, 01 Jan 2020 17:58:42 -0000

On 1/1/20 12:55 PM, John Levine wrote:

> In article<dfa17007-a637-88d8-339c-a6225b1648c5@network-heretics.com>  you write:
>> (I do also wonder how many existing SMTP servers can handle TLS with
>> client certificates, because that seems like that would also be a
>> recommendation worth considering.)
> Several, as noted, and there are some old patches for qmail to do it, too.
>
> But once again, this is submission, not SMTP.  A client certificate is
> a plausible way for a submission client to authenticate itself to the
> submission server.

Agreed that client certs can be useful for mail submission 
authentication.   But I was wondering about the feasibility of migrating 
to use of client certificates for relay to mail exchangers, i.e. across 
administrative mail domain boundaries.

Keith