I simply made sure that before every spam statement was the condition
and since that time: no problems with CPU and Mem
Wolfgang
> Why do you include the "condition = ${if <{$message_size}{500k}{1}
> {0}}" twice ?
> GTG
> >>> <Wolfgang.Fuertbauer@???> 11/08/2005 16:26:50 >>>
> I had the same problem: the fault was in the configuration file:
> take care that the 'condition' statement is before the 'spam' statement
> otherwise EVERY mail well be send to spamd and hat consumes LOTS of
> memory and CPU
> warn message = X-Spam-Score: $spam_score ($spam_bar)
> condition = ${if <{$message_size}{500k}{1}{0}}
> spam = exim:true
> warn message = X-Spam-Report: $spam_report
> condition = ${if >{$spam_score_int}{40}{1}{0}}
> spam = exim:true
> # Add X-Spam-Flag if spam is over system-wide threshold
> warn message = X-Spam-Flag: YES
> condition = ${if <{$message_size}{500k}{1}{0}}
> spam = exim
>
> # Reject spam messages with score over 5, using an extra condition.
> deny message = SPAM This message scored $spam_score SPAM points.
> condition = ${if >{$spam_score_int}{50}{1}{0}}
> spam = exim:true
>
> hope that helps
> Wolfgang
----------------------------------------------------------------------
Wolfgang Fuertbauer (e-Mail: Wolfgang.Fuertbauer@???)
EBEWE Pharma
Mondseestrasse 11
4866 Unterach, Austria
Tel +43 7665 8123 315
Fax +43 7665 8123 11
http://www.ebewe.com
