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.
-- Sam Clippinger Davide Bozzelli wrote: > Davide Bozzelli ha scritto: >> First config: >> --------------- >> >> log-level=2 >> log-target=0 >> >> ip-whitelist-file=/var/qmail/control/nospamdykeip >> sender-whitelist-file=/var/qmail/control/nospamdykefrom >> tls-certificate-file=/var/qmail/control/servercert.pem >> recipient-whitelist-file=/var/qmail/control/nospamdyketo >> local-domains-file=/var/qmail/control/rcpthosts >> ip-in-rdns-keyword-file=/var/qmail/control/badrdns >> never-graylist-ip-file=/var/qmail/control/nograyip >> >> reject-missing-sender-mx >> reject-empty-rdns >> reject-unresolvable-rdns >> #reject-ip-in-cc-rdns >> #check-rhsbl=blackhole.securitysage.com >> #check-dnsrbl=zen.spamhaus.org >> >> greeting-delay-secs=30 >> >> ----- END SNIP ----------------- >> >> Result: The delay is enforced. >> >> > As side note i've noticed that the delay is in act but if a try to type > something spamdyke does not block me . > > Have fun, > Davide > _______________________________________________ > 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
