On Wednesday 07 January 2004 09:52, David B Funk wrote: Hi,
I was seeing the same behaviour on a SuSE 8.2 machine just before christmas. Most Emails got scanned like they should, only every few hours there has been a spamd process hanging eating up more and more memory, untill it grew so big that the machine swapped itself to death. It had nothing to do with razor, pyzor, DCC. I disabled all these tests, but the problem persisted. Now, as the machine is more than 300 kms away and is a production mail server, I think I can do no more tests unfortunately, maybe look up some things. If someone needs specific infos, I am happy to share them.;-) Note that I am running a "full featured" spamd on our Solaris box here in our institute without problems for months now... > On Wed, 7 Jan 2004 [EMAIL PROTECTED] wrote: > > This is a followup to my previous mail about a problem we are seeing > > at $DAYJOB and it is getting serious. > > > > After we upgraded to SA 2.61 as was suggested by this list we had a > > mail-machine crash again when spamd expanded beyond all available > > memory. As far as we can tell it was looking at a 1.2Mb Micro$oft > > ^^^^^^^^^^^^^^ > > > Word e-mail, ham and sent to a very senior person. Spamd is set to > > limit children (to 10 I think) but we still had this runaway. The > > system manager is pushing for withdrawing spamassassin as we cannot > > have the mail going catatonic. I am not responsible for this system, > > but was the advocate for adding spamassassin, so this matters to me > > :-) > > As a general rule, spam is not large (usually < 200KB, often under > 50KB). Scanning a 1.2MB document is almost ridiculous. > > Most SA installations bypass scanning large messages (over > 100KB~200KB). Check your system to see if there is some way to > configure that behaivor. In our above setup on the faulty linux box I had a global procmail rule with the "normal" setup to ignore mails larger than 250 kByte. So this is not the point. Also I read in http://wiki.spamassassin.org/w/ SpamdKillingServer: "If you're using spamd, you should be aware that spamc will only pass messages under 250k in size to spamd. This is a built-in limit that you can override using the "-s" option on the command-line. Refer to the spamc man page for more details." Regards Dirk -- private office Schubertstr. 43 ComNets - RWTH Aachen 52080 Aachen Lehrstuhl fuer Kommunikationsnetze Phone +49 (0) 241 961180 Phone +49 (0) 241 8793779 ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
