You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Network Operations <no...@theabysss.com> on 2005/06/15 21:44:45 UTC
Limit the size of spamd
List;
We are an isp that currently runs through either qmail-scanner or
Plesk spamassassin. 2.6x and i believe 3.x. We are having issues with
spamd getting into the 125+mb process size at 4 to 5 processes. We
are running from Fedora to FreeBSD 4.9+ and qmail is the MTA. I have
looked and have not been able to find a way to limit scanning to to
messages <1mb. Any help would be greatly appreciated.
-s
Re: Limit the size of spamd
Posted by Ronan McGlue <r....@qub.ac.uk>.
Network Operations wrote:
> List;
>
> We are an isp that currently runs through either qmail-scanner or Plesk
> spamassassin. 2.6x and i believe 3.x. We are having issues with spamd
> getting into the 125+mb process size at 4 to 5 processes. We are running
> from Fedora to FreeBSD 4.9+ and qmail is the MTA. I have looked and have
> not been able to find a way to limit scanning to to messages <1mb. Any
> help would be greatly appreciated.
>
> -s
1MB?? wow thats a lot.. we use SA and exim and dont scan any mail
greater than 80k. Its a simple exim acl statement...
warn message = X-Spam-Score: $spam_bar ($spam_score)\n\
X-Spam-Score-Int: $spam_score_int
condition = ${if <{$message_size}{80k}{1}{0}}
spam = nobody:true
our process stay between 30-40Meg and means we can run 10 children at a
time.
--
========
Regards
Ronan McGlue
Info. Services
QUB
Re: Limit the size of spamd
Posted by Matt Kettler <mk...@comcast.net>.
At 03:44 PM 6/15/2005, Network Operations wrote:
>We are an isp that currently runs through either qmail-scanner or Plesk
>spamassassin. 2.6x and i believe 3.x. We are having issues with spamd
>getting into the 125+mb process size at 4 to 5 processes. We are running
>from Fedora to FreeBSD 4.9+ and qmail is the MTA. I have looked and have
>not been able to find a way to limit scanning to to messages <1mb. Any
>help would be greatly appreciated.
Are you running any add-on rulesets? In particular, are you using bigevil.cf?
Re: Limit the size of spamd
Posted by Mike Jackson <mj...@barking-dog.net>.
> We are an isp that currently runs through either qmail-scanner or Plesk
> spamassassin. 2.6x and i believe 3.x. We are having issues with spamd
> getting into the 125+mb process size at 4 to 5 processes. We are running
> from Fedora to FreeBSD 4.9+ and qmail is the MTA. I have looked and have
> not been able to find a way to limit scanning to to messages <1mb. Any
> help would be greatly appreciated.
Investigate the --max-conn-per-child and --max-children command line flags
for spamd. While not directly addressing the issue of SA processes expanding
to consume all available memory, --max-conn-per-child will at least kill and
restart a child after x number of messages, which definitely does the trick
for me. I have --max-conn-per-child set to 10, and --max-children set to 5.
SA only processes about 600 messages per day, but with a full complement of
SARE rules, it keeps the SA processes down to a trim 40-60MB per process.
Mike Jackson
Tech Administrator, Datahost
www.datahost.com