Im a dovecot newbie and need a little help with the passwd-like file auth mechanism in dovecot I got dovecot to work fine with regular /etc/passwd file auth .. so I wanted to start using another authentication store for virtual users. So .. I created a /etc/dovecot-passdb file and plopped in an encrypted password using md5crypt. Here are the appropriate lines from the dovecot.conf file auth_userdb = passwd-file /etc/dovecot-passdb auth_passdb = pam and here is the /etc/pam.d/dovecot file #%PAM-1.0 auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required pam_stack.so service=system-auth So far .. no dice. Dovecot reports constant authentication failures. I fear that the dovecot-passdb file is wonky. Can anyone give me any pointers ?
On 9 Jan 2006, at 03:32, Brad wrote:> > auth_userdb = passwd-file /etc/dovecot-passdb > auth_passdb = pamI'm no expert, but that looks distinctly to me like you're saying "the usernames are stored in /etc/dovecot-passdb, but check their passwords somewhere else". Or it could be late & I'm wrong. Stroller
Brad wrote:> wanted to start using another authentication store for virtual users. > auth_passdb = pamWhy do you need pam for virtual users? Back in the old 0.99-days, I had this: auth_passdb = passwd-file /passwd auth_userdb = static uid=103 gid=104 home=/var/spool/vmail with passwd lines looking like "someuser:{HMAC-MD5}something". The "{HMAC-MD5}something" parts were generated with 'dovecotpw -s HMAC-MD5' (you need this for CRAM-MD5).