On 23.2.2011, at 0.38, Sven Hartge wrote:
and what does %$ mean?
It's the value of quotaBytes LDAP attribute. So the idea is that you have:
ldap-attribute-name=dovecot-setting-name=dovecot-setting-value
So, %$ ist always the value of the referenced attribute?
Yeah.
What if there are multiple values, by accident or by design?
Won't work right now.
From the above I read, I can not have the storage size _and_ the max number of message in two LDAP attributes, right? Because I cannot import two different attributes into the same dovecot-setting-name.
This would have to look like
user_attrs = homeDirectory=home,quotaBytes,quotaMessages=quota_rule=*:bytes=%$:messages=%$
which of course does not work (I think).
You'll get quotaBytes set to quotaBytes's value, which won' t do anything useful. %$ gets expanded to quotaMessages's value in both cases.
In some future version hopefully I'll make this simpler.
Yeah, the current "backward" notation is mighty confusing, at least for me.
I would have expected something like
user_attrs = home=homeDirectory,quota_rule=*:bytes=quotaBytes
or
user_attrs = home=homeDirectory,quota_rule=quotaRule
(if I have the complete quota_rule in an attribute instead of just the number)
I was planning on something like:
user_attrs { home = %{homeDirectory} quota_rule = *:bytes=%{quotaBytes} }
And of course you would be able to mix and match the %{whatever-ldap-value} attributes.