> On Oct 24, 2017, at 2:15 PM, Ivan Ristic <ivan.ris...@gmail.com> wrote:
>
> No, it really is. If I am building a business on top of someone else's
> infrastructure, I don't want to build on top of something I don't control; in
> this case, their domain name. Thus, I don't want to give their MX servers to
> my customers. It can be as simple as not wanting your users to know that
> you're "reselling" someone else's service. It raises all sorts of questions.
An MTA is far more heavy-weight infrastructure component than
a website. Sure you can start a Web business on someone else's
shared platform, but running email hosting on someone else's
virtually hosted MTA is entirely unrealistic.
MTAs both send and receive email, they run complex anti-spam
and anti-virus filters, they are integrated with mailbox
stores, they have IP reputations as sending systems, they
do DKIM signing, add Authentication-Results headers, store
and forward email, ...
Mere SNI will not come remotely close to giving you a virtual
MTA. An MTA is NOT a website.
--
--
Viktor.
_______________________________________________
Uta mailing list
Uta@ietf.org
https://www.ietf.org/mailman/listinfo/uta
