On Sun, Aug 23, 2009 at 03:55:43PM -0700, Daniel Corbe wrote:
> acceptdomains_server_host = localhost
> acceptdomains_server_port = 389
> acceptdomains_bind = yes
> acceptdomains_bind_dn = cn=Manager,dc=corbe,dc=net
> acceptdomains_bind_pw = xx55ZZ
> acceptdomains_search_base = dc=corbe,dc=net
> a
Issues with the depreciated config aside I figured out what the issue was.
Burried deep inside the ldap_table(5) man page was my answer: for whatever
reason postfix defaults to LDAPv2 instead of LDAPv3. The configuration
examples with the newer versions of OpenLDAP try to gently discourage use
On 8/24/2009, Brian Evans - Postfix List (grkni...@scent-team.com) wrote:
> You are using the depreciated form of an LDAP lookup.
Pet-peeve:
The word is 'deprecated', not 'depreciated'...
--
Best regards,
Charles
Daniel Corbe wrote:
> Hi,
>
> I'm seeing the following errors in my syslog being generated by
> trivial-rewrite after a MAIL FROM: command hits my MTA. I've been trying to
> enable LDAP lookups for my mail system without much success. The error
> messages aren't very helpful (even with verbose
Hi,
I did some digging around and I didn't get much further:
# postmap -q corbe.net ldap:acceptdomains
postmap: warning: dict_ldap_lookup: Search error 50: Insufficient access
It's almost as if postfix is simply ignoring the fact that I've asked it to
bind a specific DN and is trying to bind an
Hi,
I'm seeing the following errors in my syslog being generated by trivial-rewrite
after a MAIL FROM: command hits my MTA. I've been trying to enable LDAP
lookups for my mail system without much success. The error messages aren't
very helpful (even with verbose logging turned on for the triv
