From: Lukreme (kremelskreme.com)
Date: Mon Dec 01 2003 - 16:59:10 CST

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

On 01 Dec 2003, at 14:19, Norman Zhang wrote:
>> 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?

$ ls -ls /usr/local/etc/sas*
48 -rw-r--r-- 1 postfix mail 49152 Nov 21 03:18
/usr/local/etc/sasldb2.db

--
Try to realize it's all within yourself/No one else can make you change

• application/pkcs7-signature attachment: smime.p7s

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