Hi,
thanks for the answer.
Do I understand you right that currently it's not possible to manage
both system users and virtual users in a dovecot 2 and lmtp setup?
You were talking about "adding a generic passdb/userdb {
auth_username_format } setting". Are there any plans to do so?
What are your recommendations about migrating from dovecot 1.2.15 to
dovecot 2 regarding system and virtual users? Should I use LDA instead
of LMTP then?
Thank you very much,
David
Timo Sirainen schrieb am 31.03.2013 10:53:
> On 22.3.2013, at 11.53, David Obando <da...@cryptix.de> wrote:
>
>> Timo Sirainen schrieb am 22.03.2013 09:48:
>>> Maybe. Depends on your Dovecot version and passdb/userdb
>>> configuration. So, doveconf -n output?
>> I use version 2.1.7 from the backports repo on Debian Squeeze.
>>
>> passdb {
>> args = /etc/dovecot/dovecot-sql.conf.ext
>> driver = sql
>> }
>> passdb {
>> driver = pam
>> }
> Nope, you can't currently do "user@domain" auth for sql and "user" for PAM.
> You could try using passdb checkpassword instead though, which allows you to
> script it any way you want.
>
>> userdb {
>> args = /etc/dovecot/dovecot-sql.conf.ext
>> driver = sql
>> }
>> userdb {
>> driver = passwd
>> }
> Also userdb passwd can't do that.
>
> I've thought of adding a generic passdb/userdb { auth_username_format }
> setting, but that doesn't exist yet. Would be easy to do though..
>
--
The day microsoft makes something that doesn't suck is the day they start
making vacuum cleaners.
gpg --keyserver pgp.mit.edu --recv-keys 1920BD87
Key fingerprint = 3326 32CE 888B DFF1 DED3 B8D2 105F 29CB 1920 BD87
