Re: [spamdyke-users] DENIED_SENDER_NO_MX issue?

2008-06-11 Thread Shane Bywater
I hope I'm replying to this post correctly.  Ken I am using BIND but 
ancochemicals.com isn't a domain in my control.  It looks like I just 
have to wait another 7700 seconds and then I'm hoping this zone should 
be updated correctly.

server1# dig mx ancochemicals.com

;  DiG 9.3.1  mx ancochemicals.com
;; global options:  printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 43887
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3

;; QUESTION SECTION:
;ancochemicals.com. IN  MX

;; ANSWER SECTION:
ancochemicals.com.  7700IN  MX  10 
sf1.capris.net.ancochemicals.com.

;; AUTHORITY SECTION:
ancochemicals.com.  7700IN  NS  dns1.capris.net.
ancochemicals.com.  7700IN  NS  dns2.capris.net.
ancochemicals.com.  7700IN  NS  dns3.capris.net.

;; ADDITIONAL SECTION:
dns1.capris.net.18525   IN  A   204.10.240.130
dns2.capris.net.18525   IN  A   204.10.240.131
dns3.capris.net.18525   IN  A   204.10.240.133

Regards,
Shane

 
 --
 
 Message: 1
 Date: Tue, 10 Jun 2008 16:06:46 -0400
 From: Ken Schweigert [EMAIL PROTECTED]
 Subject: Re: [spamdyke-users] DENIED_SENDER_NO_MX issue?
 To: spamdyke users spamdyke-users@spamdyke.org
 Message-ID:
   [EMAIL PROTECTED]
 Content-Type: text/plain; charset=ISO-8859-1
 
 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


___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users


Re: [spamdyke-users] DENIED_SENDER_NO_MX issue?

2008-06-10 Thread Sam Clippinger
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
 spamdyke-users@spamdyke.org
 http://www.spamdyke.org/mailman/listinfo/spamdyke-users
   
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users