On Thu, 7 Oct 2004, Jeff Tucker wrote: > I captured an exact copy of one of the messages that was being scanned > when this happened. > [ ... ] > Rescanning the same message by calling spamc didn't cause the > problem. The scan completed in just a couple of seconds.
I did exactly the same experiment with the same result. You have Bayes turned off, I have it on. I'm also using auto-whitelist. Clearly there's nothing significant about the triggering message. I'm doing fine with --max-conn-per-child=10 for now. Cheers, Mojo -- Morris Jones <*> Monrovia, CA [EMAIL PROTECTED] http://www.whiteoaks.com
