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
I'm using the rDNS filters and an RBL filter, but I still have a delay. You can telnet mail.hwy39.net on 25. What am I doing differently? Ben log-level=2 tls-certificate-file=/var/qmail/control/servercert.pem local-domains-file=/var/qmail/control/rcpthosts max-recipients=5 idle-timeout-secs=60 rdns-whitelist-file=/home/vpopmail graylist-dir=/home/vpopmail/graylist.d graylist-min-secs=300 graylist-max-secs=1814400 sender-blacklist-file=/home/vpopmail/blacklist_senders reject-ip-in-cc-rdns reject-empty-rdns reject-unresolvable-rdns rdns-whitelist-file=/home/vpopmail/whitelist_rdns ip-whitelist-file=/home/vpopmail/whitelist_ip greeting-delay-secs=5 reject-missing-sender-mx check-dnsrbl=xbl.spamhaus.org _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
