IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Sun, 27 October 2019 15:00 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 8AEA812013C for <ietf-smtp@ietfa.amsl.com>; Sun, 27 Oct 2019 08:00: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=kCvSm1zh; dkim=pass (1536-bit key) header.d=taugh.com header.b=fwsSt7Vb
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 i-ZGt5pM_3_a for <ietf-smtp@ietfa.amsl.com>; Sun, 27 Oct 2019 08:00: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 B76C812013D for <ietf-smtp@ietf.org>; Sun, 27 Oct 2019 08:00:17 -0700 (PDT)
Received: (qmail 68460 invoked from network); 27 Oct 2019 15:00:14 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=10b69.5db5b0fe.k1910; i=printer-iecc.com@submit.iecc.com; bh=KMwn/kd9VfJ5AN438q81MlaxCc/+FMJlHlzjLbkW8/4=; b=kCvSm1zhkeayF+kV9VbbYaZK+yFOy0jE/4kb3NGUGc8l7kCetCNIJ1s0B0eizai7R60WAlMKG8214YGdqbOAP2V1/jU1RDmNBxhfA8RQ1jSRD/rI70ZW2RidKQ0ybo60GD7K65PXCVkE6afKdRJvOCsZkvmvO/nCjRITqa6UJd+KAbzbRXeakoewFlQNR5YJIpcUGl7+7uOg8I6qjK9w5UONOVCTs+fUGCp0KAeuN4W7FX2dmOiygwAUzHEBDFUx
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=10b69.5db5b0fe.k1910; olt=printer-iecc.com@submit.iecc.com; bh=KMwn/kd9VfJ5AN438q81MlaxCc/+FMJlHlzjLbkW8/4=; b=fwsSt7VbwxSg2z5D9tK5n5A+qpChGT60lAxYY5J311jbsa8u5HqIytdA6H6FckKJNhgXRFhbnjAvLGnbp0Ck2CbG5uaapRtbuLAb6ucpUDYIFSt++qDSENftaFZ2o4psMKtHrO83So8pn9jCHEWEOy/yrCzFq+gV7BBFTteR6Ueo7nSvBtxL5nYLTxZbAmgxuGad0Y2DAgbTudrUPsJErGrN4md596ndHLMGhDz5mwMdoUEZukGA+f7Io3j81pjD
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 15:00:13 -0000
Received: by ary.qy (Postfix, from userid 501) id 5715BD79FC5; Sun, 27 Oct 2019 11:00:12 -0400 (EDT)
Date: Sun, 27 Oct 2019 11:00:12 -0400
Message-Id: <20191027150013.5715BD79FC5@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
In-Reply-To: <3BB87806-0EEC-47EF-B30F-50029DC2D79F@dukhovni.org>
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/EJggbfu91HrushEkilpZeUIncrE>
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 15:00:19 -0000

In article <3BB87806-0EEC-47EF-B30F-50029DC2D79F@dukhovni.org> you write:
>The middlebox breakage affects mobile users in hotels, airports, home
>networks, ...  It has little to no effect on MTAs in data-centres.
>MTA-to-MTA DNSSEC does not face any meaningful middle-box barriers. ...

>Bottom line, sign-away, you'll not have any issues, unless your domain
>is hosted by a small number of small (mostly Dutch) providers.

I agree that the DNSSEC problems have close to nothing to do with mail issues.
But it's hard to sign the MX records for a domain without also signing the A
and AAAA records.

R's,
John

v2.23.0 | Report a Bug | By Email