From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Thank you Matt! > > You're info is great, but I'm sure you dont mind if I take your > disclaimer seriously. > > Before I go on, anyone that uses spamd confirm this info...?
His suggestions sound right on to me. For the most part all you need to do is start up spamd and replace /usr/bin/spamassassin with /usr/bin/spamc in your procmailrc. I don't use procmail myself, so I can't give you any further details there. > From: Matt Kettler <[EMAIL PROTECTED]> > > At 01:16 PM 10/8/2004, [EMAIL PROTECTED] wrote: > >> > >> i can restart SA by using rc.d/init.d/spamassassin > >> > >> it shows in ps aux as /usr/bin/spamd -d -c -a > >> > >> and when mail comes in it shows as > >> /usr/bin/perl -T -w /usr/bin/spamassassin > > > > Suggestion: > > > > modify rc.d/init.d/spamassassin to add a -m parameter to spamd to > > limit the number of children it can spawn. Probably -m 5 to > > start, but you can estimate the correct value by looking at how > > big spamd is, and how much free ram you have using top or ps. > > Don't let spamd spawn more than will fit in free ram or it will > > end up choking your server to death. Good idea. The older (2.x) versions of spamassassin did not limit the children. Version 3.0 now preforks a default of 5 children. So if you are running 2.65 or older, you may want to tweak this. On the other hand, I've been running it without limits for over a year now without any problems. If you've got plenty of memory, you probably don't have to worry about it. > > If your existing call to spamassassin in procmailrc doesn't use > > the -a parameter, remove the -a from spamd to match (-a enables > > the auto-whitelist score-averaging system in 2.6x) Just look up your current options in the man pages and configure the comparable options for spamc and spamd. You generally don't need many options unless you want to do something fancy. > > modify your procmailrc to use spamc instead of spamassassin. It's > > much faster, has lower CPU overhead, and you'll end up with > > logging in syslog as spamd processes them. Spamc/spamd works very well. It is significantly faster than calling spamassassin for each email. Bowie
