IETF Logo Mail Archive

Re: [ietf-smtp] How to encrypt SMTP?

"John Levine" <johnl@taugh.com> Sun, 27 October 2019 00:25 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 96A8A1200C5 for <ietf-smtp@ietfa.amsl.com>; Sat, 26 Oct 2019 17:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 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, URIBL_BLOCKED=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=BNqSLDMD; dkim=pass (1536-bit key) header.d=taugh.com header.b=P0epCmJ7
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 Ht90z4h0Y_Zz for <ietf-smtp@ietfa.amsl.com>; Sat, 26 Oct 2019 17:25:57 -0700 (PDT)
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 0A1A712008C for <ietf-smtp@ietf.org>; Sat, 26 Oct 2019 17:25:56 -0700 (PDT)
Received: (qmail 7133 invoked from network); 27 Oct 2019 00:25:55 -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=1bdb.5db4e413.k1910; i=printer-iecc.com@submit.iecc.com; bh=dCui6myVxkPdfr7Nyfc7xBcDwm3ozjXluYBF0sYZ1Mw=; b=BNqSLDMDUi6bhZPSnfPXukjms8CqcIJQNJS4XngrKyRJ+HrOek5UN3SP/HlmpOuqs1GRc9/hnGPHnjV93jRZhopwXrVSHOPMlofWbCuicW4rsZw7FieaGJmR7Lm6JuCxgj5wROW9nvo75AD60krIuzcRNkIRjhSYd4bl5lf/4OTBQpcdlHsihjMMnRnUxsidZF04UhISvkI5evo5DHQ1rQSchbqiiUWVd2ehLn2XCz/dkYfTYnkyg3DRrb13vp62
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=1bdb.5db4e413.k1910; olt=printer-iecc.com@submit.iecc.com; bh=dCui6myVxkPdfr7Nyfc7xBcDwm3ozjXluYBF0sYZ1Mw=; b=P0epCmJ7uLCKbQaMepXGkD8Xqh5oOYX9sq8m01RlHo9SR+h2PM7QnLH0za0Xe0enYN7olEqfFB5LJNIrDr//53yfWwMB5HBL6OvHt8+a8KucdaS/lVsVOC2rzL4xLY+w+B6mS92ulp0IK13BFP7vWeUe/f6XMXcU1RuLBJaPaUEfqQnyMD3fvjZeUGI7WIeU0zmyYL3CHmXs9bUdqdnEmqklsEPWCRKAka0BGFGw7BqpX1rVmwmo7LpYnjPWINuN
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; 27 Oct 2019 00:25:54 -0000
Received: by ary.qy (Postfix, from userid 501) id 260ABD7437F; Sat, 26 Oct 2019 20:25:53 -0400 (EDT)
Date: Sat, 26 Oct 2019 20:25:53 -0400
Message-Id: <20191027002554.260ABD7437F@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: moore@network-heretics.com
In-Reply-To: <037312D9-E9DD-464C-89D3-036786456119@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/Sf087C0FPw0SGDM1AJ54kWRP9tM>
Subject: Re: [ietf-smtp] How to encrypt 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: Sun, 27 Oct 2019 00:25:59 -0000

In article <037312D9-E9DD-464C-89D3-036786456119@network-heretics.com> you write:
>Yes but IMO we should be moving toward a world in which TLS is mandatory for SMTP relay.    Clear guidance to implementors
>and operators on what TLS versions, cert algorithms, and ciphersuites a client and server should support, might help us get there.

I don't think that's the problem.  I don't see any SMTP TLS failures other than from spambots.

>(perhaps as a stepping stone, cleartext mail relay could be pessimized ...

We already have mta-sts, which says that cleartext is forbidden for
the domains it's published for.  Why reinvent another wheel?

R's,
John

v2.23.0 | Report a Bug | By Email