Bug#516115: sasl2-bin: saslauthd should not read /etc/sasldb2

[Patrick Ben Koetter]

* Olaf <olaf at fortytwo.eu.org>:
> I get this message on the receiving server side (smtpd -v) when saying AUTH
> PLAIN [snip] on the smtp client:
> 
> 
> Feb 24 14:31:03 infomail postfix/smtpd[29613]: <
> nated-by-nat-gw.ham.bmcag.net[212.105.192.18]: auth plain [snip]
> Feb 24 14:31:03 infomail postfix/smtpd[29613]: xsasl_cyrus_server_first:
> sasl_method plain, init_response [snip]
> Feb 24 14:31:03 infomail postfix/smtpd[29613]: xsasl_cyrus_server_first:
> decoded initial response
> Feb 24 14:31:03 infomail postfix/smtpd[29613]: warning: SASL authentication
> problem: unable to open Berkeley db /etc/sasldb2: No such file or directory

This does not necessarily mean that saslauthd reads /etc/sasldb2 or tries to
do so.

The log message usually shows up if SASL can't find any configuration for an
authentication backend and falls back to its default authentication backend
"sasldb".

And then, if /etc/sasldb2 was not created for the sasldb backend, you get this
log message.

Very misleading, but that's the way it is.

I suggest you use "saslfinger -s" to create debug output from your
configuration and post it so we can check it.

p at rick

-- 
state of mind
Agentur für Kommunikation, Design und Softwareentwicklung

http://www.state-of-mind.de

Franziskanerstraße 15	   Telefon +49 89 45227227
81669 München              Telefax +49 89 45227226

Amtsgericht München        Partnerschaftsregister PR 563