> -----Original Message----- > From: Frank Ng > Sent: Wednesday, May 28, 2003 10:52 PM > > I noticed that spams fall through after I upgraded to spamassassin 2.54, and > when I look closer, it doesn't look like spamassassin even tags them. > > I turned on procmail logging and verbose mode and this is what it saids ... > > procmail: Locking "spamassassin.lock" > procmail: Executing "/usr/local/bin/spamassassin" > procmail: [17116] Wed May 28 22:47:36 2003 > procmail: Program failure (-11) of "/usr/local/bin/spamassassin" > procmail: Rescue of unfiltered data succeeded
Here's what "man procmail" has to say about that diagnostic: Program failure (nnn) of "x" Program that was started by procmail returned nnn instead of EXIT_SUCCESS (=0); if nnn is negative, then this is the signal the program died on. Signal 11 is a "segv". Probably your MTA (ie, sendmail) isn't starting procmail with a high enough memory limit. You could try something like this: :0fw:spamassassin.lock * < 256000 | ulimit -d 15000; spamassassin and see if it gets better. ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
