Replies: 1 comment
-
|
Nevermind, It was a misconfiguration by my side (wrong DNS entry for the relay). I catched the error using swaks --to noc@mydomain.com --from do-not-reply@mydomain.com --server smtp.int.mydomain.com # <--- that one has a wrong DNS entryClosing the discussion, sorry for the noise and thank you for your work! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
I have configured an SMTP relay on my homelab internal network and I want to use DMS as the exit node for my emails. In particular, I have a Grafana instance running on my homelab that is using the relay to send alerting messages. I have also configured a DMS instance on my public VPS. I created a
do-not-reply@mydomain.comaccount and it is working correctly with my e-mail client: I can send and receive emails from the account. The relay is based on this project and it's configured in order to connect to the DMS through the port 465. However, when I send an email from Grafana through the relay, I get a "relay access denied" on the DMS side. Now I'm wondering if my use case is expected or if I'm doing something wrong. Relevant configuration follows. Please note that I'm using podman-systemd quadlets instead of compose files but I don't think it could be related to the issue. Thanks in advance.EDIT: Also note that a letsencrypt certificate is generated for a
whoamicontainer in order to gettraefikautomation as in here.EDIT 2: Add log from DMS
DMS logs
smtprelay.container
mailserver.container
grafana.container (only the relevant part)
Beta Was this translation helpful? Give feedback.
All reactions