dovecot - Mar 2012 - ldap userdb warning in v2.1.1

Hi,

I've upgraded from 2.0.13 to 2.1.1 and when I started the service, I got 
the following warning:

Mar 21 10:07:23 imapserver dovecot: master: Dovecot v2.1.1 starting up 
(core dumps disabled)
Mar 21 10:08:17 imapserverdovecot: auth: Warning: ldap: Ignoring changed 
user_attrs in /etc/dovecot/dovecot-passdb-ldap.conf, because userdb ldap 
not used. (If this is intentional, set userdb_warning_disable=yes)

I didn't see such warnings in 2.0.13.

I guess I should/could remove the "user_attrs" line from 
dovecot-passdb-ldap.conf because it's not needed? (I could also set 
"userdb_warning_disable=yes" as advised, but I'm trying to figure
out
what's the real cause of the warning.)

The config follows below.

Thanks,
Nick

============================================================protocols = imap
pop3

mail_location = maildir:~/Maildir/
mail_gid = 502
mail_uid = 502

auth_mechanisms = plain login
auth_username_format = %Lu
auth_verbose = yes
disable_plaintext_auth = no

mail_plugins = quota

protocol imap {
   imap_client_workarounds = "delay-newmail  "
   mail_plugins = quota imap_quota
}

protocol pop3 {
   mail_max_userip_connections = 3
   mail_plugins = quota
   pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
   pop3_uidl_format = %08Xu%08Xv
}

protocol lda {
   auth_socket_path = /var/run/dovecot/auth-master
   info_log_path    log_path    mail_plugins = quota
   postmaster_address = sysadmin at example.com
   sendmail_path = /usr/lib/sendmail
}

userdb {
   args = /etc/dovecot/dovecot-usrdb-ldap.conf
   driver = ldap
}

passdb {
   args = /etc/dovecot/dovecot-passdb-ldap.conf
   driver = ldap
}

plugin {
   quota = maildir:User quota
   quota_rule = *:storage=4G
   quota_rule2 = Trash:storage=+3%%
   quota_warning = storage=75%% quota-warning 75 %u
   quota_warning2 = storage=90%% quota-warning 90 %u
}

service quota-warning {
   executable = script /opt/mail1.sh
   user = vmail
   unix_listener quota-warning {
     user = vmail
   }
}

service auth {
   unix_listener /var/spool/postfix/private/auth {
     group = postfix
     mode = 0660
     user = postfix
   }
   unix_listener auth-master {
     group = vmail
     mode = 0660
     user = vmail
   }
   user = root
}

service imap-login {
   service_count = 1
   vsz_limit = 64 M
}

service pop3-login {
   service_count = 1
   vsz_limit = 64 M
}

ssl_ca = </etc/pki/tls/certs/chain-650.pem
ssl_cert = </etc/pki/tls/certs/cert-650.pem
ssl_key = </etc/pki/tls/private/key-650.pem

syslog_facility = local1
============================================================
and dovecot-usrdb-ldap.conf is identical to dovecot-passdb-ldap.conf:

============================================================hosts = localhost
tls = no
base = ou=people, dc=example, dc=com
scope = onelevel
ldap_version = 3
dn = uid=authenticate,ou=System,dc=example,dc=com
dnpass = secret
auth_bind = yes
user_filter = (uid=%u)
pass_filter = (uid=%u)
pass_attrs = uid=user,userPassword=password
auth_bind_userdn = uid=%u,ou=people,dc=example,dc=com
user_attrs = roomNumber=quota_rule=*:bytes=%$,uid=home=/home/vmail/%u
iterate_filter = (objectClass=*)
=============================================================

On 21.3.2012, at 11.00, Nikolaos Milas wrote:
> Mar 21 10:07:23 imapserver dovecot: master: Dovecot v2.1.1 starting up
(core dumps disabled)
> Mar 21 10:08:17 imapserverdovecot: auth: Warning: ldap: Ignoring changed
user_attrs in /etc/dovecot/dovecot-passdb-ldap.conf, because userdb ldap not
used. (If this is intentional, set userdb_warning_disable=yes)
> 
> I didn't see such warnings in 2.0.13.
> 
> I guess I should/could remove the "user_attrs" line from
dovecot-passdb-ldap.conf because it's not needed?
Hmm. Yes, if dovecot-usrdb-ldap.conf is a separate file from
dovecot-passdb-ldap.conf you can just remove it. But this reminds me that in
several places I've suggested to make one of them a symlink to the other,
and you can't really do it then. Perhaps I'll need to remove this
warning, or maybe make it recognize the symlink case.

Anyway I added it for both LDAP and SQL hoping that it would reduce questions
like: "I changed user_attrs, but it doesn't do anything!"