hi, On Tue, 21 May 2002 08:50:57 -0500, Joel Epstein wrote: JE> I've been using Spam Assassin for a few months now and find it to be JE> a fantastic project. My thanks go out to the team! JE> JE> I do have one major issue though; Whenever files with large JE> attachments ( > 4mb )are sent into our domain, SpamAssassin will JE> take about 45% of available memory and 98% of the processor JE> according to output from the top command.
do you use spamassassin directly or spamc/spamd? By default, only mails smaller than 250 KB are passed through spamd by spamc. However, there is no such limit when you're using spamassassin -P. Analyzing mails bigger than 250k doesn't make much sense because spam is normally between 5 and 20 KB in size and matching the rules on big mails takes lots of time and heavy CPU usage. JE> After about 10 minutes of churning, the mail will be returned to the JE> JE> sender with a SERVICE UNAVAILABLE message. Processor usage will JE> return to normal at this point. Occasionally, the mail will get JE> stuck in the mail queue, and oddly enough... actually append itself JE> to other messages. In other words, normal small unrelated emails JE> may suddenly become 5 mb, with their original content plus that of JE> the stuck mail that is very strange - something must be wrong with your sendmail, too? tobias -- .deSecure Digital Security www.desecure.de _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
