Trying to learn Stalwart

[dustinwilson]

Hi. I currently run a mail server for myself and have been interested in Stalwart for a while now. I decided to start poking around. I'm running the docker container. Currently using postfix I have a sqlite database and have it configured to query that database for almost everything pertaining to accounts and auth. I was hoping to replicate that somewhat in Stalwart. I'm nowhere near that point yet. Mostly, I've just been digging through the configuration and trying things out. I've sort of run into a snag just playing around with the different storage types:

[directory."default"]
type = "sql"
store = "directory"

[directory."default".columns]
name = "name"
description = "description"
secret = "secret"
email = "address"
quota = "quota"
class = "type"

[lookup."default"]
hostname = "test.home"

[server.listener]
http.bind = "[::]:80"
http.protocol = "http"
imap.bind = "[::]:143"
imap.protocol = "imap"
imaptls.bind = "[::]:993"
imaptls.protocol = "imap"
imaptls.tls.implicit = true
sieve.bind = "[::]:4190"
sieve.protocol = "managesieve"
smtp.bind = "[::]:25"
smtp.protocol = "smtp"
submission.bind = "[::]:587"
submission.protocol = "smtp"

[storage]
blob = "blob"
data = "data"
directory = "directory"
fts = "fts"
lookup = "lookup"

[store."blob"]
type = "rocksdb"
compression = "lz4"
path = "/opt/stalwart-mail/storage/blob"

[store."data"]
type = "fs"
depth = 2
path = "/opt/stalwart-mail/storage/data"

[store."directory"]
type = "sqlite"
path = "/opt/stalwart-mail/storage/directory.db"

[store."directory".query]
name = "SELECT name, type, secret, description, quota FROM accounts WHERE name = ? AND active = true"
members = "SELECT member_of FROM group_members WHERE name = ?"
recipients = "SELECT name FROM emails WHERE address = ?"
emails = "SELECT address FROM emails WHERE name = ? AND type != 'list' ORDER BY type DESC, address ASC"
verify = "SELECT address FROM emails WHERE address LIKE '%' || ? || '%' AND type = 'primary' ORDER BY address LIMIT 5"
expand = "SELECT p.address FROM emails AS p JOIN emails AS l ON p.name = l.name WHERE p.type = 'primary' AND l.address = ? AND l.type = 'list' ORDER BY p.address LIMIT 50"
domains = "SELECT 1 FROM emails WHERE address LIKE '%@' || ? LIMIT 1"

[store."directory".init]
execute = [
    "CREATE TABLE IF NOT EXISTS accounts (name TEXT PRIMARY KEY, secret TEXT, description TEXT, type TEXT NOT NULL, quota INTEGER DEFAULT 0, active BOOLEAN DEFAULT 1)",
    "CREATE TABLE IF NOT EXISTS group_members (name TEXT NOT NULL, member_of TEXT NOT NULL, PRIMARY KEY (name, member_of))",
    "CREATE TABLE IF NOT EXISTS emails (name TEXT NOT NULL, address TEXT NOT NULL, type TEXT, PRIMARY KEY (name, address))"
]

[store."fts"]
type = "rocksdb"
compression = "lz4"
path = "/opt/stalwart-mail/storage/fts"

[store."lookup"]
type = "rocksdb"
compression = "lz4"
path = "/opt/stalwart-mail/storage/lookup"

[tracer.log]
ansi = false
enable = true
level = "info"
path = "/opt/stalwart-mail/logs"
prefix = "stalwart.log"
rotate = "daily"
type = "log"

I created a separate store for each storage. I know that's unconventional, but I'm just exploring. Everything's lifted almost verbatim from the documentation with only the names of the stores being different. This configuration, however, doesn't work. The log shows this:

2024-06-23T14:12:22.794444Z  INFO common::manager::boot: Starting Stalwart Mail Server v0.8.2...
2024-06-23T14:12:23.099580Z ERROR smtp::reporting::scheduler: Failed to read from store: Internal Error: No store configured context="queue" event="error"
2024-06-23T14:12:23.099931Z  WARN jmap: Failed to unpack webadmin bundle. event="error" error=InternalError("No store configured")
2024-06-23T14:12:23.099998Z ERROR utils::config: Build error for key "storage.*": One or more stores are missing, disabling all stores
2024-06-23T14:12:23.100000Z ERROR utils::config: Build error for key "*": Failed to update configuration: Internal Error: No store configured
2024-06-23T14:12:23.100002Z ERROR utils::config: Failed to parse setting "storage.data": Data store "data" not found
2024-06-23T14:12:23.100003Z ERROR utils::config: Failed to parse setting "storage.directory": Directory "directory" not found
2024-06-23T14:12:23.100008Z  INFO common::listener::listen: Starting listener id="http" protocol=Http bind.ip="::" bind.port=80 tls=false
2024-06-23T14:12:23.100030Z  INFO common::listener::listen: Starting listener id="imap" protocol=Imap bind.ip="::" bind.port=143 tls=false
2024-06-23T14:12:23.100038Z  INFO common::listener::listen: Starting listener id="imaptls" protocol=Imap bind.ip="::" bind.port=993 tls=true
2024-06-23T14:12:23.100045Z  INFO common::listener::listen: Starting listener id="sieve" protocol=ManageSieve bind.ip="::" bind.port=4190 tls=false
2024-06-23T14:12:23.100051Z  INFO common::listener::listen: Starting listener id="smtp" protocol=Smtp bind.ip="::" bind.port=25 tls=false
2024-06-23T14:12:23.100057Z  INFO common::listener::listen: Starting listener id="submission" protocol=Smtp bind.ip="::" bind.port=587 tls=false
2024-06-23T14:12:23.100108Z ERROR jmap::services::index: Failed to iterate over index emails context="fts_index_queued" event="error" reason=InternalError("No store configured")
2024-06-23T14:12:23.102273Z ERROR smtp::queue::spool: Failed to read from store: Internal Error: No store configured context="queue" event="error"

As far as I can tell both are configured in the config.toml file. The folders were created in /opt/stalwart-mail/storage. The sqlite database was created by Stalwart in /opt/stalwart-mail/storage/directory.db and the tables were even created as specified in the init section. However, Stalwart insists they are not there. It seems that if I set any storage to a store that is something other than rocksdb it won't accept it. What am I doing wrong?

[dustinwilson]

I figured out what the problem was with the directory storage. The value is the name of the directory, not the store, so in my case it should be:

directory = "default"

That's a bit confusing considering the rest of the values are the store names. But anyway, the issue with storage.data remains. If I set it to a rocksdb storage it works, but if it's a fs storage it doesn't.

[dustinwilson]

Another curiosity is that Stalwart also creates a bunch of other tables in the directory sqlite database:

sqlite> .tables
a              e              h              m              s            
accounts       emails         i              n              t            
b              f              j              p              u            
c              g              k              q              v            
d              group_members  l              r

When looking at their schemas they're all for blob storage. I didn't set up sqlite for blob storage. It's for directory storage. I don't see why it should be creating tables that I didn't specify in the configuration.

[mdecimus]

When looking at their schemas they're all for blob storage. I didn't set up sqlite for blob storage. It's for directory storage. I don't see why it should be creating tables that I didn't specify in the configuration.

Those tables are only created in your SQL database if you're using it as a data store. Stalwart uses the SQL database as a key value store so all tables just have two columns k and v and in some cases only k.

[dustinwilson]

It should create them even if it's being used as a directory store and not a data store?

[mdecimus]

No, that is a bug that has been reported previously and will be fixed in future releases.

[dustinwilson]

I've taken my time with this making sure I have things configured correctly, and I made the switch today. I have some additional questions:

1. I copied over my mail from dovecot maildir, and now I have a bunch of duplicate folders that look like this:

   Archive
   .Archive
   Drafts
   .Drafts
   ...
   

   They seem to be duplicated data. I don't know for certain yet because I'm still downloading mail from the server. Has anyone seen this before? If so, can I just safely delete the other folders?

2. I have a gmail account that is set up to forward email delivered to it back to me. If I send email from Stalwart to my gmail account I see in the logs that the mail has been sent back to me, but nothing ends up in my inbox. When doing the same thing with postfix+dovecot the mail would show up in my inbox. If I manually send from my gmail account it ends up in my inbox just fine, though. Is there say some setting that prevents email I've sent from showing up in my inbox again?

3. I'm seeing a lot of warnings that have to do with the default sieve scripts that were set up that look like this:

   common::scripts::plugins::lookup: context="sieve:key_exists_http" event="failed" resource="http://data.phishtank.com/data/online-valid.csv" status=429 Too Many Requests
   

   Is there something I can do to mitigate this? I didn't see this in my testing before. I was restarting the server a lot during this period because of silly mistakes on my part, so maybe that has something to do with it?

Thanks!

[mdecimus]

They seem to be duplicated data. I don't know for certain yet because I'm still downloading mail from the server. Has anyone seen this before? If so, can I just safely delete the other folders?

Yes, make sure there are no messages in the folders and then delete them.

I have a gmail account that is set up to forward email delivered to it back to me. If I send email from Stalwart to my gmail account I see in the logs that the mail has been sent back to me, but nothing ends up in my inbox. When doing the same thing with postfix+dovecot the mail would show up in my inbox. If I manually send from my gmail account it ends up in my inbox just fine, though. Is there say some setting that prevents email I've sent from showing up in my inbox again?

Perhaps it is going to your Junk Mail folder? Try setting the log level to trace to see where the messages are being delivered to.

Is there something I can do to mitigate this? I didn't see this in my testing before. I was restarting the server a lot during this period because of silly mistakes on my part, so maybe that has something to do with it?

You can safely ignore this warning. The phishing list service has a rate limiter and your server has exceeded the rate since you restarted it multiple times and the list is downloaded at startup.