On Mar 12, 2012, at 09.38, /dev/rob0 wrote:
On Mon, Mar 12, 2012 at 12:00:11AM -0400, btb@bitrate.net wrote:
the problem with this is that while each of the passdb/userdb configs for the various protocols does indeed work, if a result is not found in one of them, the global passdb appears to then function as a catch-all.
how can i tell dovecot it doesn't need a global passdb? each of the protocols' passdb/userdb configs is functioning as desired, but having dovecot look elsewhere upon failure ends up defeating the purpose.
A simple workaround: use an empty passwd-file passdb as global.
thanks, yeah. i've got what effectively accomplishes the same thing - a global ldap passdb within which the search filter always returns nothing. it sure seems like there would be a more logical method than this though. i looked briefly at the static password database, but at the moment it's intended application appears to be the opposite. if there were some argument such as deny=y or similar, it could be used. but ultimately, it would seem to make more sense to be able to simply tell dovecot that it doesn't need a global passdb, since obviously it doesn't.
-b