The problem is not that the MX record doesn't exist; it's that the MX record name doesn't have a corresponding A record. In other words, there is no IP address for "sf1.capris.net.ancochemicals.com".
That name may be an error however; when I query ancochemicals.com from here, nslookup reports the MX record is "sf1.capris.net", not "sf1.capris.net.ancochemicals.com". It's possible their DNS records are improperly zoned or they've updated them recently. If you want to see which records spamdyke is using, increase the "log-level" setting in your spamdyke configuration to 4. That will force spamdyke to print debugging statements into the log, including information about DNS queries. -- Sam Clippinger Shane Bywater 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. > > ;; ADDITIONAL SECTION: > dns1.capris.net. 118735 IN A 204.10.240.130 > dns2.capris.net. 118735 IN A 204.10.240.131 > dns3.capris.net. 118735 IN A 204.10.240.133 > > To me the above shows that there does in fact exist a MX record for > anochemicals.com. That being sf1.capris.net.ancochemicals.com. If > someone can either verify that what I'm thinking is correct or tell me > why my thinking is wrong that would be appreciated. > I'm running Spamdyke 3.1.8, FreeBSD 6.0, Plesk 8.0.1 on the server. > > Regards, > Shane Bywater > > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
