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

"Valdis Kl=?utf-8?Q?=c4=93?=tnieks" <valdis.kletnieks@vt.edu> Sun, 27 October 2019 01:13 UTC

Return-Path: <valdis@vt.edu>
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 131BC1200FF for <ietf-smtp@ietfa.amsl.com>; Sat, 26 Oct 2019 18:13:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 6yw485t2IxqQ for <ietf-smtp@ietfa.amsl.com>; Sat, 26 Oct 2019 18:13:26 -0700 (PDT)
Received: from omr2.cc.vt.edu (omr2.cc.ipv6.vt.edu [IPv6:2607:b400:92:8400:0:33:fb76:806e]) (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 ACF8C12007C for <ietf-smtp@ietf.org>; Sat, 26 Oct 2019 18:13:26 -0700 (PDT)
Received: from mr6.cc.vt.edu (mr6.cc.vt.edu [IPv6:2607:b400:92:8500:0:af:2d00:4488]) by omr2.cc.vt.edu (8.14.4/8.14.4) with ESMTP id x9R1DPpN004349 for <ietf-smtp@ietf.org>; Sat, 26 Oct 2019 21:13:25 -0400
Received: from mail-qt1-f199.google.com (mail-qt1-f199.google.com [209.85.160.199]) by mr6.cc.vt.edu (8.14.7/8.14.7) with ESMTP id x9R1DJBN005271 for <ietf-smtp@ietf.org>; Sat, 26 Oct 2019 21:13:25 -0400
Received: by mail-qt1-f199.google.com with SMTP id c32so6986032qtb.14 for <ietf-smtp@ietf.org>; Sat, 26 Oct 2019 18:13:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:content-transfer-encoding:date:message-id; bh=oBQVz2oFaJq5VEYdrpUDR9losHbkDlnziVubBIr6TxI=; b=EStutJnz/LbYa9m61xGOkYg8ZIKoKuGYTgzh/oR7OtkC/J6/2Yj5/rhWZjJljo1thR K7r3iTip3BbW1yGdsD0C1m4NctMncZiTtFxUX3jq5flGpkfL+McQpzNzNqjI4CaT+Wq1 9JSDt684AlfJbCoxikm1a9pW0Rg0I6cLzr5lsYRPvWSHq6p5UoeIQxeenzlDavt9IkQQ /XdT9AvVZR1qqkTXmJ6kB1v8MmlaWyHrSPuGI54+yYn7ufWGivTWt1Hg8AJSayz5vuy/ 36rXl8VqH79wbP5xMkMvpNKrSmKMZE2RiGA1UlpPWmcg5QSt3Jg6QMX2fg9ZtJ3DiT3K 4nnA==
X-Gm-Message-State: APjAAAVH/8eJ5dU79YdyiqW4INVbSCI8wNGwPVV7unez5pd275UJDfxH vPyxQ9IPFReTvrwy75orJCVITS8DZ6iL86JxTLDBkrX+2rfR5tsnfaCRhqswn4Ev0yEToGZQ5yu 3YAgx+qk4zMp3vStcu4DSXA==
X-Received: by 2002:aed:3b3b:: with SMTP id p56mr10770872qte.200.1572138799306; Sat, 26 Oct 2019 18:13:19 -0700 (PDT)
X-Google-Smtp-Source: APXvYqzUx/3ZbidZcpuKGTR9dpm85vfDrzcLaa90v9iBlQiSVvh+YTt03VFDRNtAbycQgkv1j0LEDA==
X-Received: by 2002:aed:3b3b:: with SMTP id p56mr10770860qte.200.1572138799058; Sat, 26 Oct 2019 18:13:19 -0700 (PDT)
Received: from turing-police ([2601:5c0:c001:c9e1::359]) by smtp.gmail.com with ESMTPSA id l7sm2555970qkg.102.2019.10.26.18.13.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 26 Oct 2019 18:13:17 -0700 (PDT)
Sender: Valdis Kletnieks <valdis@vt.edu>
From: Valdis Kl=?utf-8?Q?=c4=93?=tnieks <valdis.kletnieks@vt.edu>
X-Google-Original-From: "Valdis Klētnieks" <Valdis.Kletnieks@vt.edu>
X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7+dev
To: Keith Moore <moore@network-heretics.com>
Cc: ietf-smtp@ietf.org
In-Reply-To: <ee3b3211-a0be-b6f3-b551-0027fcea63c4@network-heretics.com>
References: <20191027002554.260ABD7437F@ary.qy> <344aaf1f-df91-ffb9-38bc-527d159a2ca6@network-heretics.com> <alpine.OSX.2.21.99999.368.1910262041440.10592@ary.qy> <ee3b3211-a0be-b6f3-b551-0027fcea63c4@network-heretics.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1572138796_26149P"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 26 Oct 2019 21:13:16 -0400
Message-ID: <162361.1572138796@turing-police>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/-_QMGagjCYqwELv8o4cbL5N47_4>
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 01:13:28 -0000

On Sat, 26 Oct 2019 21:02:55 -0400, Keith Moore said:

> between administrative domains wouldn't look like a huge change.   Maybe 
> it would even be justified as a spam deterrent.

I wonder what percent of spammers would have any problems and if any spam
would actually be blocked.  They were on the bleeding edge of adopting SPF and
similar, after all.

> Nor sure I get the analogy.   AFAIK if Google signed their domains, the 
> only things that would break would be broken DNS clients/resolvers doing 
> verification, which would hopefully be few in number.

On my more cynical days, I contemplate whether breaking such clients is the
fastest way to get them fixed.....