On 11/17/2013 5:38 AM, Adam Pribyl wrote: > Hello, > > we were using postfix as mail server directly delivering email from > and to company without issues. Now we had to change the ISP and the > new one forces us to use his relay as "The next-hop destination of > non-local mail" - this means I only added a directive "relayhost" to > our setup.
... and you changed your ISP, which is likely the real problem. When your DNS server lies to you, reject_unknown_recipient domain can't work correctly. Some ISP's send fake DNS responses for non-existent domains as a helpful service for web-browser clients. The usual suggestion is to run your own DNS server, but some ISP's also redirect that traffic. If you can't turn off this unhelpful feature, you can use check_recipient_mx_access to reject mail that resolves to the ISP-supplied wildcard address. http://www.postfix.org/postconf.5.html#check_recipient_mx_access Also talk to your ISP about allowing outbound port 25 directly from your mail server. Most ISP's have a procedure to whitelist known mail servers on business-class accounts. -- Noel Jones > > With relayhost setup, when local user sends email to non-existant > domain, it just passes the email to relayhost even thou there is > smtpd_recipient_restrictions = reject_unknown_recipient_domain > > When I disable the relayhost, then postfix rejects the emails to > non-existant domain correctly. From a postfix doc it seems the > relayhost > "overrides non-local domains in recipient addresses." It looks to > me, like it overrides it and then reject_unknown_recipient_domain > could never apply anymore. > > Do I understand this correctly? Is it possible to apply > reject_unknown_recipient_domain even when using realyhost? > > Thanks > > Adam Pribyl
