[Postfixbuch-users] LDAP Map Query Problem
Martin Ott
martin.ott at itk-engineering.de
Sa Jun 26 11:28:21 CEST 2010
Hallo Alexander,
> # /etc/postfix/ldap-all_map.cf
> #
> # lookup for the dynamic all dispatcher alias
>
> server_host = zcp.example.com
> server_port = 389
> version = 3
> bind = no
> search_base = ou=Aliases,dc=example,dc=com
> scope = one
> query_filter = (mail=%s)
> special_result_attribute = memberURL
> result_attribute = mail
>
>
...
> Wo kommt dieses Resultat her - feature by design? Und besser noch, wie
> verhindere ich dies?
>
Dass bei der Abfrage mit key=all at example.com als value u.a. wieder
all at example.com zurückkommt liegt an result_attribute = mail. Um das
abzustellen kannst du versuchen "result_attribute =" und
"leaf_result_attribute = mail" zu setzen.
http://www.postfix.org/ldap_table.5.html
*leaf_result_attribute (default: empty)*
When one or more special result attributes are
found in a non-terminal (see above) LDAP entry,
leaf result attributes are excluded from the expan-
sion of that entry. This is useful when expanding
groups and the desired mail address attribute(s) of
the member objects obtained via DN or URI recursion
are also present in the group object. To only
return the attribute values from the leaf objects
and not the containing group, add the attribute to
the leaf_result_attribute list, and not the
result_attribute list, which is always expanded.
Note, the default value of "result_attribute" is
not empty, you may want to set it explicitly empty
when using "leaf_result_attribute" to expand the
group to a list of member DN addresses.
Gruß,
Martin
-------------- nächster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <https://listi.jpberlin.de/pipermail/postfixbuch-users/attachments/20100626/62b0d22e/attachment.html>
Mehr Informationen über die Mailingliste Postfixbuch-users