IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Wed, 01 January 2020 17:55 UTC

Return-Path: <johnl@iecc.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 56B561200C4 for <ietf-smtp@ietfa.amsl.com>; Wed, 1 Jan 2020 09:55:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=FAzOaMvQ; dkim=pass (1536-bit key) header.d=taugh.com header.b=Lpf7DitG
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 b1cuXmYIy31m for <ietf-smtp@ietfa.amsl.com>; Wed, 1 Jan 2020 09:55:12 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48AA21200C3 for <ietf-smtp@ietf.org>; Wed, 1 Jan 2020 09:55:12 -0800 (PST)
Received: (qmail 67461 invoked from network); 1 Jan 2020 17:55:11 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=10782.5e0cdcff.k2001; i=printer-iecc.com@submit.iecc.com; bh=34k5SghcQ9PRT02DkkDMEiWmoDZk1fo6bvjApqTNv0A=; b=FAzOaMvQmYCl00mONaHjwSgtbcuwo3UdrI/KuWzwr27Zg7c+VCdynsQX6Y5HLNrt5lr/tkMwqkkHDgIjWDNTpVV4SYGEvqFKDF/+Kfr9Lw4tguxvyb7aoHR0pVw2Qhtsx52fFK1mqQp43NwDtBaREwt6nJajptk7QBAyZ+FaWljkGJWijycOJtEBCMC7UI5HORu03fplzOigB5htrPnr6Sin7SGgofH2DDzrqP8aal4jGxWC9/iyVUUAWk06rsZl
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=10782.5e0cdcff.k2001; olt=printer-iecc.com@submit.iecc.com; bh=34k5SghcQ9PRT02DkkDMEiWmoDZk1fo6bvjApqTNv0A=; b=Lpf7DitGx/rqBkZhz3YMog5mt5MUNCKYTITkRXMzYm2xqtnoFWdUabOdciRnC0zSpiyhgdzanPdJYLSHXyrDswttxqIrfXeARyJg0LdJa8WnWDYFaxCeJNn+tO32PKuFJMe3fiewY9c7YXqtmPUSieloiQvZUie2td1AyEK/Zyf0D4LN21NC2kk8gCoHhvpuqp2Ngz2ILfxlm4XEUJo4z6cqqmhPJD/NuBuP0OzCY/bqCJu17Rl/hl+JN+Xu82hl
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, printer@iecc.com) via TCP6; 01 Jan 2020 17:55:10 -0000
Received: by ary.qy (Postfix, from userid 501) id 8549A11E2905; Wed, 1 Jan 2020 12:55:09 -0500 (EST)
Date: Wed, 01 Jan 2020 12:55:09 -0500
Message-Id: <20200101175510.8549A11E2905@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: moore@network-heretics.com
In-Reply-To: <dfa17007-a637-88d8-339c-a6225b1648c5@network-heretics.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/0E0MJGE12DbTIkplhOBluGL-NSE>
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:55:13 -0000

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.

R's,
John

v2.23.0 | Report a Bug | By Email