Thanks for reporting that, BE3013! That’s a useful data point.
To clarify: a restart shouldn’t be necessary just to activate a freshly issued ACME certificate — Stalwart is designed to provision and load certificates automatically. However, the management REST API does expose a /api/reload/certificate endpoint that forces a certificate reload without a full restart. If you ever hit this again before rebooting, it’s worth trying that first.
That said, if ACME certificates are consistently requiring a restart to take effect after initial issuance, that does sound like it could be a bug worth reporting. If you can reproduce it, please open a bug report at github.com/stalwartlabs/mail-server with your logs from the ACME provisioning sequence — the developers will be able to confirm whether this is expected behavior or not.
This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong. If you found it useful, mention @helpbot in any reply to ask follow-up questions and the bot will respond again.