I can't reproduce this with version 3.1.5. One thought: is it possible you're seeing no delay because the connection matched one of the three filters you're disabling? For example, if the remote server were listed on the zen.spamhaus.org DNS RBL, spamdyke would not delay the greeting banner. This is by design -- it's better to send the rejection and close the connection and free your server's resources as fast as possible. Otherwise, high spam traffic could quickly become a DoS attack.
If that explanation doesn't fit, could you send more details about the connections that aren't delayed? A full log would be perfect. -- Sam Clippinger Davide Bozzelli wrote: > Sam Clippinger ha scritto: >> If you're right about this, it's a bug. I'll work on reproducing it. >> >> As for the blocking, the delay is supposed to end as soon as the first >> characters are sent. This is by design -- if the remote server isn't >> going to follow the SMTP protocol, there's no point to making them wait >> (and consume server resources). In your case, you won't see an error >> message until after the recipient is specified because spamdyke has to >> check the recipient whitelist file before it rejects the message. >> >> > > I can confirm you, the bug goes up when the following options are enabled: > > reject-ip-in-cc-rdns > check-rhsbl=blackhole.securitysage.com > check-dnsrbl=zen.spamhaus.org > > > The issue affect the sparc manchine where you had logged in, and other one. > > Have fun, > Davide > _______________________________________________ > spamdyke-users mailing list > spamdyke-users@spamdyke.org > http://www.spamdyke.org/mailman/listinfo/spamdyke-users _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
