Since upgrading to 3.4.0 from 3.3.2 we've seen problems with all of the
spamd children blocking (for a yet unknown reason) for long enough that
the clients all give up and retry another server. Eventually, the spamd
child hits its internal timeout and then goes of and blocks indefinitely
while
: new lowest idle kid: 16819
[16816] dbg: prefork: adjust: decreasing, too many idle children (3 2),
killed 16863
[16816] dbg: prefork: new lowest idle kid: 16819
[16816] info: spamd: handled cleanup of child pid 16863 due to SIGCHLD
This is perl 5.6.1 on hacked RH 7.3.
--
Kelsey Cummings - [EMAIL
archives...
From: [EMAIL PROTECTED] (Justin Mason)
Date: Wed, 05 Sep 2001 14:10:11 +1000
Subject: [Spamassassin-talk] SpamAssassin 1.0 released
:)
--
Kelsey Cummings - [EMAIL PROTECTED] sonic.net, inc.
System Administrator 2260 Apollo Way
707.522.1000 (Voice
an anonymized data feed that looked something like:
sa scoretabspam/hamtaburltaburltaburl\n
It wouldn't be very hard to send this information in realtime.
--
Kelsey Cummings - [EMAIL PROTECTED] sonic.net, inc.
System Administrator 2260 Apollo Way
707.522.1000
On Tue, Oct 05, 2004 at 05:05:18PM -0700, Justin Mason wrote:
Kelsey Cummings writes:
On Tue, Oct 05, 2004 at 03:25:55AM -0700, Jeff Chan wrote:
4. SURBL query traffic
mostly good if you subtract the blacklisted ones
But any big, as-yet-undetected spam domains can also
