OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: Wits end wt "Could not open db"

From: Andreas Winkelmann (mlawinkelmann.de)
Date: Sun Jan 14 2007 - 05:56:17 CST


On Sunday 14 January 2007 09:47, Christopher H. Laco wrote:

> It's late. I'm cranky, and completely missing something obvious.
> I'm trying to merge an existing postfix 2/sasl1/cyrus server to another
> server. The new server is running the latest postfix, sasl2, and cyrus.
>
> IMAP/Cyrus w/sasl2 auth is working just dandy, and postfix local
> delivery is working just fine going from postfix->amavisd->cyrus.
>
> But try as I might, I can't get sasl auth working in postfix without
>
> getting the ever painfull:
> > Jan 14 03:30:02 cypher postfix/smtpd[19172]: warning: SASL authentication
> > failure: Could not open db Jan 14 03:30:02 cypher postfix/smtpd[19172]:
> > warning: SASL authentication failure: Could not open db Jan 14 03:30:02
> > cypher postfix/smtpd[19172]: warning: SASL authentication failure: no
> > secret in database
>
> I have debugging level 5 on, and of course, it doesn't tell me what file
> it's really going after. I've trying taking smtpd out of chroot. I've
> try symlink the /usr/local/etc/sasldb2.db to the usual /etc names, and
> I've tried various forms of pwcheck_method: sasldb, sasldb2, auxprop.

pwcheck_method: auxprop
auxprop_plugin: sasldb

nothing else.

hmm, a way to find out the path to sasldb2 would be:

# strings /usr/lib/sasl2/libsasldb.so | grep sasldb2

Check for chroot in Postfix's master.cf. Show the Line(s). Only a "n"
means "no", "y" and "-" means "yes".

> Nothing works. Yes, /usr/local/etc/sasldb2.db has read permissions for
> the mail group, which has postfix in it.
>
> What am I missing here?

--
        Andreas