Displaying 1 result from an estimated 1 matches for "domain_3".
Did you mean:
domain3
2006 Jan 11
0
special variables
...---BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
Are there any plans to extend the special variables you can use for ldap
query strings (%u,%n,etc)? For instance, say you have an ldap schema
like this with multiple domains in a single top-level-domain:
dc=domain_1,dc=tld_1
dc=domain_2,dc=tld_1
dc=domain_3,dc=tld_1
dc=domain_4,dc=tld_2
dc=domain_5,dc=tld_2
dc=domain_6,dc=tld_2
Now dovecot (latest CVS snapshot) offers, among others, the following
variable:
%d - domain part in user at domain, empty if there is no domain
But, what if dovecot could offer something like this:
%1-9 = domain tokens (%1...