On 19/08/2010 16:16, Robert Fitzpatrick wrote:
The firewall at one of our locations is down and we are using a cheaper solution until it is replaced, which does not handle content filtering as well with calls to our db at another network like the old router did very well. So, I am trying to reroute all the mail destined for that Postfix gateway to another gateway on that other network. I commented out the transport_maps we use with ldap to determine destination for domains and content filtering, then setup relayhost. We do address verification for our own domains and would like to do that on the 1st gateway before it goes to the second. I found that if I do this, the second always gives deliverable status to unknown users because the 1st gateway is on a trusted network.
Address verification is always done (i think), even when the client is trusted. I solved a similar issue setting up a backend server with address verification disabled for smtpd: -o receive_override_options=no_unknown_recipient_checks -o smtpd_recipient_restrictions=permit_mynetworks,reject -o my_networks=192.168.22.254 -- Simone Caruso IT Consultant +39 349 65 90 805 p.iva: 03045250838
