I have a courier/postfix box with postfix using cyrus-sasl for smtp-auth...In trying to integrate and simplify the administration, I read that sasl2 can use authdeamond like courier does...However, I cannot get it to not look past or not read the berkeley sasl2 db /etc/sasldb2 no matter what i do....I recompiled the cyrus-sasl2 --with-authdaemond and made sure no distro pkg libraries were still being used as I deleted them and ln -s to the compiled libraries (CentOS 5). All the .so, .so.2,etc files are the new compile date.
I ran postfix/smtpd in verbose mode to make sure that it's finding the smtpd.conf as I read this as a problem in a previous post:
Code:
Mar 21 07:42:00 server1 postfix/smtpd[17238]: xsasl_cyrus_server_init: SASL config file is /usr/local/lib/sasl2/smtpd.conf
The smtpd.conf file contains:
Code:
log-level: 3
pwcheck_method: authdaemond
mech_list: PLAIN LOGIN
authdaemond_path:/usr/local/var/spool/authdaemon/socket
So, if I rename to /etc/sasldb2 to something else i get this even though it's finding the smtpd.conf:
Code:
Mar 21 07:53:28 server1 postfix/smtpd[17349]: warning: ip-66-235-250-53.sterlingnetwork.net[66.235.250.53]: SASL CRAM-MD5 authentication failed: authentication failure
Mar 21 07:53:28 server1 postfix/smtpd[17349]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory
Mar 21 07:53:28 server1 last message repeated 4 times
Mar 21 07:53:28 server1 postfix/smtpd[17349]: warning: SASL authentication failure: Password verification failed
Mar 21 07:53:28 server1 postfix/smtpd[17349]: warning: ip-66-235-250-53.sterlingnetwork.net[66.235.250.53]: SASL PLAIN authentication failed: authentication failure
Mar 21 07:53:30 server1 postfix/smtpd[17349]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory
Mar 21 07:53:30 server1 last message repeated 2 times
And if I put it back without a user added into the sasldb2, i get this:
Code:
Mar 21 07:51:20 server1 postfix/smtpd[17349]: warning: SASL authentication failure: no secret in database
Mar 21 07:51:20 server1 postfix/smtpd[17349]: warning: ip-66-235-250-53.sterlingnetwork.net[66.235.250.53]: SASL CRAM-MD5 authentication failed: authentication failure
Mar 21 07:51:20 server1 postfix/smtpd[17349]: warning: SASL authentication failure: Password verification failed
Mar 21 07:51:20 server1 postfix/smtpd[17349]: warning: ip-66-235-250-53.sterlingnetwork.net[66.235.250.53]: SASL PLAIN authentication failed: authentication failure
Mar 21 07:51:22 server1 postfix/smtpd[17349]: warning: SASL authentication failure: no secret in database
Mar 21 07:51:22 server1 postfix/smtpd[17349]: warning: ip-66-235-250-53.sterlingnetwork.net[66.235.250.53]: SASL CRAM-MD5 authentication failed: authentication failure
Mar 21 07:51:22 server1 postfix/smtpd[17349]: warning: SASL authentication failure: Password verification failed
Mar 21 07:51:22 server1 postfix/smtpd[17349]: warning: ip-66-235-250-53.sterlingnetwork.net[66.235.250.53]: SASL PLAIN authentication failed: authentication failure
Is there something I missed? I have for testing sake chmod'd 777 to the smtpd.conf file. I've verified the authdaemond socket location. Any help would be appreciated.
Thanks,
Chad
Dev Shed Forums Sponsor:
March 21st, 2008, 10:01 AM
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
