Storage and Quotas

[alankeny]

I'm testing Stalwart Mail as a replacement for a small personal email server composed of Dovecot, OpenSMTPD, and RSpamD. Initially I tried importing my primary mailbox using stalwart-cli import, but the folder hierarchy came over as a flat list with dots separating the folder names. After that I deleted everything, reinstalled Stalwart Mail, and tried migrating my account with imapsync instead.

For the first attempt I used the default storage settings. I also set a quota on my account, so I could view how much space my account was using through the web interface. The first time I ran it, imapsync synced everything as expected. The second time I ran it, imapsync copied everything over again; my disk usage doubled in the web interface; but the space used on the disk stayed roughly the same.

Deleting my account and my domain didn't free up any of the storage space used on the disk. Running stalwart-cli server database-maintenance didn't reclaim the space either. I deleted everything again and reinstalled Stalwart Mail.

For the second attempt I set most of the storage options to SQLite, but I set the blob storage to a file system folder. When I ran imapsync a second time, it recognized the existing messages and didn't copy them again.

When I deleted my account, it didn't free up any of the storage space. Running stalwart-cli server database-maintenance didn't reclaim the space. The purge frequency was set at the default of 3:00 AM, but the next morning the server was still using over 2 GB of storage, even though there were no accounts configured on the server any more.

Why would imapsync work differently depending on the back end storage options selected?

How do I reclaim the storage space used by deleted accounts?

After I set an account disk quota to any amount, I haven't been able to set it back to "none". It reverts to the last amount I set. Is it not possible to disable an account quota after one is set?

[mdecimus]

The purge tasks that you can trigger from the CLI remove references to unused blobs and other expired data. However, even if Stalwart deletes this expired data, it is up to the database (RocksDB, SQLite, etc) when this data will be actually removed from disk.
This usually occurs when the underlying database performs a compaction, but at the moment it is not possible to manually trigger a manual compaction on RocksDB but you can do it on SQLite using the sqlite3 binary.