This is definitely a bug -- I can reproduce it when I use reject-missing-sender-mx, local-domains-file (or -entry) and recipient-whitelist-file (or -entry). It should happen any time a filter is triggered but spamdyke can't reject the connection without first seeing the recipient address (because the recipient address might be whitelisted somehow).
The timeout is occurring because spamdyke isn't closing the connection to qmail when "quit" is seen, then it waits for qmail to exit. Thankfully, the idle timeout is triggered before qmail closes on its own (20 minutes later). I'm finishing a new release right now, I'll include this fix too. Thanks for reporting this! -- Sam Clippinger On 1/31/11 1:13 PM, Ulrich C. Manns wrote: > I typed by hand: > > -> telnet www.msp-it.com <http://www.msp-it.com> 25 > <- 220 www.msp-it.com <http://www.msp-it.com> ESMTP > -> helo mail > <- 250 www.msp-it.com <http://www.msp-it.com> > -> mail from:ad@ak > <- 250 ok > -> rcpt to:bb@cc > <- 421 Refused. The domain of your sender address has no mail > exchanger (MX). > -> quit > <- 221 Refused. The domain of your sender address has no mail > exchanger (MX). > -> quit > <- 421 Timeout. Talk faster next time. > > Ok, the domains are not valid, but it seems that there is a bug in the > flow, becaue /quit/ won't work. > > Maybe that's the reason why i have many TIMEOUTS in the Version 4.1.0? > > Regards, > Ulrich > > > _______________________________________________ > 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
