Paul Matthews wrote: >> Are you using sa-update? >> > > i'm not sure, how do i know if i am, but i did a locate sa-update and i > came up with nothing so i have to guess that i'm not. >
What version of SA are you using? If older than 3.1.1, consider upgrading to the current version before adding on extra rulesets. > Although, i've found the website > > http://www.sa-blacklist.stearns.org/sa-blacklist/ > > and i've add the following information into a script and set it to run as > a cron job once a week. > > wget http://www.sa-blacklist.stearns.org/sa-blacklist/sa-blacklist.current.cf > wget > http://www.sa-blacklist.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf > wget http://www.sa-blacklist.stearns.org/sa-blacklist/random.current.cf > > Has anyone out there used this website? is it any good? does it work? > DO NOT use the sa-blackset rules. Either of them. 1) sa-blacklist is based on email addresses. This is not a very effective tactic for fighting spam. 2) sa-blacklist is a nearly 2meg file, which will increase your spamd size by about 100 megs per-instance. This massive memory increase will grind most boxes to a halt. 3) sa-blacklist-uri is superseded by the URIBL test URIBL_WS_SURBL. This test is more accurate (it's a live query to DNS, thus rapidly updated) and uses much less memory. However, it does require use of DNS.
