Garry Glendown writes: > Justin Mason wrote: > > for what it's worth, I would suggest an iterative search -- remove all > > extra rulesets, and re-add them gradually until you spot one or two > > that are causing the load issues. > > I'll try, but I still can't see that the rulesets are actually causing > this ...
Well, there are several in the past that certainly did -- bigevil, for instance. It's a known issue -- SpamAssassin does not limit rules' memory/CPU load itself, so you have to do it yourself. > I just did another check of what else might have changed since beginning > of october ... all I can see is > > - ClamAV update from 0.88.4 via 0.88.5 to now 0.88.6 > - SpamAssassin Update from 3.1.5 to 3.1.6 > > Any idea if either of those might be causing it? Dunno about clamav, but that SpamAssassin upgrade, I very much doubt it. --j.
