Actually the answer is much simpler.  spamdyke will send back the TXT answer if 
it receives a TXT record from the RBL.  It will send the default A answer if it 
receives an A record from the RBL.  If the RBL returns both, spamdyke will use 
the one that arrives first.  Since DNS queries are (mostly) done over UDP, this 
can lead to intermittent behavior like what you're seeing.  (UDP packets, 
unlike TCP packets, are not guaranteed to arrive at all, much less in any 
particular order.)

I suppose there are two things you could do to fix this.  First, since you 
control all of the RBLs you're using, you could remove the A records so only 
TXT records are returned.  Or second, you could use the "dns-query-type-rbl" 
option to limit spamdyke's RBL queries to TXT records only.  Either one would 
ensure that only the TXT results are used.

-- Sam Clippinger




On Dec 8, 2011, at 4:46 PM, Lutz Petersen wrote:

> 
> I'm in trouble understanding what happens when spamdyke detects an rbl match 
> and how it generates the error message that is sending back to the blocked 
> client. The configuration is simple:
> 
> dns-blacklist-entry=one.rbl.here
> 
> There is no 'rejection-text-dns-blacklist' defined, so it should do the 
> default behavior as documented.
> 
> But, it doesn't. Or more precise, not always. Sometimes it sends back the TXT 
> message of the rbl dns request, sometimes it sends back the default-spamdyke 
> string for rbl matches. I've tested a lot, but don't find the answer why. All 
> rbl zones that are configured / checked by spamdyke are in my control 
> (rbldnsd copies of all the checked rbls). The only thing I found was that 
> some of the zones have a TXT entry for 127.0.0.2, some only for another 
> (127.0.0.3 for example). Thats quiet normal, because today most of the rbls 
> are for special cases und give different return codes; the 127.0.0.2 is only 
> the default A when no other A record is specified for a match. Could it be 
> that spamdyke only sends back the TXT record when there is a TXT record for 
> 127.0.0.2, but not for the special A record (127.0.0.A) ?
> 
> 
> _______________________________________________
> 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

Reply via email to