IETF Logo Mail Archive

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

Keith Moore <moore@network-heretics.com> Sun, 27 October 2019 01:24 UTC

Return-Path: <moore@network-heretics.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 63B16120089 for <ietf-smtp@ietfa.amsl.com>; Sat, 26 Oct 2019 18:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 EwNa1o8ogrR8 for <ietf-smtp@ietfa.amsl.com>; Sat, 26 Oct 2019 18:24:36 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EAE4120043 for <ietf-smtp@ietf.org>; Sat, 26 Oct 2019 18:24:36 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 8A6E1367; Sat, 26 Oct 2019 21:24:35 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Sat, 26 Oct 2019 21:24:35 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=99dBQOaH2XOLJEjkzJLPIMHyBmt09Ny4qWLDiB+J9 r4=; b=AR1yGpIMmL6Koadvk/24cDn8jl4we4sQuVvhebaIVgm4Jjo1aSog6NYi/ g5bPJ9M/TUesZAo8KTqUotUuJtjwkniYfmEqWMMbq5zN7rXCQgdeeezp9CdLsuTd P90IKs3GAKQZPn0n798lIjPCOLBQlzO6gvoBNhQCgHMavK18VSoGgEpBmFzHOy4D Zqv3vnULw0EOm6B8XSLflwcTYVmAoyUDKIqN3wBIWzCDi4U/6y4rXdTFPpZD5R6K X9L+m3lj6CvDeO94YtxzDO0UndPiELl/K2/b17eayeDHy6tppK1I/bd93SmlBOgV NNE0+DSnJJq4O8161JUmVmxH0Ly8Q==
X-ME-Sender: <xms:0_G0XXYBarznS2kz8gLJ390tLpOcX-Es0AN1o0qxeE_HN0cLAr6iMQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrleeigdegiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefmvghithhh ucfoohhorhgvuceomhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhmqe enucfkphepuddtkedrvddvuddrudektddrudehnecurfgrrhgrmhepmhgrihhlfhhrohhm pehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomhenucevlhhushhtvg hrufhiiigvpedt
X-ME-Proxy: <xmx:0_G0XdMIW8dkjfFTlnPkHPN4V7mlAn4j9b2WBqZ3xIT4XQOL-pQ2dg> <xmx:0_G0XS7qwaVDiClGcHT61T_-UMMRSDrv43p0lHnRX-igx8KIA_DWSg> <xmx:0_G0XQfVX6o6t7DCQdzPzCoCJWanjmE_azqIsk6gplxK67RLczqeyA> <xmx:0_G0XaK7cttVWJQV2NiPkkdaJ2jiTCBf7GaQpec5YnUhzm_xqNHudw>
Received: from [192.168.1.97] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id BDB20D6005A; Sat, 26 Oct 2019 21:24:34 -0400 (EDT)
To: John Levine <johnl@taugh.com>, ietf-smtp@ietf.org
References: <20191027011742.5E6BAD74D2F@ary.qy>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <3bd69a26-1587-1ac9-0cec-c91ba2ac94a2@network-heretics.com>
Date: Sat, 26 Oct 2019 21:24:34 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <20191027011742.5E6BAD74D2F@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/_C7BdlZJ4CwjVhnHKrLT5G36zso>
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:24:37 -0000

On 10/26/19 9:17 PM, John Levine wrote:

> 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.

Ah yes, interesting point.   And users do have strange ideas as to what 
"works fine".

What's the half-life of a broken middlebox?   I'm guessing about 10 years.

Keith

v2.23.0 | Report a Bug | By Email