On Tue, Jun 10, 2008 at 11:09 AM, Shane Bywater <[EMAIL PROTECTED]> wrote: > Hi, > I have just recently started using spamdyke and am finding it very > useful but have a concern with some of the DENIED_SENDER_NO_MX entries > in the logs. I'm thinking sometimes spamdyke incorrectly determines > that there is no MX for a particular domain when in fact there is. > Below is one such example. > > Jun 10 04:47:37 server1 spamdyke[30647]: DENIED_SENDER_NO_MX from: > [EMAIL PROTECTED] to: [EMAIL PROTECTED] origin_ip: > 209.226.175.35 origin_rdns: tomts14-srv.bellnexxia.net auth: (unknown) > > but when I execute "dig mx ancochemicals.com" on the same server as > spamdyke is running I get the following: > > server1# dig mx ancochemicals.com > > ; <<>> DiG 9.3.1 <<>> mx ancochemicals.com > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27206 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3 > > ;; QUESTION SECTION: > ;ancochemicals.com. IN MX > > ;; ANSWER SECTION: > ancochemicals.com. 107910 IN MX 10 > sf1.capris.net.ancochemicals.com. > > ;; AUTHORITY SECTION: > ancochemicals.com. 107910 IN NS dns2.capris.net. > ancochemicals.com. 107910 IN NS dns3.capris.net. > ancochemicals.com. 107910 IN NS dns1.capris.net. >
Shane: Are you by chance using 'bind' for your DNS server? If so, check to make sure you have the trailing "dot" at the end of your MX record entry in your zone. Without this dot the server appends the name of the zone to the entry resulting in something like "sf1.capris.net.ancochemicals.com." instead of "sf1.capris.net." Hope this helps! -ken -- Have a nice day ... unless you've made other plans. _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
