|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re[2]: access lists and multiple values
From: Manuel Guesdon (ml
sbuilders.com)
Date: Thu Dec 21 2006 - 05:59:51 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 21 Dec 2006 11:59:38 +0100 Tony Earnshaw <tericssonearnshaw
barlaeus.nl> wrote:
>| ml
sbuilders.com skrev:
>|
>| > I'm fighting with access lists fo hours :-(
>| >
>| > I have a
>| > check_recipient_access = ldap:/etc/postfix/ldap/uid.cf
>| >
>| > with /etc/postfix/ldap/uid.cf:
>| > version = 3
>| > server_host = ...
>| > search_base = ...
>| > timeout = 150
>| > query_filter = (uid=%u)
>| > result_attribute = uid
>| > result_format = OK
>| > bind = yes
>| > bind_dn = ....
>| > bind_pw = ...
>| >
>| > but in some cases there's 2 uid for an entry so the lookup returns "OK, OK" and I get a server configuration error with <<warning: unknown smtpd restriction: "OK">>
>|
>| Put 'OK %u' in result_format, which is actually what you want: You have
>| to have a LHS and a RHS in a (anyway most) table lookups. Funnily enough
>| the LDAP table result_format result is a mirror image of a hash table
>| result, so the above order is correct.
Thank you very much: It works !! But I can't see why "OK uid1, OK uid2" is accepted and "OK, OK" is not :-(
BTW, I've found that result_attribute should be in lowercase (i.e. myAttribute will be never returned); probably because open ldap return lowercase attribute names. May be it should be added in ldap_table.5.html
Manuel
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]