On Mon, 05 Jun 2006, Daryl C. W. O'Shea delivered in simple text monotype:
Are all of your spamd children busy when this happens? You could have more children enabled than your system memory can support.Are you using SA < 3.1.2 and allow_user_rules? If so it could be a Perl bug being triggered. You'd see "insecure dependency" errors in your maillog if this is the case.Are you seeing any errors in your maillog? Have you looked at your maillog?
<---snip---> Hi Daryl, Thanks for your reply. I actually limit my maxchildren to 4 due to the intensive memory hogging nature of the beast. At present I'm using a recent spamassassin compiled from the svn version 3.2.0-r386260. My spamassasin logs have absolutely no trace of the spam that gets through, but my procmail logs of course record the spam going into my Inbox. That's why I'm hoping for a hint on even where to begin troubleshooting the leakage. Anything come to mind?-Arias
pgpdSgu4xmnkv.pgp
Description: PGP signature
