🐛: Created a new email account, no email received, restarted the docker compose, then only started receiving the message.

[samyogdhital]

What happened?

Hi, I’ve deployed a Stalwart mail server with ~30 domains and ~60 mailboxes. I noticed a recurring issue: when I create a new account using the admin dashboard and send an email to it (e.g., from Gmail), the mailbox doesn’t receive any mail unless I restart the Docker container running Stalwart.

This doesn’t happen every time, but here’s the pattern I’ve observed:

If I create a new account shortly after restarting the container, it works fine and receives mail immediately.

However, if I haven’t created any new accounts for ~10 days and then create one, incoming mail to that new account fails silently until I restart the container.

After the restart, the new account begins receiving mail as expected.

This has happened at least twice now.

Additional details:

I’m using Amazon SES for outbound relay.

DKIM signing is disabled (handled externally by SES).

All reporting (SPF, DKIM, DMARC) is turned off.

The issue appears only with newly created accounts and only when some time (several days) has passed since the last account creation.

Can you confirm if this is expected behavior or a known issue? Have you encountered this internally?

How can we reproduce the problem?

I can reproduce the problem by doing the following steps:

• Go to dashboard, create a new mailbox.
• Send email from any other email outside stalwart.

I see this happening on v0.12 and also now in 0.13

Version

v0.13.x

What database are you using?

RocksDB

What blob storage are you using?

RocksDB

Where is your directory located?

Internal

What operating system are you using?

Docker

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[samyogdhital]

docker compose is really simple one nothing fancy.

[samyogdhital]

Any update here guys?

[mdecimus]

Hi, try setting the log level to debug or trace, send an email and check your logs for details.