I've considered that option in the past and just never gotten around to it. My reason for hesitating is that spamdyke should not disconnect too soon -- it should continue running long enough to gather information for its log messages. In this particular case, disconnecting immediately would fix the problem but resetting the idle timeout does the same thing. Perhaps the idle timeout should be set to a very low value instead of 20 minutes (after the qmail process exits)?
-- Sam Clippinger Felix Buenemann wrote: > Hi, > > On 06.10.2008 16:26 Uhr, Sam Clippinger wrote: > >> The problem is that remote servers (spambots) are not disconnecting >> after getting a rejection message. When spamdyke sends a rejection code >> and there's no chance the connection could be allowed (e.g. no >> whitelists remain to be matched), it disconnects qmail and allows the >> qmail process to exit. spamdyke then continues imitating an SMTP server >> for the remainder of the connection. However, because spamdyke 4.0 has >> no idle timeout by default, it's up to the remote server to disconnect. >> > > I think it'd be a great idea to have a configuration option for > spamdyke, that instantly drops the connection to the peer after it has > send a rejection code. > > -- Felix > > _______________________________________________ > 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
