Sorry you have no answer yet. You might want to try emails one of the devs directly on this. Sometimes they can't read all the posts. OK, most of the time.
I don't know enough on Debian and postfix to help you :( --Chris > -----Original Message----- > From: Matthew R Anderson [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 30, 2004 12:29 PM > To: [EMAIL PROTECTED] > Subject: critical spamc/spamd problem on high volume implementation > > > Greetings- > > I'm working on a mailserver with spamassassin installed sitewide. It > receives some impressive spikes in traffic which seem to go > hand in hand > with SA crashing the machine, apparently via libc. > > It's a dual PIII 1.26ghz with 2GB of RAM running debian 3.0 > with SA 2.63 > compiled and installed by hand with no apparent problems in > that process. > It's using everything but razor and pyzor at the moment, the bayesean > filtering a must-have. > > This machine receives mail via Postfix and has been happily > receiving mail > (albeit a lot of junk with SA) for at least 6 months. It's > configured in > master.cf to inject mail into spamassassin directly. > > I'm not the quickest with my ninjitsu, but I've been pretty > good at solving > problems with this software. I've tried limiting the spamd > child processes > (-m 32) and tinkering with the spamc timeout (-t 5), and > nothing at all, and > each time when traffic spikes heavily the machine crashes and > requires a > hard reboot. > > I'd like some options and/or advice. Is there a problem with > compiling SA > by hand on a debian machine without any compiler tricks? I > can't use the > debian stable spamassassin as its spamc does not include the > functionality > to integrate it into the MTA and I don't really like the idea > of sending > this much mail through procmail. > > I can generate any further specifics as needed. This is a > high priority fix > and I'm getting sick of rebooting this machine! :) Thanks, > > /m >
