IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Wed, 16 October 2019 19:53 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 9E50012082C for <ietf-smtp@ietfa.amsl.com>; Wed, 16 Oct 2019 12:53:19 -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=e8XNfyea; dkim=pass (1536-bit key) header.d=taugh.com header.b=tal1iuva
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 OuWJ_brG0ZCw for <ietf-smtp@ietfa.amsl.com>; Wed, 16 Oct 2019 12:53:18 -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 08AB012095B for <ietf-smtp@ietf.org>; Wed, 16 Oct 2019 12:53:17 -0700 (PDT)
Received: (qmail 66343 invoked from network); 16 Oct 2019 19:53:15 -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=10325.5da7752b.k1910; i=printer-iecc.com@submit.iecc.com; bh=Ut8Hpvy2WIS1fA8XIOEAcHGn2r3SYRI7NizyQG0vdIo=; b=e8XNfyeateB9P/OS4iuqHvTIm3m/hLw019bEjszmazgITrlhzWVQo1UWjXFNd+4H4neA6KqzIrvC1cGi3Hqf00fDg6MOmn3JSyO5Bz/7FbZ5Syz66wfU26q+LIXtJBQruNZw2nfkM36oS8ifbVTeuF2unJKBYzRvvB6i+8Dh3c5m+Ee+GnAMS390Td3cqRfuk/ePOxOPojXmEtctmPdIyUWKeevK0Iro9ZQegQq5dB4uTADRNkxGI9u/QWzHwKRK
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=10325.5da7752b.k1910; olt=printer-iecc.com@submit.iecc.com; bh=Ut8Hpvy2WIS1fA8XIOEAcHGn2r3SYRI7NizyQG0vdIo=; b=tal1iuvat3P7t15FBZw68dNK/Aj/yNhN66KqUzBMHs4KZZBoetjpOVhu4nOrrB6LM8UTTAxfCTNAeUUk+TGIDM2FJ4uTMXOHDnYCCs8lgnd7tPMCe8CJASis3qHkGyxXRjAOOnucHhkGv2Mi1kK7ZXyjHldljZYu+Yqno+l8n69+n/trvlwWJU2BTq3YndFktOK50bA6LsCVmYGz2pclMnvkOkX88KIg2zRTF5fJ0iZ4w932AXlOKiEbO6Kwph0Z
Received: from ary.local ([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; 16 Oct 2019 19:53:15 -0000
Received: by ary.local (Postfix, from userid 501) id 145DFCBFAAF; Wed, 16 Oct 2019 15:53:14 -0400 (EDT)
Date: Wed, 16 Oct 2019 15:53:14 -0400
Message-Id: <20191016195315.145DFCBFAAF@ary.local>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: valdis.kletnieks@vt.edu
In-Reply-To: <167179.1571248841@turing-police>
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/2j-Jo3bZU3SV0PSpvp3izQTW_gs>
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: Wed, 16 Oct 2019 19:53:29 -0000

In article <167179.1571248841@turing-police> you write:
>Seriously - if gnu.org *still* doesn't support TLS 1.1 (RFC4346 came out in
>April 2006), they're probably running an SSL/TLS software stack that has about
>4 zillion since-patched security holes in it.

They're running Exim 4.71 which was released in 2009.  The current
version is 4.92.3.  Their mail software is a decade out of date.

This is not a hard problem to solve.

v2.23.0 | Report a Bug | By Email