Stalwart mta-sts
I have been running Stalwart for some time and I have to say I am very pleased. And I did not run into any of the expected issues like delivery problems to Gmail. One thing that did not work out of the box was mta-sts. There is an enhancement ticket on GitHub with an answer from mdecimus explaining how to get mta-sts to work properly with multiple domains.
Let's say you host email for foo.net and bar.org, you need to do the following:
- Create an ACME provider entry containing mail.foo.net, mta-sts.foo.net, autoconfig.foo.net and another ACME provider for mail.bar.org, mta-sts.bar.org, autoconfig.bar.org. You may also add all these domains under a single ACME provider.
- Reload the Stalwart configuration.
- Done, you now have MTA-STS and Autoconfig enabled for all your domains. Stalwart automatically uses the right certificate based on the TLS name provided.
It is indeed that easy. I would have expected this information to be part of the mta-sts section in Stalwarts documentation. If I would have to point at one of the biggest weaknesses of the app right now it would be the documentation. It is mostly complete but sometimes it is a pain to find exactly what you are looking for. The Prometheus section is a good example. An explanation for the different metrics would have been more helpful than the history of Prometheus.
posted on Feb. 28, 2025, 8:26 p.m. in howto, infrastructure, security, self-hosting
This entry was posted as a "note" and did not undergo the same editing and review as regular posts.