OK, then what? You said every connection was refused, but _how_ did that happen? Did spamdyke or qmail log any messages during that time? Did the remote clients receive a message from spamdyke or qmail?
Have you tried running spamdyke's "config-test" feature? Is there anything unusual or exotic about your server that might lend a clue (NFS filesystems, virtual machines, load balancers, etc)? -- Sam Clippinger [email protected] wrote: > I've now created /etc/tcp.smtp with: > 83.136.81.124:allow,RELAYCLIENT="" > > and added it to spamdyke.conf: > access-file=/etc/tcp.smtp > > >> -----Ursprungliche Nachricht----- >> Von: [email protected] >> [mailto:[email protected]] Im Auftrag von >> Sam Clippinger >> Gesendet: Mittwoch, 4. Februar 2009 17:05 >> An: spamdyke users >> Betreff: Re: [spamdyke-users] Frequently "553 sorry, that >> domain isn't in my list of allowed rcpthosts (#5.7.1)" >> >> >> That error message is generated by qmail, not by spamdyke. >> It's qmail's >> way of saying "relaying denied". >> >> Are you seeing these errors when the recipient's address is within a >> domain listed in rcpthosts? What does spamdyke log for those >> connections? Is the remote client authenticating? >> >> -- Sam Clippinger >> >> [email protected] wrote: >> >>> Hello, >>> >>> I'm using spamdyke 4.0.10 with plesk9 and getting frequently "553 >>> sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)" >>> errors in my maillog although my domains are listed in >>> /var/qmail/control/rcpthosts. >>> >>> The strange thing is, that this happens not every time, >>> >> only from time >> >>> to time - appx. 5 an hour, whith various domains. Spamdyke >>> >> is included >> >>> in smtp_psa before everything else. >>> >>> Here goes my spamdyke.conf: >>> log-level=verbose >>> #log-target=SYSLOG >>> #access-file=/var/qmail/access >>> local-domains-file=/var/qmail/control/rcpthosts >>> max-recipients=5 >>> idle-timeout-secs=300 >>> graylist-dir=/var/qmail/greylist >>> >> graylist-level=always-create-dir graylist-min-secs=300 >> graylist-max-secs=1814400 >> #policy-url=http://my.policy.explanation.url/ >> >>> sender-blacklist-file=/var/qmail/blacklist_senders >>> recipient-blacklist-file=/var/qmail/blacklist_recipients >>> ip-in-rdns-keyword-blacklist-file=/var/qmail/blacklist_keywords >>> ip-blacklist-file=/var/qmail/blacklist_ip >>> rdns-blacklist-dir=/var/qmail/blacklist_rdns.d >>> reject-empty-rdns >>> reject-unresolvable-rdns >>> #reject-ip-in-cc-rdns rdns-whitelist-file=/var/qmail/whitelist_rdns >>> ip-whitelist-file=/var/qmail/whitelist_ip >>> greeting-delay-secs=5 >>> dns-blacklist-entry=ix.dnsbl.manitu.net >>> dns-blacklist-entry=bl.spamcop.net >>> dns-blacklist-entry=cbl.abuseat.org >>> reject-missing-sender-mx >>> >> #tls-certificate-file=/var/qmail/control/servercert.pem >> >>> sender-whitelist-file=/var/qmail/whitelist_senders >>> >>> Any idea is welcome to fix this >>> >>> Best Regards, >>> >>> Boris >>> >>> _______________________________________________ >>> 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/spamd> yke-users >> >> > > _______________________________________________ > 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
