When you manage incoming mail for your domain, email transport security shows up as three tasks: introducing MTA-STS, investigating TLS-RPT reports, and updating MX hosts or certificates without disrupting external senders. Each guide ends in a deployment or investigation decision. Choose the guide for the task on your desk right now.
Roll out MTA-STS from testing to enforcement
If you are setting up MTA-STS for the first time, start with MTA-STS rollout: from testing to enforce, and a way back. The procedure guides you through the checks on each receiving path, publishing the policy, the decision to move from testing to enforcement, and withdrawing the policy.
You also establish a rollback strategy before flipping the switch. External sending servers cache your policy for the duration set by max_age, so a new policy or a changed ID does not shorten the lifetime of policies senders have already cached. For the underlying standard, read the guide chapter on MTA-STS (RFC 8461).
Interpret TLS-RPT reports without guessing
When a TLS-RPT report lands in your inbox, turn to How to read a TLS-RPT report (and what it can’t tell you) to decide what warrants investigation. The guide connects the policy data and the failure categories to a receiving endpoint, explains why counts can overlap, and names the evidence you need to verify a repair.
Remember what the data cannot show. Session counts are not message counts or proof of inbox placement, and a missing report does not establish a clean result. For the reporting schema itself, read the guide chapter on TLS-RPT (RFC 8460).
Update MX hosts or renew certificates with MTA-STS live
When MTA-STS is already enforced on your domain, changing mail exchange routing requires strict sequencing.
Follow Changing MX hosts or certificates with MTA-STS enforced to execute the migration cleanly. The walkthrough separates routine certificate renewals from server migrations and covers certificate checks on both SMTP and the policy host. Its migration example brings together the expiry of the historical policy, separate DNS timers, overlapping MX authorization and rollback conditions, so you can tell when a route change has to wait and what must stay available during recovery.
For another email infrastructure topic, return to the knowledge base.


