What it means
The policy file was fetched but doesn't follow the format. A valid file has one key: value per line: version: STSv1, mode: with enforce, testing or none, max_age: in seconds, and an mx: line for each mail server. The detail lists the problems we found. A file larger than 64 KB is treated as invalid too.
Why it matters
Senders that can't read your MTA-STS policy ignore it. Typical mistakes are a misspelt mode such as strict, a missing max_age, mx entries written as a comma-separated list on one line, or an HTML error page served in place of the file.
How to fix it
- Open the file and compare it with this layout:
version: STSv1
mode: enforce
mx: mx1.example.com
mx: *.mail.example.net
max_age: 604800
- Use one
mx:line per server or wildcard pattern; a wildcard covers exactly one label. - Keep
max_agebetween a day (86400) and a year (31557600). - Change the
id=in the_mta-stsrecord after editing, so senders fetch the new file.
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. The policy row should list your mode, max_age and patterns with no errors.