What it means
Your MTA-STS policy doesn't list one or more of your mail servers. The detail names the MX hosts that no mx: line or wildcard pattern matches. In enforce mode this is a fault; in testing mode it is a warning.
Why it matters
With mode: enforce, a sending server that picks an unlisted MX host must refuse to deliver to it. Mail that reaches that server, often a backup MX, simply bounces or waits in the sender's queue. This usually happens after changing mail providers, adding a backup server, or when a provider renames its hosts.
How to fix it
- List your current MX records. The result shows each host and the pattern that matched it, if any.
- Edit the policy file and add an
mx:line for each missing host. A wildcard such as*.mail.protection.outlook.comcovers every host one level below that name, but not deeper ones. - Remove lines for servers you no longer use.
- Change the
id=value in the_mta-stsTXT record so senders fetch the corrected policy. - If you can't fix it today, switch the policy to
mode: testinguntil you can.
Check it worked
Run the MTA-STS checker on your domain again. Policy files are fetched fresh on every check, but senders cache the old policy for as long as its max_age says, so give real mail servers that long to notice. Every MX host should show a matching pattern.