Just wanted to followup regarding this -
Looks like there might be an issue with sender-blacklist-entry. We've got a
single address blocked at the moment and I removed it from our configuration
yesterday and we've not had any spamdyke processes get stuck since.
I've looked at the code and
I'd be very interested to know how this turns out. Two things bug me about
this solution: no matter what the timeout is, spamdyke should just sit quietly
and wait for more input (using select()); it shouldn't consume any CPU at all.
Also, when the idle timeout is zero and spamdyke disconnects
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.
We're seeing a lot of spamdyke processes on our servers getting stuck in
some sort of state where they'll hang, and use 100% CPU until we kill -9
them. Anyone else seeing this with 4.2.0?
From what it looks like, it occurs once spamdyke has done its job and Qmail
has accepted the message.
