This problem isn't getting any clearer as we go on here, it's actually getting stranger.
Could you give more details about your attempt to add /etc/tcp.smtp -- what exactly did you do? Plesk doesn't use that file, so if spamdyke was refusing all connections afterwards, perhaps we can find the solution there and end up fixing your original problem. -- Sam Clippinger [email protected] wrote: > >> -----Ursprungliche Nachricht----- >> Von: [email protected] >> [mailto:[email protected]] Im Auftrag von >> Sam Clippinger >> Gesendet: Freitag, 6. Februar 2009 19:24 >> An: spamdyke users >> Betreff: Re: [spamdyke-users] Frequently "553 sorry, that >> domain isn't in my list of allowed rcpthosts (#5.7.1)" >> >> >> I'm not really sure what's happening here -- it looks like >> something is >> wrong with qmail. Maybe it's encountering some other error but >> returning this one instead? Is your server low on RAM? What's the >> system load look like? >> > > I doubt it is a qmail related problem, since before I used spamdyke I > used qgreylistrbl before which worked quite well for appx. 1-2 years. > > Ram-Load is always about 80% on total ram - without swap. > CPU looks fine and is low as 20-40% > > >> One possible fix might be to configure spamdyke to control relaying >> instead of allowing qmail to do it. That way, if there is a problem >> with your configuration, spamdyke might log something >> helpful. To get >> spamdyke to control relaying, add the "access-file" option >> (you may need >> to create a proper tcp.smtp file for this). >> > > I've already tried to add an access-file with ':allow' in it (found here > in maillinglist archive). > As result every connection was refused. > > >> -- Sam Clippinger >> >> [email protected] wrote: >> >>> Hello Sam, >>> >>> Here goes a debug output of /usr/local/psa/var/log/maillog: Feb 4 >>> 15:18:09 main8 spamdyke[26436]: FILTER_OTHER: response: "553 sorry, >>> that domain isn't in my list of allowed rcpthosts (#5.7.1)" Feb 4 >>> 15:18:09 main8 spamdyke[26436]: DENIED_OTHER from: >>> >> [email protected] >> >>> to: [email protected] origin_ip: 217.235.128.112 >>> origin_rdns: pd9eb8070.dip0.t-ipconnect.de auth: (unknown) Both >>> domains are listed in /var/qmail/control/rcpthosts >>> >>> The users use smtp-authentication with their mailaddresses and same >>> setttings/password like pop3. >>> >>> Regards, >>> >>> Boris >>> >>> >>> >>>> -----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/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
