Quoting Sean Kennedy <[EMAIL PROTECTED]>:
Sorry for replying to my own topic, but I've figured out what's causing
it to go so slow.
It's the rules in sa-blacklist.current.uri.cf from
http://www.sa-blacklist.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf.
This ruleset works fine in 3.1, I
Sean Kennedy wrote:
Sorry for replying to my own topic, but I've figured out what's
causing it to go so slow.
It's the rules in sa-blacklist.current.uri.cf from
http://www.sa-blacklist.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf.
This ruleset works fine in 3.1, I'm not sure why it
On Fri, 15 Feb 2008, Sean Kennedy wrote:
It's the rules in sa-blacklist.current.uri.cf from
http://www.sa-blacklist.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf.
This ruleset works fine in 3.1, I'm not sure why it doesn't in 3.2, any
insight?
Don't use it. It's a huge list of URIs t
Sorry for replying to my own topic, but I've figured out what's causing
it to go so slow.
It's the rules in sa-blacklist.current.uri.cf from
http://www.sa-blacklist.stearns.org/sa-blacklist/sa-blacklist.current.uri.cf.
This ruleset works fine in 3.1, I'm not sure why it doesn't in 3.2, any
i
I recently upgraded from v3.1.9 to v3.2.4 and I've noticed a substantial
increase in scan times. The general average scantime with v3.1 was
about 1.2s and now with v3.2 it's about 2.2s. It's enough of a slow
down so that my mail queue backs quite easily now.
So I'm trying to debug SA and fig
