Bug 734088

Summary: postfix unable to open Berkeley db /etc/sasldb2: Invalid argument
Product: [Fedora] Fedora Reporter: Artur <arus>
Component: postfixAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: jskarvad, mlichvar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-29 12:41:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Artur 2011-08-29 12:34:02 UTC 
Description of problem:

Users are unable to authenticate to smtp service. Postfix (smtpd) is uanble to access sasldb2 database via sasl library.

Version-Release number of selected component (if applicable): postfix-2.8.4-1.fc15

How reproducible: install postfix, configure it to use sasl authentication, configure sasl library for application smtpd to use pwcheck_method auxprop with plugin sasldb (the default), give postfix (smtpd) read access to /etc/sasldb2

Steps to Reproduce:
1. configure postfix to allow smtp access from network
2. configure smtpd to use sasl authentication
3. configure email client to use this instalation for sending mail via SMTP with smtp authentication turned on

Actual results:
(in maillog):
postfix/smtpd[27873]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: Invalid argument

Expected results:
(in maillog):
postfix/smtpd[8609]: 003A520047: client=unknown[x.x.x.x], sasl_method=LOGIN, sasl_username=username


Additional info:

This happens because postfix executables are are linked with db4-4.8 instead of libdb-5.1, and /usr/lib64/sasl2/libsasldb.so.2.0.23 (package cyrus-sasl-lib-2.1.23-18.fc15) is linked with libdb-5.1
Comment 1 Artur 2011-08-29 12:41:51 UTC 

*** This bug has been marked as a duplicate of bug 734084 ***