postfix dbmail and cyrus-sasl

[Alexander Dalloz]

Am Mi, den 07.09.2005 schrieb Alan Glait um 18:44:

> Im trying to enable smtp auth in postfix+dbmail
> now I have:
> /usr/local/lib/sasl2/smtpd.conf
> pwcheck_method: saslauthd
> saslauthd_path: /var/run/saslauthd/mux
> mech_list: CRAM-MD5 DIGEST-MD5

That unfortunately does not tell us how "saslauthd" is configured, means
which method it uses to provide MD5 mechs. Is saslauthd compiled to
provide sasldb (saslauthd -v)?

> and I get in maillog
> 
> < unknown[192.168.1.5]: AUTH CRAM-MD5
> smtpd_sasl_authenticate: sasl_method CRAM-MD5
> smtpd_sasl_authenticate: uncoded challenge: <3886930606.2037449@>
>  > unknown[192.168.1.5]: 334 
> PDM4ODY5MzA2MDYuMjAzNzQ0OUBteDIucmVuYXRyZS5vcmcuYXI+
> < unknown[192.168.1.5]: YWdsYWl0IDA4ZWJlYTZjMzdlZjE3NTRkMTg5ZTExZjhmMGJjMzdk
> smtpd_sasl_authenticate: decoded response: user 
> 08ebea6c37ef1754d189e11f8f0bc37d
> warning: SASL authentication failure: Could not open db
> warning: SASL authentication failure: Could not open db
> warning: SASL authentication failure: no secret in database
> warning: unknown[192.168.1.5]: SASL CRAM-MD5 authentication failed

SASL tries to read from sasldb2 - and fails. That can be either because
of wrong permissions or it missing.

> ....
> probing ... I test
> bash-2.05b# testsaslauthd -s smtp -u aglait -p pass
> 0: OK "Success."
> 
> so ... I think that I have a bad configuration ....
> 
> can you help me ??

saslfinger may help.

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773
legal statement: http://www.uni-x.org/legal.html
Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp 
Serendipity 19:47:35 up 16 days, 16:31, load average: 0.23, 0.27, 0.27