From: Norman Zhang (nzhangarkon-group.com)
Date: Mon Dec 01 2003 - 15:19:53 CST

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

> I don't currently have SASL enabled in postfix because:
>
> % sasldblistusers2
> can't getkeyhandle
> listusers failed
>
> # tail /var/log/auth.log
> Dec 1 13:54:05 saslauthd[95246]: server_exit : master exited:
> 95246 Dec 1 13:54:39 saslauthd[16059]: detach_tty : master pid
> is: 16059 Dec 1 13:54:39 saslauthd[16059]: ipc_init :
> listening on socket: /var/state/saslauthd/mux
> Dec 1 13:54:43 sasldblistusers2: Could not open db
>
> and, when I still had it enabled, i was getting:
>
> postfix/smtpd[81549]: warning: x.client.comcast.net[24.9.x.x]: SASL
> CRAM-MD5 authentication failed
> postfix/smtpd[81549]: warning: SASL authentication failure: Could not
> open db
> postfix/smtpd[81549]: warning: SASL authentication failure: Could not
> open db
> postfix/smtpd[81549]: warning: SASL authentication failure: no secret
> in database

Sounds like a permission problem. Did you try giving postfix rw access to
sasl.db?

Regards,
Norman

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