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

"Stan Kalisch" <stan@glyphein.mailforce.net> Mon, 07 October 2019 19:11 UTC

Return-Path: <stan@glyphein.mailforce.net>
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 012A11200E9 for <ietf-smtp@ietfa.amsl.com>; Mon, 7 Oct 2019 12:11:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mailforce.net header.b=ey/LSMpn; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=qZxIQ+A/
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 j-pwvdPsCGFO for <ietf-smtp@ietfa.amsl.com>; Mon, 7 Oct 2019 12:11:19 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6AD612008A for <ietf-smtp@ietf.org>; Mon, 7 Oct 2019 12:11:19 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id E6FAF20D98; Mon, 7 Oct 2019 15:11:18 -0400 (EDT)
Received: from imap6 ([10.202.2.56]) by compute7.internal (MEProxy); Mon, 07 Oct 2019 15:11:18 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailforce.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm1; bh=n3mG+/kMueBTMymbPE4mHeDbGE3f vY6Bhl+NZR78x/M=; b=ey/LSMpnqyolCGirA1lBFJhMf8BMDLpHSIaVSF7fcAjT 81jLsnttQeATW6o8FwdsOH41u1z0sjbn/NhZ4MrghZz2jSamXrTv8rk7loTmOAcs ITF6LonN8KSWC2R+0/f0dRDG+OWSFrQbcPnirJ+FKjudlkH11uwm3UkasLE9ZqFA kWrfyA5WTDl8bzY7ZlFEgqpV5Ogy+1LIOTsTioe+9EqYdfwH0jYVsKUm8841NVyc DaygI2WvO94N8J5YXB/ZFJZfoeUO8ioOmst7upq/CSVDzXLQkx18HO7IziVspHXs QmKVQtZitoT4Ge8qXRlsyBUzAF8rTtY5JYYJ2qyU/w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=n3mG+/ kMueBTMymbPE4mHeDbGE3fvY6Bhl+NZR78x/M=; b=qZxIQ+A/gowEpqrAzPZF2b oAZSTv9GdYpwyRd2dqZ6YLpXLyS6A+VA92Rpp5e2KHWmzVDTUPnRr4nRoid3sRU/ bBW5qaguf3gBgB9D7NSXfMrCCeRmMugHcIr86mRFI26ahSQB3DAKH8td0jFUB5K+ E2wHCu1rcBqYUBve/zSqRzMNz41WGWer0XkJ3o/De4YhMSf+oOCNYbFOLQWBpcEr 2HMIPPhC+lahfv8TVY/jJJQ/2eJN/5eg6QIzaDRI2tu0IaH3/ZXSodEhQzDd+mey 2LME0vG1jknPAw916Ti+NsXtfP/JbBk7Pr5mOqxSdlehYH4qxiQRXe6RVZlot+2w ==
X-ME-Sender: <xms:1o2bXZHIkrwyFt4lQsqWTQhH0AMi1gBZPrnn-9vfqZ2sdkvHdghGkw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrheejgdduvdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreerjeenucfhrhhomhepfdfuthgr nhcumfgrlhhishgthhdfuceoshhtrghnsehglhihphhhvghinhdrmhgrihhlfhhorhgtvg drnhgvtheqnecurfgrrhgrmhepmhgrihhlfhhrohhmpehsthgrnhesghhlhihphhgvihhn rdhmrghilhhfohhrtggvrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:1o2bXVyjL4CTCbqU_G8TBGJKPAMRatwYOFjXqprZ7WrxeDaRODLuQA> <xmx:1o2bXYg-W_betg_zlhsPLiL2VCvV4HnphZuNSqSyRerIV7HKRnX7xA> <xmx:1o2bXYxTMl0Ot6HsXlGm-KfP51_RjaqMqqh5Ayky944FCZfrejVTWA> <xmx:1o2bXVwkqz1t7V-X53gCVWib5WTduUxx8O6xx7eobHq_7wwFaFPgCA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4DD481400A6; Mon, 7 Oct 2019 15:11:18 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-360-g7dda896-fmstable-20191004v2
Mime-Version: 1.0
Message-Id: <f7b9f700-7303-449d-8212-147f29d0bdfd@www.fastmail.com>
In-Reply-To: <19705.1570469430@turing-police>
References: <20191007002348.GA23742@x2.esmtp.org> <20191007015616.BE113BB3D68@ary.qy> <CANtKdUeC0NVfvVpbHtwd=OoO=BoT8KNWVx8BGF-GPZPU-zo6QA@mail.gmail.com> <CAOEezJTH4Jukz2J4jSDfixECg2Jyyk4+cDnasiAoa4Q2F9=ZZw@mail.gmail.com> <b0dae4ca6e95dc83ca70f71ad780a1432273bcf5.camel@aegee.org> <CAOEezJRXUZkPoJn_kV92q=OQoUs32VzTR5a0JeAKg6NYBW55=Q@mail.gmail.com> <19705.1570469430@turing-police>
Date: Mon, 07 Oct 2019 15:10:29 -0400
From: Stan Kalisch <stan@glyphein.mailforce.net>
To: Valdis Klētnieks <valdis.kletnieks@vt.edu>, Viruthagiri Thirumavalavan <giri@dombox.org>
Cc: SMTP Discuss <ietf-smtp@ietf.org>
Content-Type: multipart/alternative; boundary="1f56b8fc026345ba8d627a8e3111a1c0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/YchX3LRReBYT7G4WN_XqpLHpU1M>
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: Mon, 07 Oct 2019 19:11:21 -0000

On Mon, Oct 7, 2019, at 1:30 PM, Valdis Klētnieks wrote:
> On Mon, 07 Oct 2019 22:55:19 +0530, Viruthagiri Thirumavalavan said:
> 
> > We both use a different demographic to define "end user" for MTA-STS. The
> > way you see it, an end user is a "mail server operator". The way I see it,
> > an end user is a "small business" who hosts their mails in a third party
> > mail service like Gmail. Configuring an HTTPS server is not going to be
> > easy for such small businesses.
> 
> The obvious answer is, of course, to write the proposal such that the https server
> can be outsourced the same way the email service was outsourced, and the DNS
> service was outsourced to a DNS hosting company.
> 
> There's an obvious business opportunity for hosting the email, the DNS, the http, and
> any other bits as one turnkey package.

That may be, but I do not think, however, that this addresses Viruthagiri's assertion about the cost being prohibitive for some in developing countries.


Thanks,
Stan