>> My question, is this intended behaviour? Did anyone notice this >> behavious as well? > > Yes, this is documented intended behaviour. See, ldap_table(5): > > %[1-9] The patterns %1, %2, ... %9 are replaced by > the corresponding most significant component > of the input key's domain. If the input key > is u...@mail.example.com, then %1 is com, %2 > is example and %3 is mail. If the input key > is unqualified or does not have enough > domain components to satisfy all the speci- > fied patterns, the search is suppressed and > returns no results.
Hmm yeah, I read this part of the man page. To me "If the input key is u...@mail.example.com, then ..." sounded more like an example, explaining how the domain is broken up in pieces. Anyhow, thanks for the confirmation. Durk
