May you please clarify that? Where should I omit the userdb_ prefix? Which of my attempts are you pointing at? As stated, I omitted the userdb_ prefix when working with an LDAP attribute.
> On 7 Aug 2018, at 10:03, Aki Tuomi <aki.tu...@dovecot.fi> wrote:
>
> with ldap userdb, you need to omit the userdb_ prefix.
>
> Aki
>
>
> On 07.08.2018 10:54, Simeon Ott wrote:
>> Sorry for that! I was offline during writing my answer to your mail and so
>> it left my outbox after the advice from Sami.
>>
>> The solution works well when using passwd userdbs only. I didn’t get it
>> running in conjunction with ldap userdb. I tried to use an LDAP attribute
>> and mapping it to userdb_acl_globals_only and another try with
>> acl_globals_only. Both attributes were not considered by the lookup. Another
>> try was to use a separate passwd-userdb for this attribute only. When
>> placing the passwd-userdb before the ldap-userdb the ldap attributes are not
>> considered. If the ldap-userdb is placed before the passwd-userdb, the extra
>> attribute is not considered. I think this is a wanted behaviour.
>>
>> Any ideas in conjunction with LDAP?
>>
>>> On 7 Aug 2018, at 08:54, Aki Tuomi <aki.tu...@dovecot.fi> wrote:
>>>
>>> As Sami pointed out, I had wrong syntax:
>>>
>>>> close, but few typos. userdb should be:
>>>>
>>>> userdb {
>>>> driver = passwd-file
>>>> args = username_format=%Lu /etc/dovecot/share.passwd
>>>> }
>>>>
>>>> Sami
>
smime.p7s
Description: S/MIME cryptographic signature
