bug report: relay map does not take effect about docker-mailserver HOT 5 CLOSED

I just confirmed the edge image improves the behavior -- no need to set a RELAY_HOST for the map to work.

from docker-mailserver.

@gszr thanks for the follow-up comments, it's helpful for other users that land on the issue 👍

Hoping to get v14 published in April with the much better relay host support!

from docker-mailserver.

Please note that this response was created using generative AI, leveraging previously available information from the repository. This information may be helpful. However, it is our strong recommendation that you carefully consider the information before blindly applying it.

It seems like your relay configuration is not being applied as expected. Based on the information provided and the documentation, here are a few steps and checks to ensure your relay setup works correctly:

1. Verify Configuration Files: Ensure that the postfix-relaymap.cf and postfix-sasl-password.cf files are correctly configured and located in the correct directory (mail/config/). These files should contain the relay domain and authentication details you've set up.

2. Check for Typos: Double-check the domain names, email addresses, and passwords for any typos. It's crucial that these details are accurate for the relay to work.

3. Restart the Container: After making changes to the configuration or adding relay settings, ensure you restart the Docker container to apply these changes. Use docker-compose down and then docker-compose up -d to restart the container.

4. Check DMS Version: Ensure you are running a version of DMS that supports the relay features you are trying to use. You mentioned running version 13.3.1, which should support these features, but it's always good to check the DMS GitHub repository for any updates or changes related to relay configurations.

5. Review Relay Configuration Steps: Refer to the Relay Hosts documentation to ensure all steps were followed correctly. Pay special attention to the setup relay add-domain and setup relay add-auth commands and their parameters.

6. Debugging Logs: Since you have DMS_DEBUG=1 enabled, review the detailed debug logs for any errors or warnings related to the relay setup. This can provide clues on what might be going wrong.

7. Ensure No Conflicting Configurations: Make sure there are no conflicting configurations in your docker-compose.yml or in the DMS environment variables that might be overriding or interfering with your relay setup.

If after following these steps your issue persists, consider reaching out to the DMS community on GitHub by creating an issue with detailed information about your setup, steps taken, and logs observed. The community or the maintainers might be able to provide more specific guidance.

This comment was generated by Glime.

from docker-mailserver.

Folks, I might have been a bit hasty in opening this as an issue. I will take some more time to investigate what is going on and reopen if needed. Apologies for the noise.

from docker-mailserver.

In case others come across this issue.
I was trying to route only emails sent from my @acm.org alias through ACM's Mailroute smtp server. I did run both ./setup.sh relay add-domain and ./setup.sh relay add-auth acm.org, but it still did not work. Looking at the code, I saw that RELAY_HOST needs to be set for the relay map to apply. I also found #3607, which seems to be fixed (I did not test) in the master branch. Setting RELAY_HOST to " " - just to test - the acm.org map worked, but now any mail sent from my smtp server fails.

from docker-mailserver.