Sevrin Robstad wrote:
I have used spamassassin over a year on my mail server, using James as
pop/smtp and a homewritten mailet to connect to spamd through tcp.
Yesterday I suddenly discovered load average peaks over 100 (!!!) on the
server, and soon found this :
22617 spamd 18 0 1830m 1.6g 2156 D 2 54.2 2:00.59 spamd
. Yea, one instance of spamd uses 1,6 *GIGABYTE* of memory. This forces my
server to swap, which makes the server dead slow.
It happens some time after I have started SA, but mails get through fine
before this happens.
information about my system:
cat /etc/sysconfig/spamassassin
# Options to spamd (-D for debug logging)
SPAMDOPTIONS="-D -d -c -m 4 -H -u spamd"
I was using spamassassin v 3.1.9, but have now upgraded to 3.2.6, without
this fixing the problem.
plugins: I don't know which information is important so I list everything :
I'm using URIDNSBL, Hashcash and SPF, ImageInfo,
VBounce,Bayes,BodyEval,DNSEval,HTMLEval,HEaderEval,MIMEEval,RelayEval,URIEval,WLBLEval,HTTPSMismatch,URIDetail
DCC,Pyzor,Razor2,SpamCop,AWL,AutoLearnThreshold,WhiteListSubject,MimeHeader,ReplaceTags
.
No rules over 150k.
<snip>
Anybody have a clue?
Normally that's a sign of a giant ruleset.. (ie: sa-blacklist)
Have you tried running spamassassin --lint -D, and looking at the debug
output for all the rulesets parsed. Are there any you weren't aware of?
Do you have a lot (thousands) of black/whitelist entries in a user_prefs
somewhere?
