On Tue, 2008-10-21 at 20:36 +0200, mouss wrote: > Robert Fitzpatrick a écrit : > > On Tue, 2008-10-21 at 12:34 -0400, Brian Evans - Postfix List wrote: > >> The current best use view of reject_unverified_(recipient|sender) is > >> to > >> use for your domains that you control. > > > > Thanks, and yes, I agree this should be done. We currently use LDAP > > lookups for transports. Is there a way to tie > > reject_unverified_(recipient|sender) to domains using LDAP lookups? > > If it's LDAP, then use reject_unlisted_recipient. simply configure the > list of valid users in the various mumble_recipient_maps and you're done. > > note that recipient validation is done by default, so this is not > necessary. but you can use it explictely to reject a transaction before > doing expensive checks (reject_rbl_*...) > > > [snip]
Thanks, but we don't use LDAP for storing addresses, only transport maps. I need to do address verification only to our transports, we're now using verification for all. So, I'm looking for a way to hopefully use our entries for transport maps to determine which domains to do address verification. Right now, our transport maps are determined as follows... esmtp# cat postfix/ldap/transport.cf bind = no server_host = ldapi:/// version = 3 search_base = ou=Domains,dc=example,dc=net query_filter = (dc=%s) result_attribute = mailRoutingAddress result_format = smtp:[%s] esmtp# ldapsearch -LLL "(dc=example.com)" mailRoutingAddress dn: dc=example.com,ou=domains,dc=example,dc=net mailRoutingAddress: 1.2.3.4 esmtp# postmap -q example.com ldap:/usr/local/etc/postfix/ldap/transport.cf smtp:[1.2.3.4] -- Robert
