I have a 30day Enterprise trial license.
Issued To: .com
Licenses: 50
Validity: August 03, 2026 to September 02, 2026
Type: Stalwart Enterprise Edition
·enterprise.licenseKey and enterprise.apiKey are set as Secret values (verified with stalwart-cli get enterprise → Secret entries are visible as: ****).
·I ran ‘stalwart-cli … create action/ReloadSettings’ successfully (Created Action …).
·I have logged out and into the Stalwart UI multiple times.
·JMAP logs show calls like x:Enterprise/get.
·However, no Enterprise features appear in the WebUI (no multitenancy options, no AI spam filter, etc.), and journalctl -u stalwart.service | grep -i license shows nothing related to the enterprise license activation.
·I tried to follow the Support Forum Article I got a enterprise trial licence, but its not active? how can i enable the enterprise features? - #5 by sreutter but even if I try to search for ‘server.licensing’ in the Stalwart logs (WebUI) I dont find anything. So it looks like Stalwart is not even trying to activate the Enterprise License?
Can you please check whether my trial license is valid and bound to the correct domain, or if there is an issue with license activation on my instance?
Any help would be nice.
Thank you, best regards
I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.
@Disrupt, the practical advice is right but the mechanism isn’t: ReloadSettings does re-run licence validation, because it reloads the full core, which re-parses the Enterprise object. So actions aren’t the problem here.
@bitfuchs, the reason you’re seeing nothing either way is a gap on our side rather than a sign of what happened. A successful check only logs server.licensing at startup, and a failed check gets recorded as a warning on the Enterprise settings object rather than as a log event, while the action only reports errors back to you. So the CLI said “Created Action” and told you nothing, and the log stayed quiet, whether the licence validated or not. Restarting is still the right move, but only because it’s the one path that logs the answer.
After the restart you should see either the server.licensing line saying the key is valid, or a warning naming DomainMismatch or InvalidDomain. My guess is the latter: the licence binds to the registrable domain of defaultHostname on the SystemSettings object, not to the URL you use in the browser. If defaultHostname is an internal name, or sits under a different domain from the one the licence was issued to, validation fails.
If licenseKey is stored as an environment-variable or file reference rather than a literal value, confirm the reference actually resolves for the service user; an unresolvable secret falls through silently. And confirm the account count is at or under 50, since exceeding the licensed count disables Enterprise with a warning too.
All clear! Thanks too @Disrupt and @stalwart for the support. BUT:
It was my mistake for not knowing that I have to build a binary with the ‘enterprise’ flag. After that everything else worked as expected.
I can see log entries for the valid enterprise edition license key and the features are now visible.