Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Use hostname FQDN when sending email

See original GitHub issue

Description

When emails are sent via Overseerr the header contains Received: from [127.0.0.1].

This can cause issues with some ESPs marking the email as spam as the sending server has not declared itself properly.

Desired Behavior

Ideally the sending server is supposed to specify the FQDN, not doing so leaves the email marked as spam in some ESPs

Additional Context

Radarr uses /etc/hosts to provide a unique ID from the container which is enough to actually get around the spam filter but it would be nice to properly specify the hostname.

When using host networking Docker will pull /etc/hosts from the Host OS into the container. Using the FQDN in /etc/hosts would be best way to go imo

Issue Analytics

State:
Created 2 years ago
Comments:7

Top GitHub Comments

1reaction

pro4tlzzcommented, Apr 27, 2021

@pro4tlzz I think the application URL should be used as the hostname? We should be able to parse the application URL to be the hostname. We can then set a dummy hostname if that setting is blank?

That would be a good idea, it is easier to pull the FQDN from their than trying to locate the host file for each OS

0reactions

github-actions[bot]commented, May 5, 2021

🎉 This issue has been resolved in version 1.24.0 🎉

The release is available on: