Welcome to the Hotel California: MTA-STS Unintended consequences?

[alento]

@stylnchris

removing the DNS records for the mta-sta woudn’t fix the problem (after waiting 7 days)?

No, because the issue is that Google caches the information internally in their system. Removing the record has no bearing as they will not check the record again before the time specified. This is mentioned specifically in the link shared earlier by @miabuser

[miabuser]

@alento

No, because the issue is that Google caches the information internally in their system. Removing the record has no bearing as they will not check the record again before the time specified.

But this would only be an issue if you had a previous policy with a later expiration date than the current policy. If you are using MiaB for more than a year and / or never have used the domain with MTA-STS before, then you should defentily be fine

## Option 2: Delete your MTA-STS DNS TXT record

MTA-STS turned off when policy expires, from one day to one year.

With this method, MTA-STS is turned off after the current and previous policies expire.

Some remote sites might have stored a previous policy version in the cache. Previous policies can have a later expiration date than your current policy.

[alento]

@miabuser

But this would only be an issue if you had a previous policy with a later expiration date than the current policy. If you are using MiaB for more than a year and / or never have used the domain with MTA-STS before, then you should defentily be fine

But the problem is that the domain was used with MTA-STS on the MiaB, so when it is moved to another provider, exactly what you listed happens …

MTA-STS turned off when policy expires

Which means NO email will be sent to the domain from Google, and whomever else may finally decide to implement MTA-STS, UNTIL the policy expires.

[stylnchris]

so google caches it forever ?

[alento]

No, until said policy expires. Which in the case of MiaB is one week.