I think I've completely overlooked us not having an idle time-out. Turning the logging on, I noticed that the processes were getting stuck were definitely spammers. I'd say the issue is is exactly how Sam describes it on the website:
"Most spam software is pretty stupid and doesn't handle error codes from SMTP servers. Instead, they send their commands and wait for specific responses. When those responses don't come, the software just sits forever and waits" I've added timeout values in on a few servers, and we'll see how we go over the next 24 hours. Chris On Fri, Aug 19, 2011 at 12:01 AM, Eric Shubert <[email protected]> wrote: > Is it spamdyke that's using the CPU, or another process? clamav had a > problem doing this sort of thing a couple versions back (0.95.x iirc). > > Other than that, I haven't heard of anything like this. I'd look at > processes related to queuing (scanners?) and see if there's a problem in > that area. Given your volume, I'd suspect that there's a resource > constraint that a little configuration tweaking might remedy. > > -- > -Eric 'shubes' > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users >
_______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
