postmap appears to fold to lowercase by default for ldap queries: >postmap -vq '86:A5:5C:85:A3:98:2E:19:7A:54:57:99:76:9D:D5:A3:7E:46:85:C5' >ldap:./ccert_access-test.cf postmap: name_mask: ipv4 [...] postmap: dict_ldap_lookup: ./ccert_access-test.cf: Searching with filter (&(objectclass=mailserver)(memberof=cn=mail_relayers,ou=exo,ou=servers,ou=groups,dc=example,dc=net)(certfingerprint=86:a5:5c:85:a3:98:2e:19:7a:54:57:99:76:9d:d5:a3:7e:46:85:c5)) postmap: dict_ldap_get_values[1]: Search found 0 match(es) postmap: dict_ldap_get_values[1]: Search found 0 match(es) postmap: dict_ldap_get_values[1]: Leaving dict_ldap_get_values postmap: dict_ldap_lookup: Search returned nothing postmap: dict_ldap_close: Closed connection handle for LDAP source ./ccert_access-test.cf
is this intended? i see in postmap(1): as of Postfix 2.3 this case folding happens only with tables whose lookup keys are fixed-case strings such as btree:, dbm: or hash:. i wouldn't consider ldap to be in the same category as those three in that regard, and wasn't sure if that list was intended to be comprehensive, or just exemplary. i also looked in DATABASE_README and ldap_table(5) for further discussion, but didn't find any. thanks -ben
