-
> 4) 3.2. MTA-STS Policies
>
> The [RFC7231] "Content-Type" media type for this resource MUST be
> "text/plain".
>
> I think this requirement is a bit strong, because we should really
>…
-
When N/D/R trains have 36 St, N runs first, only has 36th Bklyn, so replaces 36 St Queens by mistake.
-
In section 3.4 you cover policy delegation to a "smart host". This term and the procedure is not clear to me.
The term "smart host" is well known for outgoing mail servers (when the sender log in to…
-
----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------
Thanks to everyone who worked on this docume…
-
sometimes different web services are running on the same IP address.
in the case of HTTP traffic there is no definitive way to determine the vhostname (you can use some redirects header and such but …
-
While the Security Considerations section says
> SMTP TLS Reporting provides transparency into misconfigurations or attempts to intercept or tamper with mail between hosts who support STARTTLS.
…
-
In section 3.3, maybe rephrase to
> "which is valid for the 'mta-sts' host at the policy domain, e.g. 'mta-sts.example.com'"
-
The current draft has this to say about multiple TXT records for a single domain:
> If multiple TXT records for `_mta-sts` are returned by the resolver, records
which do not begin with `v=STSv1;` …
-
See issue #161.
It's fixed for MTA-STS but not yet for SMTP-TLSRPT. Using RFC 7405 would make the ABNF a lot easier to read.
-
I've written a small (possibly buggy) testing tool for MTA-STS: https://github.com/aykevl/mta-sts.
While doing that, I found a few issues with the spec as it is. Some are things that I suspect are re…