modoboa: DNSBL report incorrect
Just upgraded to 1.6.0 from 1.5.1
added new crontab entries then manually ran /srv/modoboa/env/bin/python /srv/modoboa/instance/manage.py modo check_mx as vmail with no errors. All DNSBL show as listed, my manual checks (where possible) show no listings. using dnsbl.info only dnsbl-3.uceprotect.net shows listed due to my server being a digital ocean droplet (minor issue).
I am unsure how to debug this issue. I have set debugging to True in settings.py is there a log file I can check?
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 20 (11 by maintainers)
Commits related to this issue
- Remove deprecated provider and full DNS names. see #921 — committed to modoboa/modoboa by tonioo 8 years ago
This issue is caused by a missing domain entry in the
resolv.conffile. An empty value might still cause issues in case your hostname is a subdomain (like mail.example.com).@tonioo I suggest to append a
.at the end of the hostname (which will force the name to be the full DNS name instead of a relative one) (e.g.bl.spamcop.net.instead ofbl.spamcop.net)The workaround until then is to add the following line to the
/etc/resolv.conf:Found the error! I had set a DNS Search Domain in my /etc/resolv.conf. socket.gethostbyname always returned the IP address of my Webserver. The Searchdomain also is the hostname of my Webserver, so it seems, when socket.gethostbyname cannot resolve the Hostname, it takes the IP of the searchdomain.
Removing the Searchdomain fixed this.
(and the script crashes if no MX is present now… mhh did I break something? 😄 the try…catch, doesn’t seem to catch the “dns.resolver.NXDOMAIN” error, which is raised if no MX is present…)
^- forget that, this seems to be already fixed in the current git master…