From: Andreas Winkelmann (mlawinkelmann.de)
Date: Sun Oct 30 2005 - 14:09:42 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Am Sunday 30 October 2005 17:11 schrieb John Payne:

> All the troubleshooting I've seen says "make sure the authdaemon
> socket is in a directory that postfix has execute on.
>
> I've done that, and it fixed some of the errors, but now I'm getting:
>
> Oct 30 08:03:03 haybaler postfix/smtpd[19185]: warning: SASL
> authentication failure: Password verification failed
> Oct 30 08:03:03 haybaler postfix/smtpd[19185]: warning: doghome-
> gw.sackheads.org[136.248.127.51]: SASL PLAIN authentication failed
>
> when I'm testing PLAIN. Upping the peer_debug_level shows that the
> userid and password are correct.
>
> Postfix settings:
> $ postconf -n | grep -i smtpd_sasl
> smtpd_sasl_auth_enable = yes
> smtpd_sasl_local_domain =
>
> smtpd.conf:
>
> pwcheck_method: authdaemond
> log_level: 3
> mech_list: PLAIN LOGIN
> authdaemond_path: /usr/local/var/authdaemon/socket
>
> I'm not sure what log_level means as I can't figure out where it's
> logging to!

"log_level" in cyrus-sasl alone is senseless. It would only help, if the
Application which uses Cyrus-SASL handles it, and Postfix is not such an
Application. The Logging-Level in Postfix is controlled with -v, -vv or -vvv
as Start-Option of the Daemon. Or debug_peer_level/debug_peer_list of course.

> Any clues where to look next?

Look in the Log from authdaemond. If the Postfix-Log doesn't show Warnings
connecting authdaemond, you should check authdaemond and it's configuration.
If you use PAM, maybe you should look at the Servicename. It's not imap like
Courier (?), it is smtp now. So the PAM-Config-File changed.

--
        Andreas

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]