Topic · Transport Security
TLS-RPT STARTTLS not supported
A starttls-not-supported failure in TLS reporting indicates a mail server did not offer STARTTLS as expected.
How it works
A sender checks SMTP EHLO capabilities before negotiating an encrypted channel under policy.
What can go wrong
A misconfigured or inconsistent MX pool may fail security policy even if other mail exchangers support TLS.
What to check or do
Probe each MX host on port 25 and compare EHLO STARTTLS support across IPv4 and IPv6.
Practical scenario
A company has three MX servers. Two advertise STARTTLS, but the backup on IPv6 does not. Some senders report starttls-not-supported while a manual probe of only the first IPv4 MX appears clean.
Verification checklist
- Enumerate all MX hostnames and their A and AAAA addresses.
- Probe port 25 EHLO and STARTTLS on every reachable address.
- Compare per-host TLS-RPT failure counts.
- Fix the inconsistent listener and revalidate under the advertised transport policy.
How to investigate TLS-RPT STARTTLS not supported
- Signal to investigate
- A sender reports failure to negotiate STARTTLS with a backup MX.
- Evidence to collect
- Connect to each reported hostname and inspect EHLO/STARTTLS from relevant networks.
- Common wrong conclusion
- One working MX does not negate failures on another host or across an alternate IP family.
Put this into practice
Run a focused check, then explore protection if your domain needs it.