Actually, very soon now. I'm very close to releasing a new version that includes this fix and a bunch of others (but does not, sadly, include recipient validation). I have two more small changes to make and test, then I'll be ready to send out a beta version. I'd really like help testing this one, as the nonblocking I/O /may/ cause some other errors, though I believe I've got them handled.
-- Sam Clippinger On 6/7/10 8:08 PM, Eric Shubert wrote: > Hartmut Wernisch wrote: > >> On 22 Mar 10, Mirko Buffoni wrote: >> >>> At 13.10 19/03/2010 +0100, you wrote: >>> >>>> At 13.39 19/03/2010 +1100, you wrote: >>>> >>>>> On 19/03/2010 07:15, [email protected] wrote: >>>>> >>>>>> Started a new thread for this improved patch. This should fix the >>>>>> SSL_accept, SSL_shutdown and SSL_read issues. It temporarily sets the >>>>>> socket to non-blocking and timesout after the configured time. >>>>>> >>>>>> This is a replacement for the previous patch, apply to a clean >>>>>> spamdyke-4.0.10 code base. >>>>>> >>>> So far, with the new patch, no sign of hung or defunct processes has been >>>> noticed. >>>> I also shortened the default qmail timeoutsmtpd to 600 (10 minutes) >>>> Survived a good amount of spam in the 11:00-12:00 time range. >>>> Good sign. >>>> >>> After 3 days and several spam storms (that can be seen from collected >>> statistics) >>> no hanged up spamdyke process, nor defunct qmail-smtpd process have been >>> noticed. >>> IMO, I'd say your latest patch is stable enough to be included in the >>> official trunk >>> since it corrected a very annoying behavior. >>> >>> Thank you for your support, Trog. >>> >> yes me too. no more idle spamdyke processes or defunc qmail process >> since using this patch. >> >> best, >> Hartmut Wernisch >> > Sam, > Any guess as to when this patch will be rolled into the next version? > Many thanks. > > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
