code 550 (5.5.0) 'Mailbox not found. after upgrading from 0.12 to 0.13

[europacafe]

Stalwart docker: 0.13.2

I was running 0.12.4 before, and no such problem.

After upgrading my docker to 0.13.2, I can't send mail to one of my mail account ([email protected]).

I have many mail accounts registered on Stalwart.

Symptom:

• When sending a mail to this particular account ([email protected]), it bounced back with
  <[email protected]> (host 'localhost' rejected command 'RCPT TO:<[email protected]>' with code 550 (5.5.0) 'Mailbox not found.')
• When sending mails to any aliases of the [email protected] account, they all went to [email protected] inbox as expected
• When sending a mail from [email protected] to other mail accounts, it can deliver those mails as usual
• I still can login to [email protected] with my webmail clients (snappymail, cypht, and tmail-web) and all existing mails are still there.
• I don't have such a problem with other mail accounts.

I don't know what has caused the issue. Need help...thanks.

[europacafe]

just check the log file. Here is the message

2025-08-31T09:12:47Z INFO Starting Stalwart Server v0.13.2 (server.startup) version = "0.13.2"
2025-08-31T09:12:47Z ERROR Server startup error (server.startup-error) details = "Failed to migrate database, aborting startup.", reason = Store not configured (store.not-configured) { causedBy = "crates/store/src/dispatch/store.rs:64", causedBy = "crates/migration/src/lib.rs:77" }

thread 'tokio-runtime-worker' panicked at crates/jmap-proto/src/request/capability.rs:311:72:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'tokio-runtime-worker' panicked at crates/jmap-proto/src/request/capability.rs:311:72:
called `Option::unwrap()` on a `None` value

thread 'tokio-runtime-worker' panicked at crates/jmap-proto/src/request/capability.rs:311:72:
called `Option::unwrap()` on a `None` value

thread 'tokio-runtime-worker' panicked at crates/jmap-proto/src/request/capability.rs:311:72:
called `Option::unwrap()` on a `None` value

After restarting stalwart docker container, it still displays the exact same log messages, i.e. no additional log after several restarts.

[europacafe]

Since I was unsure about the cause of the issue, I resolved it by renaming the mail account to a different name and then renaming it back to [email protected].

[mdecimus]

thread 'tokio-runtime-worker' panicked at crates/jmap-proto/src/request/capability.rs:311:72:
called Option::unwrap() on a None value

This has been fixed, it looks like you were using an invalid base URL in your configuration but Stalwart should not panic if that is the case.

[stappersg]

This has been fixed

Which commit?

it looks like you were using an invalid base URL in your configuration

Was "mal formed email address" part of the invalid URL?
I'm asking because there was: resolved it by renaming the mail account to a different name and then renaming it back.

[stappersg]

On Tue, Sep 02, 2025 at 08:11:13PM -0700, bthoven wrote: resolved it by renaming the mail account to a different name and then renaming it back to ***@***.***

So there might be account names that don't get upgraded. Please report that at stalwartlabs/stalwart (not here at stalwartlabs/webadmin) and pretty please close this issue. -- Silence is hard to parse