🪲: SMTP Relay not working in 0.13

[David-Development]

What happened?

I believe since version 0.13 the relay host settings are not applied anymore. I'm 90% sure that it worked in 0.12 but after the last update to 0.13 it seems like that the setting for relay host are not applied anymore. I've followed the tutorial here: https://gist.github.com/chripede/99b7eaa1101ee05cc64a59b46e4d299f#smtp-relay to set up an smtp relay. However, when I use the troubleshooting page it tries to send the email directly without respecting the relay setting.

I've also tried using the config.toml to set the rules manually (and not via the UI), but it seems like the rules are not applied at all (even though I've added the queue.strategy.route to the local settings

Here is the log from the troubleshooting page: Img

Configuration:

How can we reproduce the problem?

I can reproduce the problem by doing the following steps:

1. Setup SMTP Relay
2. Go to Troubleshooting and send an email (to an external email address) -> Check the Log it will say that it used the internal one

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

...
2025-10-12T15:58:57Z TRACE HTTP request body (http.request-body) listenerId = "http", localPort = 8080, remoteIp = 10.X.0.X, remotePort = 41118, details = [["host", "mail.xxx.it"], ["user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36"], ["accept", "*/*"], ["accept-encoding", "gzip, deflate, br, zstd"], ["accept-language", "de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7"], ["authorization", "Bearer XXX"], ["priority", "u=1, i"], ["referer", "https://mail.xxx.it/manage/troubleshoot/delivery"], ["sec-ch-ua", ""Chromium";v="140", "Not=A?Brand";v="24", "Google Chrome";v="140""], ["sec-ch-ua-mobile", "?0"], ["sec-ch-ua-platform", ""macOS""], ["sec-fetch-dest", "empty"], ["sec-fetch-mode", "cors"], ["sec-fetch-site", "same-origin"], ["x-forwarded-for", "xxx"], ["x-forwarded-host", "mail.xxx.it"], ["x-forwarded-port", "443"], ["x-forwarded-proto", "https"], ["x-forwarded-server", "xxx"], ["x-real-ip", "xxx"]], contents = "", size = 0
2025-10-12T15:58:57Z TRACE HTTP response body (http.response-body) listenerId = "http", localPort = 8080, remoteIp = 10.X.0.X, remotePort = 41118, contents = "{"data":"XXX"}", code = 200, size = 103
2025-10-12T15:58:57Z DEBUG HTTP request URL (http.request-url) listenerId = "http", localPort = 8080, remoteIp = 10.X.0.X, remotePort = 41118, url = "/api/troubleshoot/delivery/redacted%40hotmail.de?token=XXX"
2025-10-12T15:58:57Z TRACE Expression evaluation result (eval.result) listenerId = "http", localPort = 8080, remoteIp = 10.X.0.X, remotePort = 41118, id = "http.allowed-endpoint", result = "Integer(200)"
2025-10-12T15:58:57Z TRACE Write batch operation (store.data-write) elapsed = 0ms, total = 2
2025-10-12T15:58:57Z TRACE HTTP response body (http.response-body) listenerId = "http", localPort = 8080, remoteIp = 10.X.0.X, remotePort = 41118, contents = "[stream]", code = 200, size = 0
2025-10-12T15:58:57Z TRACE Raw SMTP input received (delivery.raw-input) contents = "220 DB3PEPF0000885A.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Sun, 12 Oct 2025 15:58:56 +0000 [xxx]\r\n", size = 138
2025-10-12T15:58:57Z TRACE Raw SMTP input received (delivery.raw-input) contents = "250-DB3PEPF0000885A.mail.protection.outlook.com Hello [84.132.154.51]\r\n250-SIZE 49283072\r\n250-PIPELINING\r\n250-DSN\r\n250-ENHANCEDSTATUSCODES\r\n250-STARTTLS\r\n250-8BITMIME\r\n250-BINARYMIME\r\n250-CHUNKING\r\n250 SMTPUTF8\r\n", size = 212
...

Code of Conduct

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

[David-Development]

Most likely a duplicate of #2211

[mdecimus]

The configuration format changed, always read the changelog before upgrading:

https://github.com/stalwartlabs/stalwart/blob/main/UPGRADING.md#upgrading-from-v012x-and-v011x-to-v013x