On Wed, 2007-03-14 at 11:38 -0700, Troy Engel wrote:
Timo Sirainen wrote:
I accidentally added it to passdb instead of to userdb. It doesn't at least currently work in passdb passwd (although it could, but does anyone use it anyway?)
OK thanks for that, but I'm still a bit confused -- I'm after the second part of the wiki entry in relation to nss_ldap; I was thinking to set blocking=yes to just avoid any possible problems in the future with PAM/nss_ldap.
A) Does blocking=yes still apply to passdb pam {}?
Yes, http://wiki.dovecot.org/PasswordDatabase/PAM explains what it does and why it might not be a good idea. Although no-one has yet reported any success/failure stories, those are all my own guesses..
B) Do I still add blocking=yes to userdb passwd {} if I'm using passdb pam {} as above?
You probably don't have to, but doing so might give you better performance.
Is there no such block as 'userdb pam {}' since I don't see one in dovecot-example.conf?
No. PAM can't be asked any userdb info (home dirs etc.)