From: Andreas Winkelmann (mlawinkelmann.de)
Date: Fri Nov 28 2003 - 07:02:46 CST

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

Am Freitag, 28. November 2003 13:40 schrieb Erwan Le Moing:

> in warnings log :
>
> warning: SASL authentication failure: cannot connect to saslauthd
> server: No such file or directory

> [rootmail root]# saslauthd -d -a pam
> saslauthd[2422] :main : num_procs : 5
> saslauthd[2422] :main : mech_option: NULL
> saslauthd[2422] :main : run_path : /var/lib/sasl2
> saslauthd[2422] :main : auth_mech : pam
> saslauthd[2422] :ipc_init : using accept lock file:
> /var/lib/sasl2/mux.accept
> saslauthd[2422] :detach_tty : master pid is: 0
> saslauthd[2422] :ipc_init : listening on socket: /var/lib/sasl2/mux
> saslauthd[2422] :main : using process model
> saslauthd[2422] :have_baby : forked child: 2423
> saslauthd[2422] :have_baby : forked child: 2424
> saslauthd[2422] :have_baby : forked child: 2425
> saslauthd[2422] :have_baby : forked child: 2426

Check your master.cf if chroot is turned off. Post the part.

--
        Andreas

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