What MTA-STS is#
MTA-STS (Mail Transfer Agent Strict Transport Security) lets a domain declare that inbound mail must be delivered over TLS with a valid certificate. TLS-RPT provides reports on delivery failures caused by TLS problems.
Why it matters#
Opportunistic TLS can be downgraded by an attacker in the network path. MTA-STS closes that hole and is increasingly a checkbox in security questionnaires.
What Klaviyo handles#
Most platforms, including Klaviyo, generate the records or settings you need under a domain authentication or sending settings page, and expose bounce and complaint data in reports. Confirm the exact location in Klaviyo's current documentation.
What you still own#
- Publish a _mta-sts TXT record with an id value you will change on each policy update.
- Host a policy file at https://mta-sts.yourdomain.com/.well-known/mta-sts.txt listing your MX hosts.
- Start in mode: testing, then move to mode: enforce after reviewing TLS-RPT reports.
- Publish _smtp._tls TXT with rua=mailto: to receive TLS-RPT reports.
Common mistakes#
- Listing MX hostnames that do not exactly match certificate names.
- Forgetting to bump the id when the policy file changes, so caches never refresh.
Frequently asked questions#
Does MTA-STS affect outbound mail?
Only when the recipient domain publishes a policy. Your own policy protects mail coming to you.
Is DANE better than MTA-STS?
DANE requires DNSSEC and is stronger, but MTA-STS is easier to adopt. Microsoft and Google both support MTA-STS.
Does Klaviyo set up MTA-STS automatically?
Klaviyo provides the values and some checks, but publishing DNS, aligning domains, and monitoring results remain your responsibility.