Issue Description
After updating to Stalwart 0.16.25, I noticed that the SMTP listener on port 25 no longer advertised STARTTLS.
Google TLS-RPT reported incoming TLS failures with:
result-type: starttls-not-supported
Testing the SMTP listener confirmed that EHLO did not contain “250-STARTTLS”.
Stalwart is running as an application on TrueNAS 25.10.3.1 (Stalwart app package 2.0.17).
I eventually found that the generated “tn-smtp” listener was configured with TLS disabled. Manually enabling TLS in the Stalwart UI did not persist after restarting/redeploying the application.
Expected Behavior
The SMTP listener on port 25 should support explicit TLS (STARTTLS):
useTls = true
tlsImplicit = false
After EHLO, the server should advertise:
250-STARTTLS
Port 25 should remain standard SMTP with STARTTLS and should not use implicit TLS.
Reproduction Steps
-
Run Stalwart 0.16.25 using the TrueNAS Stalwart application package 2.0.17.
-
Configure the TrueNAS SMTP port as TCP 25.
-
Start/redeploy the application.
-
Connect to port 25 and send an EHLO command:
nc 25
EHLO test.example -
Observe that the SMTP capabilities do not include:
250-STARTTLS
-
In the Stalwart web interface, open the generated “tn-smtp” listener and enable TLS while keeping Implicit TLS disabled.
-
Restart/redeploy the Stalwart application from TrueNAS.
-
Check the “tn-smtp” listener again. TLS has been disabled again and STARTTLS is no longer advertised.
The TrueNAS application template generates the listener using the same boolean value for both useTls and tlsImplicit.
For SMTP port 25, the generated configuration is therefore:
useTls = false
tlsImplicit = false
I tested changing the generated configuration for “tn-smtp” to:
useTls = true
tlsImplicit = false
After redeploying the application, STARTTLS is advertised and works correctly.
Relevant Log Output
Before the change:
220 mail.example.net Stalwart ESMTP at your service
EHLO test.example
250-mail.example.net you had me at EHLO
250-SMTPUTF8
250-SIZE 104857600
250-REQUIRETLS
250-PIPELINING
250-NO-SOLICITING
250-ENHANCEDSTATUSCODES
250-CHUNKING
250-BINARYMIME
250 8BITMIME
There is no 250-STARTTLS capability.
Google TLS-RPT also reported:
result-type: starttls-not-supported
After setting useTls=true and tlsImplicit=false for tn-smtp:
250-mail.example.net you had me at EHLO
250-STARTTLS
250-SMTPUTF8
...
External verification:
openssl s_client -starttls smtp -connect <public-ip>:25 -servername mail.example.net
Result:
Verification: OK
New, TLSv1.3
Verify return code: 0 (ok)
Stalwart Version
v0.16.x
Installation Method
Docker
Database Backend
RocksDB
Blob Storage
Filesystem
Search Engine
Internal
Directory Backend
Internal
Additional Context
This report is provided for information and reproducibility. I do not require support or troubleshooting assistance
I have reviewed the documentation and FAQ and confirm that my issue is NOT addressed there.
on
I have searched this support forum (open and closed topics) and confirm this is not a duplicate.
on