[Top] [All Lists]

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

2019-10-07 15:04:46
I'm interested to hear more about those situations.

It seems like the primary concerns with additional costs associated with

* the cost of buying a CA-signed cert (but what about Let's Encrypt?)
* the cost of hosting your own HTTP server if you are in a hosted
* the cost of hosting an HTTP server if you are hosting your own MTA

Depending on the level of automation, I think the extra effort required by
MTA-STS ranges from "none" to, unfortunately, "some." But I don't fully
understand the scenario where it's a significant economic burden beyond the
basic cost of hosting an MTA. Can someone help explain this better?

On Mon, Oct 7, 2019 at 9:11 PM Stan Kalisch 

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


ietf-smtp mailing list

How's my emailing? http://go/dan-email-slo

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

ietf-smtp mailing list
<Prev in Thread] Current Thread [Next in Thread>