IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Sun, 27 October 2019 01:17 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 06B2F1200FE for <ietf-smtp@ietfa.amsl.com>; Sat, 26 Oct 2019 18:17:45 -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=rwfaDu4I; dkim=pass (1536-bit key) header.d=taugh.com header.b=s9XEkyP/
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 04Okz-ikYQmF for <ietf-smtp@ietfa.amsl.com>; Sat, 26 Oct 2019 18:17:44 -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 2314B120048 for <ietf-smtp@ietf.org>; Sat, 26 Oct 2019 18:17:44 -0700 (PDT)
Received: (qmail 14104 invoked from network); 27 Oct 2019 01:17:43 -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=3715.5db4f037.k1910; i=printer-iecc.com@submit.iecc.com; bh=Uo2YpTVspcFLrPRjXHaK2fJdHtzapcdw2JAxBa5IOk0=; b=rwfaDu4Ii8w4lF03PmMCsbpa50FWWo2GQFw/ZG1qRr0tWnvKvr4RFc4MiYmLAYYH/9cE/IA7F2paFCJlm273VDI1mC3ghVjk+tTR5w3Jm9FmiY1pGPgZjNTOGFBj1RQ27RyYZzPxaPF3PRSj4zYqeKr1B1KDFdKN+a2hhgUrU34G6Q8oyxdhwBpDMekRseeWOHi55KAGUTdWkbJmAjlmycIyBMS+en7c9omA5YiicFjlws6g0I/cN+BkbdbvM2xX
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=3715.5db4f037.k1910; olt=printer-iecc.com@submit.iecc.com; bh=Uo2YpTVspcFLrPRjXHaK2fJdHtzapcdw2JAxBa5IOk0=; b=s9XEkyP/aIDNbv3ZxhFbK8AAZOLiqRCnNCD8hTqvhUBw8wXNi7rfzQyCfkPHhSr7KO4lvwxzI2bKet2W3s9e1irXPdJ9vLermc/b+9Eqxpo5hKVv4sRB1xZZzHA9yREgIVenzrX/V2W0rdpoafvzvjCWb50D5uoi2hF1QHEXFGocX3zRFMY0QH35ISHXZFe3PFzbJ4o3VpR2Nb5cT+YMNkYIPOWY+GQY9DskINtLT4g2GMILrmTR4PwxwlCL27tw
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 01:17:42 -0000
Received: by ary.qy (Postfix, from userid 501) id 5E6BAD74D2F; Sat, 26 Oct 2019 21:17:42 -0400 (EDT)
Date: Sat, 26 Oct 2019 21:17:42 -0400
Message-Id: <20191027011742.5E6BAD74D2F@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: moore@network-heretics.com
In-Reply-To: <ee3b3211-a0be-b6f3-b551-0027fcea63c4@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/iNF4Lz_jEF2qkhmvhWC29LHPuOM>
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:17:45 -0000

In article <ee3b3211-a0be-b6f3-b551-0027fcea63c4@network-heretics.com> you write:
>> I believe it's the same reason that Google doesn't sign their domains 
>> with DNSSEC.  They certainly could if they wanted to.
>
>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.

I gather that the number of ways that middleboxes can screw up the DNS
is far greater than we can imagine.  And getting people to fix it is not
easy since "the box works fine" and DNS works fine, too.

v2.23.0 | Report a Bug | By Email