Because of problems with the DNS servers for nuclearelephant.com, my server has been refusing the dspam-users mailing list for several months now. I have been waiting to see if the problem would be corrected, but it's been so long, and anyone who's server is configured with the (as far as I'm concerned) normal 'refuse unknown sender/domain' setting of their software is not getting this list either.
According to http://www.dnsstuff.com/tools/dnsreport.ch?domain=nuclearelephant.com there are quite a few problems. ERROR: One or more of the NS records that your nameservers report are invalid: 206.225.81.170. is not a valid host name (it must be a host name, not an IP address) ERROR: You have less than two nameservers. You are required to have at least 2 nameservers per RFC 1035 section 2.2 (RFC2182 section 5 recommends at least 3 nameservers). FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNSreport will not query these servers, so you need to be very careful that they are working properly. 206.225.81.170 ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are: aplus01.us.gntc.com. Your DNS servers leak stealth information in non-NS requests: Stealth nameservers are leaked [206.225.81.170.]! And... There are no NS records for lists.nuclearelephant.com to validate sender info against (such as SPF). I reconfigured my server today so only this email account does not use postfix's "reject_unknown_address" so I could see what was going on on the list. But I did not see anyone mention the DNS problems. Because the DNS servers I run and dnsstuff.com's servers agree, I thought I should mention the problem(s).
