Master user without pass=yes error

Thomas HUMMEL
Tue, 03 Feb 2015 10:23:22 -0000

On Mon, Feb 02, 2015 at 05:55:26PM +0100, Thomas HUMMEL
wrote:
> Hello Timo,

Hello again. I'll try to answer my own question myself ;-)

I think my problem was that "pass=yes" just becomes _mandatory_ when
using
_only one_ and _prefetched_ userdb because retrieving the normal user userdb
attributes then becomes a "side effect" of the "pass=yes"
behavior :

My understanding now is that, even with master user :

  . a userdb still has to be done for the normal user and
  . since my (ldap) userdb is (ldap) passdb-prefetched (and the only userdb),
    it can only be searched if somehow an (ldap) passdb search is performed

  -> with pass=no, dovecot does not try to check the existence of the normal
     user in the normal (ldap) passdb : so the normal user userdb attributes are
     never retrieved (because of the prefetch nature of this userdb)

  -> with pass=yes, dovecot performs an (ldap) passdb lookup to check the
     existence of the user and prefetches the normal user userdb attributes
(side
    effect), allowing the master user to retrieve the normal user mailbox.

Am I correct ?

Thanks