postfix/smtpd[29658]: warning: SASL authentication problem: unable to open Berkeley d
source: http://www.kloopy.com/344_Postfix__SASL2__unable_to_open_Berkeley_db
postfix/smtpd[29658]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory
postfix/smtpd[29658]: warning: SASL authentication failure: Password verification failed
postfix/smtpd[29658]: warning: localhost[127.0.0.1]: SASL LOGIN authentication failed
The reason that it can't find /etc/sasldb2 even though you've created it (hopefully) using saslpasswd2 is that saslauthd chroots (by default) to /var/spool/postfix for security. Thus, despite the authentication daemon thinking it's checking /etc/sasldb2 and this is where the saslpasswd2 creates the database, it's not there. Simply copy /etc/sasldb2 to /var/spool/postfix/etc/sasldb2 and the problem will be fixed.
postfix/smtpd[29658]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory
postfix/smtpd[29658]: warning: SASL authentication failure: Password verification failed
postfix/smtpd[29658]: warning: localhost[127.0.0.1]: SASL LOGIN authentication failed
The reason that it can't find /etc/sasldb2 even though you've created it (hopefully) using saslpasswd2 is that saslauthd chroots (by default) to /var/spool/postfix for security. Thus, despite the authentication daemon thinking it's checking /etc/sasldb2 and this is where the saslpasswd2 creates the database, it's not there. Simply copy /etc/sasldb2 to /var/spool/postfix/etc/sasldb2 and the problem will be fixed.
Comments
Post a Comment