Displaying 6 results from an estimated 6 matches for "maildn".
Did you mean:
maildb
2019 Jul 01
2
Variable expansion with variables containing '%' (ldap with 2.3.6)
...er.
seems to me the sequence of intepreting variables and modifiers changed
between 2.2 ans 2.3
now it gets the variable value from remote in the first place, and
interprets the value itself for more variables or modifiers, which
might not be what you want.
like in a subquery using
@mail=%{ldap:mailDN}
but I dont use subqueries. just a simple expansion
=myvar=%{ldap:mailDN}
any more ideas?
2019 Jul 02
1
Variable expansion with variables containing '%' (ldap with 2.3.6)
...hanged
>> between 2.2 ans 2.3
>> now it gets the variable value from remote in the first place, and
>> interprets the value itself for more variables or modifiers, which
>> might not be what you want.
>>
>> like in a subquery using
>>
>> @mail=%{ldap:mailDN}
>>
>> but I dont use subqueries. just a simple expansion
>>
>> =myvar=%{ldap:mailDN}
>>
>> any more ideas?
>>
>>
>>
>>
>>
> I have to investigate this a bit.
>
>
> Aki
>
Seems to be a bug of a kind. I'll open it...
2019 Jul 02
0
Variable expansion with variables containing '%' (ldap with 2.3.6)
...reting variables and modifiers changed
> between 2.2 ans 2.3
> now it gets the variable value from remote in the first place, and
> interprets the value itself for more variables or modifiers, which
> might not be what you want.
>
> like in a subquery using
>
> @mail=%{ldap:mailDN}
>
> but I dont use subqueries. just a simple expansion
>
> =myvar=%{ldap:mailDN}
>
> any more ideas?
>
>
>
>
>
I have to investigate this a bit.
Aki
2019 Jul 01
2
Variable expansion with variables containing '%' (ldap with 2.3.6)
Hi,
there seems to be a problem when expanding variables containing a
single '%' in value in dovecot V2.3.6
having a user defined Variable in user_attrs like
user_attrs = name=home=/maildir/%Ln,
=myvar=path/%L{ldap:sAMAccountName}
and sAMAccountName conains a '%', in my example "sonder%zeichen"
leads to:
2013 Mar 19
1
v2.2 status update
...inters to other entries that are
queried. (Support for LDAP URLs could probably also be added with little
trouble.) The configuration becomes a bit more complex again, but until
the whole LDAP configuration is redesigned this will work. Example:
user_attrs = \
=user=%{ldap:uid}, \
@mail=%{ldap:mailDN}, \
=uid=%{ldap:uidNumber at mail}, \
=gid=%{ldap:gidNumber at mail}, \
=home=%{ldap:rootPath at mail}/%d/%n
2018 Feb 06
2
LDAP userdb and dovecot LDA/LMTP - different requirements
...equirements solved in one userdb unit?
Or is it possible to have one userdb unit for LDA/LMTP, and another
one for IMAP and other Dovecot components?
I have also encountered entries getting the values from LDAP userdb
in the form as:
user_attrs = \
=user=%{ldap:uid}, \
@mail=base(%{ldap:mailDN}), \
=uid=%{ldap:uidNumber at mail}, \
=gid=%{ldap:gidNumber at mail}, \
=home=%{ldap:rootPath at mail}/%d/%n
or
user_attrs = \
=home=%{ldap:homeDirectory}, \
=uid=%{ldap:uidNumber},
=gid=%{ldap:gidNumber},
=quota_rule=*:bytes=%{ldap:quotaBytes},
=namespace/default/separa...