On 06/08/2011 06:50 AM, ron wrote: > I am having an issue with one of our clients sending us an email. Spamdyke > does very well with everyone else except this one domain and it blocks or > stops all mail from them. I have had to disable spamdyke because of this. > I have white listed the ip address, but it did not help. Can anyone give > me any other ideas on what to do or look for? I have included a portion > of the log and my spamdyke configuration file. > > Thanks in advance > Ron > > Information from smtp log: > > @400000004dee4249107d002c tcpserver: end 14525 status 0 > @400000004dee4249107d2b24 tcpserver: status: 0/100 > @400000004dee4249139753d4 tcpserver: status: 1/100 > @400000004dee42491397869c tcpserver: pid 14628 from 64.58.208.13 > @400000004dee424913979e0c tcpserver: ok 14628 > mail2.nsii.net:65.116.220.139:25 :64.58.208.13::64793 > @400000004dee424916766784 spamdyke[14628]: > DEBUG(filter_rdns_missing()@filter.c:897): checking for missing rDNS; > rdns: mail-out-01.healthways.com > @400000004dee424916769e34 spamdyke[14628]: > DEBUG(filter_ip_in_rdns_cc()@filter.c:928): checking for IP in rDNS > +country code; rdns: mail-out-01.healthways.com > @400000004dee42491676b5a4 spamdyke[14628]: > DEBUG(filter_rdns_whitelist_file()@filter.c:1005): searching rDNS > whitelist file(s); rdns: mail-out-01.healthways.com > @400000004dee42491676f424 spamdyke[14628]: > DEBUG(filter_rdns_blacklist_file()@filter.c:1108): searching rDNS > blacklist file(s); rdns: mail-out-01.healthways.com > @400000004dee42491677fdc4 spamdyke[14628]: > DEBUG(filter_ip_whitelist()@filter.c:1176): searching IP whitelist > file(s); ip: 64.58.208.13 > @400000004dee424916780d64 spamdyke[14628]: FILTER_WHITELIST_IP ip: > 64.58.208.13 file: /etc/spamdyke/whitelist_ip(2) > @400000004dee42c30e44ea7c spamdyke[14628]: TIMEOUT from: (unknown) to: > (unknown) origin_ip: 64.58.208.13 origin_rdns: > mail-out-01.healthways.com auth: (unknown) encryption: TLS reason: TIMEOUT > > My spamdyke configuration file: > > #dns-blacklist-entry=zombie.dnsbl.sorbs.net > #dns-blacklist-entry=dul.dnsbl.sorbs.net > #dns-blacklist-entry=bogons.cymru.com > dns-blacklist-entry=zen.spamhaus.org > dns-blacklist-entry=bl.spamcop.net > graylist-dir=/var/spamdyke/graylist > graylist-level=always > graylist-max-secs=2678400 > graylist-min-secs=180 > connection-timeout-secs=3600 > greeting-delay-secs=5 > idle-timeout-secs=120 > ip-blacklist-file=/etc/spamdyke/blacklist_ip > ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords > ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords > ip-whitelist-file=/etc/spamdyke/whitelist_ip > local-domains-file=/var/qmail/control/rcpthosts > log-level=debug > log-target=stderr > max-recipients=50 > #policy-url=http://my.policy.explanation.url/ > rdns-blacklist-file=/etc/spamdyke/blacklist_rdns > rdns-whitelist-file=/etc/spamdyke/whitelist_rdns > recipient-blacklist-file=/etc/spamdyke/blacklist_recipients > recipient-whitelist-file=/etc/spamdyke/whitelist_recipients > reject-empty-rdns > reject-ip-in-cc-rdns > reject-missing-sender-mx > reject-unresolvable-rdns > sender-blacklist-file=/etc/spamdyke/blacklist_senders > sender-whitelist-file=/etc/spamdyke/whitelist_senders > tls-certificate-file=/var/qmail/control/servercert.pem > tls-level=smtp
Sam will know better, but it looks to me as though there's something not quite right happening in the smtp session that results in spamdyke timing out. Please use the detailed logging option: full-log-dir=/var/log/spamdyke (you'll need to create that directory w/ appropriate permissions) to see where exactly the session is hanging. Post the log results here if the problem isn't immediately apparent. -- -Eric 'shubes' _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
