Alias / account editing consistency whith auth against external sqlite DB

[speters]

For my small personal mailserver, I have my mail users authenticate against an sqlite database.

The database is set up as written in the stalwart documentation.

The stalwart webadmin interface shows the accounts and allows adding aliases:

So the alias seems to be stored somewhere.

But the new alias is not in use:

For other account operations like setting a password, the webadmin tells that this wasn't possible:

After such a failed account edit, the previously added alias is gone, the number of aliases matches the number of aliases of this user in the database again.

This looks like an inconsistency in the web admin. As a user, I would expect that I can either edit something reliably. Or I can not edit at all (e.g. just list).

[speters]

• When adding an alias via INSERT into the db, this alias is not recognized, even after a daemon restart via systemctl.

  It needed a stalwart-cli -c $ADMINPASS -u $URL server database-maintenance to make the new alias appear.

  Maybe this has something to do with the cache setting (kept default 1h TTL for positive, 10min TTL for negative).

• If I would set the rcp_to directory from '*' to 'mysqlitedir' (my sqlite database directory used for authentication: Would this affect also the special postmaster handling (my understanding is that postmaster is treated automatically for reporting - or is it neccessary to add a postmaster account/alias?)

• the use of quotas in conjunction with the sqlite auth is unclear All users in screenshot have 10737418240 (10GB) quota set, but only one user has percentage quota shown: