Mail HELO localhost #736

Closed
opened 2026-02-04 22:23:26 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @Don-Swanson on GitHub (Jul 2, 2020).

Subject of the issue

Emails being sent by the instance are often being blocked by corporate subscription spam filters because the HELO command is sending localhost as the sending mail server name. This is frowned upon and therefore usually listed as spam by many corporate filters.

Your environment

  • Bitwarden_rs version: 2.14.0
  • Install method: Docker

Steps to reproduce

Look at a pcap from email traffic

Expected behaviour

should list a server name

Actual behaviour

lists localhost

Originally created by @Don-Swanson on GitHub (Jul 2, 2020). ### Subject of the issue Emails being sent by the instance are often being blocked by corporate subscription spam filters because the HELO command is sending localhost as the sending mail server name. This is frowned upon and therefore usually listed as spam by many corporate filters. ### Your environment <!-- The version number, obtained from the logs or the admin page --> * Bitwarden_rs version: 2.14.0 <!-- How the server was installed: Docker image / package / built from source --> * Install method: Docker ### Steps to reproduce Look at a pcap from email traffic ### Expected behaviour should list a server name ### Actual behaviour lists localhost
Author
Owner

@dani-garcia commented on GitHub (Jul 5, 2020):

Checking the lettre configuration, there's an option to provide the HELO name, should I create an option for it, or is it enough to use the SMTP host as-is?

@dani-garcia commented on GitHub (Jul 5, 2020): Checking the lettre configuration, there's an option to provide the HELO name, should I create an option for it, or is it enough to use the SMTP host as-is?
Author
Owner

@Don-Swanson commented on GitHub (Jul 5, 2020):

Thanks for the quick response!
Preference would be to allow a configurable option, because another issue that would come up is if the server name presented doesn't match the reverse dns lookup of the IP (which in my case it wouldn't since its a docker container on a host with a different name and reverse dns.)

@Don-Swanson commented on GitHub (Jul 5, 2020): Thanks for the quick response! Preference would be to allow a configurable option, because another issue that would come up is if the server name presented doesn't match the reverse dns lookup of the IP (which in my case it wouldn't since its a docker container on a host with a different name and reverse dns.)
Author
Owner

@dani-garcia commented on GitHub (Jul 5, 2020):

Okay, option HELO_NAME is added now in the SMTP settings in the latest commit: 596c9b8691.

The docker images will still take some hours to build, but once done I'd appreciate if you can give it a try!

@dani-garcia commented on GitHub (Jul 5, 2020): Okay, option `HELO_NAME` is added now in the SMTP settings in the latest commit: https://github.com/dani-garcia/bitwarden_rs/commit/596c9b869185a86d7619024066c80a008102199e. The docker images will still take some hours to build, but once done I'd appreciate if you can give it a try!
Author
Owner

@Don-Swanson commented on GitHub (Jul 8, 2020):

That did the trick! Thank you so much!

@Don-Swanson commented on GitHub (Jul 8, 2020): That did the trick! Thank you so much!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#736