[SOLVED] V0.50 MTA-STS policy is missing: STSFetchResult.NONE

[johnfl68]

Hello:

I figured out most of this, but still have 1 issue left.

Part of the issue is I use DNS Made Easy for all my DNS, and my main domain is on a separate server than the MIAB server. I have been running this way fine for quite a while.

I was able to add the _mta-sts and _smtp._tls txt files fine.

Then using info from this thread:

MTA-STS for MIAB?

I’m surprised there’s not been more mention of MTA-STS on here, especially when it fits so nicely with the (very welcome!) implementation of TLS 1.2 and 1.3-only change in MIAB 0.44. There’s a nice little guide here for setting up MTA-STS along with TLS-RPT. I’m looking to do that for MIAB. Unfortunately mta-sts is not one of the default sites set up (it does the bare domain, autoconfig, & autodiscover), so that would need adding, and it would also need to be added to the list of (sub) domains …

I added the Alias administrator@mta-sts.mydomain.com (using my domain name).
This worked ok it said.

But then for the TLS Certificate, for that subdomain, there was no ‘Provision’ option in the GUI, just an install option?

How to I get Let’s Encrypt to add the TLS certificate for the new subdomain on the MIAB server?
Also it did not seem to create the mta-sts.mydomain.com subdomain, the /home/user-data/www/ directory just has a ‘default’ directory and not anything else. Is the file somewhere else? It didn’t say to create that directory, it implied that it would be made when I added the alias mail account.

Let’s Encrypt did the main MIAB domain certificate fine when I first installed and has worked fine for that.

If anyone can offer some help, it would be appreciated.

Thank you!