Arias Hung wrote:
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?
How long are messages (that are logged) taking to be scanned by
SpamAssassin when/before this happens. What timeout are you using with
spamc? You are using spamc, right, and not spamassassin?
Daryl
