Folks,
I have a large whitelist (380M) and this code is death when remove_entry
is called:
if ($addr =~ /^(.*)\|ip=cmd$/) {
# it doesn't have an IP attached.
# try to delete any per-IP entries for this addr as well.
# could be slow...
my $mailaddr = $1;
my @keys = grep { /^\
[ Apologies if this already appeared; I don't see it in the archives. ]
Howdy,
Just upgraded to 2.60, seems to work great for the most part! Catching
even more spam than before (as to be expected).
One thing which has become a bit of a problem - AWL seem to be much slower
in some cases, althoug
Howdy,
Just upgraded to 2.60, seems to work great for the most part! Catching
even more spam than before (as to be expected).
One thing which has become a bit of a problem - AWL seem to be much slower
in some cases, although I'm not sure why. My AWL is currently 146M, so
it's pretty hefty. I'v
On Fri, 29 Aug 2003, Simon Byrnand wrote:
> Generally the situation for us anyway is that we have fast DNS available
> but individual blacklists may stop replying as osirusoft did... its not
> common for the response time of all lists to be slow at once, so it looks
> like the above scheme may wor
Folks,
With respect to the OSIRU DNS problems recently, we had the situation
where SpamAssassin suddenly went from taking one second to process a
message to 30 seconds or more. Mail suddenly started backing up, and we
ended up with a real train wreck - mail volume was much higher than usual
due t
