Hello Matt, Thursday, July 24, 2003, 8:20:58 PM, you wrote:
MK> Sounds like you need locking to keep there from being an infintite number MK> of simultaneous instances of spamassassin. MK> You should have something like this: MK> :0fw: spamassassin.lock MK> * < 256000 MK> | spamassassin Matt, thanks for the great tip, but it didn't solve my problem. I disabled Bayes and then modified procmail as you suggested, and a large, legit email from a previously unknown user (not whitelisted) with a 30k attachment went through without a hitch. Then I re-enabled Bayes, and SA choked and crashed on a small email (under 2k) with another out of memory error - so I think it's got to be a problem with the Bayes database. I did run sa-learn --build (even before I posted), and that didn't seem to do any good. -Abigail ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
