IETF Logo Mail Archive

Re: [ietf-smtp] why are we reinventing mta-sts ?

"John Levine" <johnl@taugh.com> Tue, 08 October 2019 01:58 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 8188C12010F for <ietf-smtp@ietfa.amsl.com>; Mon, 7 Oct 2019 18:58:55 -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=kdYlWiH6; dkim=pass (1536-bit key) header.d=taugh.com header.b=ldyz6sCd
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 9R4SBMtaMPFE for <ietf-smtp@ietfa.amsl.com>; Mon, 7 Oct 2019 18:58:54 -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 1573D120019 for <ietf-smtp@ietf.org>; Mon, 7 Oct 2019 18:58:53 -0700 (PDT)
Received: (qmail 18900 invoked from network); 8 Oct 2019 01:58:52 -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=49d2.5d9bed5c.k1910; i=printer-iecc.com@submit.iecc.com; bh=2vZbo5K2jT9bPd1C8wjOUEa/IiYdeZ9sYCsH4MV59nI=; b=kdYlWiH6o2sNyrViPHemQgpnVTrIFSPEP9zDylJfhaRdp5/9FFKr6c2nvznaQ/iGcF7kjH2uxwzwoRiys0Dcohfcreg0ObC8jjFPsZNWFcvDKoXg+cBgNWNBmOu0egIfGmdEnSJGggFImHRlNs3Gx77iz8kdMJJ5wKdAQE3xqamG+4/XwDxKxd+YAgaD7n4AHM5SHA4D26oytRUSNJyCvtsOJgNgZ2HUf0uS6gLtGhAon6klonauDK9jjQrbz66j
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=49d2.5d9bed5c.k1910; olt=printer-iecc.com@submit.iecc.com; bh=2vZbo5K2jT9bPd1C8wjOUEa/IiYdeZ9sYCsH4MV59nI=; b=ldyz6sCdZ5v8Wk5sMLlZdhcU6HzkBrd+afPFufLCrfHuyfYohDckTGlMYRvOd3QQE4856wH1v72e8JtLE56dbo2cFgxjklkeyFKTiHKcJMYi9picxve8sqCCzV837N9uC9rqH6vLMPtjcxG+hdAxTu+Hakf0YLdXh4Zbr5i0YIoP27Ga2eCXLBtdqLOdgLgKxFZ/114P710dDNYqCb+bn8CKJtg82PNd2HBnkbgTpMcKlSGQMHWa5iLma2FCOMTG
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; 08 Oct 2019 01:58:52 -0000
Received: by ary.qy (Postfix, from userid 501) id 818E1BBE15E; Mon, 7 Oct 2019 21:58:51 -0400 (EDT)
Date: Mon, 07 Oct 2019 21:58:51 -0400
Message-Id: <20191008015851.818E1BBE15E@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
In-Reply-To: <b0dae4ca6e95dc83ca70f71ad780a1432273bcf5.camel@aegee.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/92AlJ9GEyt8-49Zic9CEmRHWe9Y>
Subject: Re: [ietf-smtp] why are we reinventing mta-sts ?
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: Tue, 08 Oct 2019 01:58:55 -0000

In article <b0dae4ca6e95dc83ca70f71ad780a1432273bcf5.camel@aegee.org> you write:
>Hello,
>
>On Mon, 2019-10-07 at 18:55 +0530, Viruthagiri Thirumavalavan wrote:
>> (3) Not all end users have knowledge about how to configure an HTTPS server. This is the reason why most of
>them relying on third party mail hosting services like Gmail for hosting their mails. They can follow simple
>things like adding a DNS record. But configuring an HTTPS server is going to be a rocket science for them.   
>> 
>
>Much more people know how to configure an HTTPS server, than to configure a SMTP server (with STARTTLS).  So configuring
>HTTPS is not an obstacle.

Having actualy implemented mta-sts for the mail domains I host (about
85 of them) I can confirm that it's not difficult.  Setting up a
little web server is easy; if for some reason you're outsourcing your
mail to a provider that doesn't support mta-sts, it was a deliberate
decision to put the web server at a different name mta-sts.<name> so
you can point it at some random $5/yr web host if you need to.

This whole argument is fairly silly, since if mta-sts catches on, the
mail providers will all do it for you anyway.  Google provides it for
gmail.com and google.com so their other zillion domains shouldn't be
far behind.

v2.23.0 | Report a Bug | By Email