Thanks Guys,

I'm definitely running 3.0.1 and have removed the custom rulesets that are included in SpamAssassin3. The problem isn't with the rulesets though as I was running SpamD2.64 prior with the same rulesets and had no issues.

I have written a script which simply monitors the spamd processes and if one increases above 200mb virtual it gets killed, if that fails I'll look to implementing your suggestion Justin.

I do have one further question however. I eventually figured out why I was having so many issues, the boxes didn't have fast DNS servers setup on them, and even though i have specified
dns_available no
in the local.cf file, it still was taking about 30 seconds to respond to a query. I setup an internal DNS server in the network config for the server, and all of a sudden it processes the same messages in 0.0 or 0.1 seconds.


Does the dns_available tag still function in version 3.0.1 of spamd?

Thanks guys,
- Will

----- Original Message ----- From: "Justin Mason" <[EMAIL PROTECTED]>
To: "Daniel Quinlan" <[EMAIL PROTECTED]>
Cc: "Will Kruss" <[EMAIL PROTECTED]>; <users@spamassassin.apache.org>
Sent: Wednesday, November 24, 2004 7:38 PM
Subject: Re: Weird Memory Problem



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


and try using the patch I posted recently at http://bugzilla.spamassassin.org/show_bug.cgi?id=3983 ,

- --j.

Daniel Quinlan writes:
"Will Kruss" <[EMAIL PROTECTED]> writes:

> We do have some custom rules from SARE and a couple of others =
> (chickenpox/antidrug/weeds2/bogusviruswarnings).

Some of these can require a lot of memory, they have not been through
the SpamAssassin development process.  Also, antidrug is included in
SpamAssassin 3.0.0 already.  Maybe you're running 2.64?

Set --max-conn-per-child to a lower number of messages.  That gets the
huge processes out of the way quicker.

Don't run spamc on really big messages, stick with the 250k default,
maybe go even lower.

Make sure you really need 15 children -- is that optimal for your load.
Seems like a lot for a dual, especially if you're not using any network
tests.

Daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFBpEh4MJF5cimLx9ARArgDAJwJZI3rXOW1Hwo5mVCb7qB+FzchawCgslsO
krz6VmSWwV1XJ9gRKmMTEQI=
=dLT1
-----END PGP SIGNATURE-----




Reply via email to