Hello dear Stalwart developers,
I don’t have an urgent problem anymore, but I feel the need to share my thoughts. After the major disaster during the update from Stalwart 0.15.x to 0.16.x – which left everything in a non-functional state – I had hoped that such situations wouldn’t happen again during updates. On Monday evening, however, I learned otherwise.
An update from v0.16.27 to the latest version (image: latest) caused my Stalwart mail server (running in Docker) to stop working – yet again. The container failed to start because Stalwart reported that the version of RocksDB being used (1.0.0) was no longer supported. Everything worked fine again once I reverted to v0.16.27.
My attempts to export the data from the old database and import it into a new one were all unsuccessful. None of the suggestions I found online – or those recommended by AI – worked. In the end, my old database became corrupted, forcing me to set up Stalwart Mail from scratch with an empty, new database. Losing all my stored emails is one thing, but having to reconfigure every single setting is quite another. There is a clear need for a simple, version-agnostic export/import function within the WebGUI.
To make matters worse, the WebGUI became inaccessible a day later, returning only an HTTP 503 error. This led to another long troubleshooting session. I eventually discovered that Stalwart had added the IP address of my Caddy reverse proxy – which I use to expose the service – to its blocklist. This is another behavior I never encountered in v0.16.27. Ultimately, I had to add the IP range of my home network – where Caddy is running – to Stalwart’s whitelist.
Everything seems to be working again now, but this is already the second Stalwart Mail update that has ended in chaos. I don’t know why, but I only ever encounter such dramatic issues with Stalwart Mail. You really need to improve your update strategy. It is unacceptable for updates to repeatedly cause such problems, requiring extensive manual adjustments just to get things running again.
I am a private user, not a paying premium customer, so I don’t want to complain too much – but if I were relying on a mail server for stable, reliable business use, I would have reached the point where I’d switch to another provider.
Thank you for your understanding, and I hope you will consider how things could be handled better in the future.
Best regards,
Mic.