--On October 26, 2011 4:45:01 PM -0700 Quanah Gibson-Mount
<qua...@zimbra.com> wrote:
I'm using simple binds as I have since postfix 2.3. I actually was not
aware the code for using SASL mechanism binds had been added to postfix.
Very happy to know that. ;) I have my own test server set up now so I
can better get the information you're asking for.
First, a normal postmap -q when the user exists and it has a working
password:
zimbra@zre-ldap002:~$ postmap -q testus...@zre-ldap002.eng.vmware.com
ldap:/opt/zimbra/conf/ldap-transport.cf
lmtp:zre-ldap002.eng.vmware.com:7025
Here is the ldap-transport.cf file:
root@zre-ldap002:/opt/zimbra/conf# cat ldap-transport.cf
server_host = ldap://zre-ldap002.eng.vmware.com:389
server_port = 389
search_base =
query_filter =
(&(|(zimbraMailDeliveryAddress=%s)(zimbraDomainName=%s))(zimbraMailStatus=enabled))
result_attribute = zimbraMailTransport
version = 3
start_tls = yes
tls_ca_cert_dir = /opt/zimbra/conf/ca
bind = yes
bind_dn = uid=zmpostfix,cn=appaccts,cn=zimbra
bind_pw = zimbra
timeout = 30
I will note that I build with -DUSE_LDAP_SASL and use OpenLDAP as the API.
It *looks* like this should use the old dict_ldap_bind_st function, but
since there is no logging in it or dict_ldap_bind_sasl specifically noting
which is used, I can't be 100% sure.
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
