Thanks for the response - unfortunately - there aren't any local, custom rules. I even removed all of the RulesDuJour whilst testing.
I blew away SA today and am re-installing via CPAN - I think it may be something to do w/ my Perl installation as a whole... Plausible??? I've reinstalled 3 times w/ the same appalling results 10-15 minute scanning... the SA and Amavis builds are by the book! Plus I've got other working machines that provide the basis of the limited configuration options... I'm just about at the end of my tether... I remember when I was settling dependencies for Amavisd, I had lots of problems w/ Math::Pari, bignum, all the RSA stuff and did a few 'forced' installs in the build directory. I've been fighting w/ these machines for 3 weeks now and it's the only variable that I've not explored... RE: the 66mhz - no it's a Poweredge PIII w/ 512 of ram - all it does is filter SA, act as a backup SQUID proxy, an infrequent SSL apache pass through and backup MX. thanks again., all the best. -Peter Farrell
On 18/06/07, Loren Wilton <[EMAIL PROTECTED]> wrote: > Three minutes for regex processing is very much NOT normal, unless you are > running on a 66mhz box or the like. > > First question: are you thrashing? That is the number one reason for slow > SA processing, you have run out of memory for one reason or another. > > If the 3 minutes is CPU time and you aren't thrashing, you have a bad regex > that is getting looped up. Probably something with a number of *'s and > backtracking in it. While it is possible this could be a release or SARE > rule that has found some creative way to fail on your system, I would be > more inclined to suspect a locally-crafted rule. > > There is some technique that can be used to time the individual rules, but > I'm not sure what it is. > > Loren > > >
