bitwarden.sh checksmtp failing

[CuzImBisonratte]

Steps To Reproduce

1. Use SSL on a mailserver using port 465 like this:

globalSettings__mail__smtp__port=465
globalSettings__mail__smtp__ssl=true

2. Use ./bitwarden.sh checksmtp

Expected Result

Response: SMTP settings are correct.

Actual Result

Actual response: SMTP authentication failed or connection error occurred.

Screenshots or Videos

Additional Context

If the configuration is right the server can still send emails using SMTP, even though the check says otherwise.

I tried the check once with the same data - but settings SSL false and port 25 - and the check responded truthfully that the config is valid.

Build Version

Server 2025.7.3 (but had that problem a few months ago as well)

Environment

Self-Hosted

Environment Details

• OS: Ubuntu 24.04

• Docker: Engine v28.3.3, Compose v2.39.1

• Hardware: Qemu based VM

• Mail Server: Netcup Webhosting Built-in Mailserver

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-25722

[NovaSilentium]

Hi there,

I attempted to reproduce your issue and was unable to do so. I think your error could have its origin in a misconfiguration. Please update your server and check that the hostname in the SMTP server's SSL certificate matches the configured globalSettings__mail__smtp__host.

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!