Replies: 3 comments 3 replies
-
You shouldn't have the default container ID if you set
Yes, the hostname is used for various services / features in DMS. It's assumed that you are in control of it.
Not sure, but you really shouldn't be configuring for domains you don't actually own. (EDIT: I just noticed the example you gave is tailored to your host, not as generic as I thought when I responded) You can also have:
You're not always going to get a perfect match there, I don't think you'll find many real services being that strict. They should just check that your EHLO resolves to an IP that rDNS domain resolves back to the same IP. That is what Postfix supports as a check, but it can perform a more relaxed one too. Consider that you're perhaps just chasing a score here that isn't that important. If you're really concerned about delivery reputation / success, you should relay through a service like SendGrid. They're better established at avoiding the problems you're concerned about.
If you really insist on this, Postfix has Perhaps you can contact your ISP to change the rDNS to point to your actual domain for DMS hostname. |
Beta Was this translation helpful? Give feedback.
-
#You shouldn't have the default container ID if you set hostname for the container as our docs instruct you to do? Thanks I re-read the example / instructions and found it too... Not sure anymore how it got missing from my config. I tried a lot to make it work behind Caddy (certificates) and with a webmail server ... Now I have put the hostname in my docker-compose config and I'm probably not spamming anymore since I found the logwatch report in my own mailbox... #Consider that you're perhaps just chasing a score here that isn't that important. reverse.DNS.name ESMTP Exim VERSION Tue, 13 Feb 2024 10:49:11 +0100 For me it seams that the announced name of the mailserver is just a name. But announcing the rDNS makes at least the mxtoolbox test and perhaps some spamfilters happier? I was just wondering would it be wrong to configure the mailserver announcement name at creation time of a container to be the rDNS name (which at least exists somewhere and can be reached, is probably also known to the owner of the server and means something in the real world) instead of the randomly generated docker container name, in cases like mine where by mistake no hostname was configured) I was meaning to ask my question in general based on my n=1 experience as I think not everybody owns or can easily (ask to) change the rDNS ... and perhaps make DMS a bit more fool proof for fools like me that somehow lost the hostname in their configuration. |
Beta Was this translation helpful? Give feedback.
-
#I'm not quite sure how you got DMS to run without configuring the hostname docker-compose.yml without any hostname configured starts fine...
And this .x.y.z is not in my DNS settings anywhere ... a host's reverse dns should probably always exist and can be figured out in 2 steps (perhaps there is even a reverse DNS PTR service like ifconfig.me for my ip address that can do it in 1 step?):
this works for me at my isp vps and my hosting community vps and also my test server in google cloud. |
Beta Was this translation helpful? Give feedback.
-
when i used https://mxtoolbox.com/SuperTool.aspx to test my new docker-mailserver based installation I got a warning that my reverse DNS name doesn't match with the announced name of the docker mailserver and that this increases the SPAM points in some cases. Postfix was announcing the hostname as .mydomain ... but this randomly generated docker name is nowhere in my DNS nor in the Reverse DNS PTR of my ISP level (which i can't control like probably many others also can't control)
I found a fix, by manually setting the docker hostname to the reverse dns name of my host ... (myhostname.ISPNNAME). mxtoolbox test all became green. I was happy.
Then next day my ISP contacted me and said i was "spamming" them.
my mailserver was sending the logwatch reports to
postmaster@ispname ... instead of to postmaster@MYHOST.ispname
(this is also written in the mailserver.env example I see now after I became a spammer)
Could postfix be configured to announces the "correct Reverse DNS name" automagically without any user intervention? The docker generated host name is nowhere to be found in any DNS and things seam to work. So if that works ... the announcing servername could perhaps also be the Reverse DNS name ... this could be configured at container creation by obtaining the reverse DNS?
Or would that break other stuff?
Beta Was this translation helpful? Give feedback.
All reactions