On Tuesday 6 April 2021 22:04:48 CEST, Kristijonas Lukas Bukauskas wrote:
I believe O365 clients of *paid* services could argue this is a
breach of the contract. A client wants to deliver a message to
user(_at_)example(_dot_)com. Sending MTA misleadingly says: Receiving MTA
of user(_at_)example(_dot_)com has the problem A (MTA-STS validation
failed), that's why we can't provide you a service you paid for.
If that's not the case (and I suppose it's not: RFC8461, section
4.1 defines MX host Validation by matching MX record *name*
against MTA-STS policy; the end).
Look it up and quote chapter and verse, please. I don't see anything of the
kind. I do see wording in "my" enterprise documentation that IMO suggests a
required ability to send to working sites, but nothing that requires
Microsoft to provide a correct analysis of what is broken at sites outside
Microsoft's control.
Arnt
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp