What it means
Your MTA-STS policy says mode: testing. Sending servers fetch it and report any delivery that would have failed the policy, but they still deliver the message, encrypted or not. Testing mode is the right first step; it just doesn't protect anything yet.
Why it matters
The point of MTA-STS is to stop a sender from falling back to unencrypted delivery when someone interferes with the connection. In testing mode that fallback still happens. The only thing you gain is the reports, so testing is useful only while someone reads them.
How to fix it
- Make sure you publish a TLS-RPT record and that its reports reach a mailbox someone reads or a reporting service.
- Watch the reports for two to four weeks. Look for failures naming one of your own mail servers: an expired certificate, a name the policy doesn't list, or a server that doesn't offer encryption.
- Fix anything the reports show. Then edit the policy file: change
mode: testingtomode: enforceand raisemax_ageto a week or more, for example604800. - Change the
id=value in the_mta-stsTXT record so senders know to fetch the new policy.
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 MTA-STS section should say enforced.