Paul Houlbrooke wrote: Kevin wrote: >> Paul Houlbrooke wrote: >>> Kevin wrote: >>>> Paul Houlbrooke wrote: >>>>> Looks like IPs listed in the DNSBLcache are not getting fully blocked, >>>>> instead they are continuing on until the actual DNSBL test is run. >>>> What is 'ForceRBLCache' set to? >>> It's off. >> Then nothing is wrong. >> Turn if on if you want the DNSBL cache hits to be blocked earlier. >> >> Kevin >> > > The DNSBL cache hits are not being blocked at all. Why would I have to > enable ForceRBLCache (which moves the test to before delaying) to have > them block? Or am I just misreading the ForceRBLCache description?
This is a normal DNSBL cache block from the logs in your first message. --------- SPAM FOUND (89.132.3.160 listed in zen.spamhaus.org, DNSBLcached at 08-01-14/13:32) ---------- The IP was found in the cache and blocked as it should have been. > "If set, ASSP will use DNSBL cache hits to block the failed IP's before > DELAYING kicks in." > > I take that to mean if it is not set then the DNSBLcache test will occur > after delaying. Is that incorrect? No, that is not quite what it means. Normally the DNSBL code checks the cache before it does a DNS lookup for the IP. If the IP is in the cache ASSP does not bother doing a DNS lookup. When 'ForceRBLCache' is enabled. ASSP performs a DNSBL cache lookup VERY early in the smtp connection rather than waiting for the normal DNSBL test. Kevin ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
