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. If I don't trust the network, then I get verification in both places and the 1st gateway queue starts to back up.

Can address_verify_relayhost be setup to use ldap in some way? I get errors when trying to do just that. Because we use ldap to determine which domains are to be address verified. I tried to re-enable transport_maps, but that appears to be done before relayhost and the mail is then routed without content filtering. Can someone offer a solution to my temp issue?

Thanks, Robert

Reply via email to