I'm currently running into the same problem. And no I have only PAM enabled on this machine.
MECHANISMS="pam" The difference I have is that I enabled debugging output OPTIONS="-d -c -m /var/spool/postfix/var/run/saslauthd" due to debugging the recent postfix_2.10.0-1 FUBAR which prevented mail relaying (including sending mail from a MUAs like Thunderbird) and wich could only be fixed by dropping back to postfix_2.9.6-2 + for script in '$scripts' + /etc/rc2.d/S16saslauthd start [....] Starting SASL Authentication Daemon: saslauthdsaslauthd[1978] :main : num_procs : 5 saslauthd[1978] :main : mech_option: NULL saslauthd[1978] :main : run_path : /var/spool/postfix/var/run/saslauthd saslauthd[1978] :main : auth_mech : pam saslauthd[1978] :cache_alloc_mm : mmaped shared memory segment on file: /var/spool/postfix/var/run/saslauthd/cache.mmap saslauthd[1978] :cache_init : bucket size: 92 bytes saslauthd[1978] :cache_init : stats size : 36 bytes saslauthd[1978] :cache_init : timeout : 28800 seconds saslauthd[1978] :cache_init : cache table: 944764 total bytes saslauthd[1978] :cache_init : cache table: 1711 slots saslauthd[1978] :cache_init : cache table: 10266 buckets saslauthd[1978] :cache_init_lock : flock file opened at /var/spool/postfix/var/run/saslauthd/cache.flock saslauthd[1978] :ipc_init : using accept lock file: /var/spool/postfix/var/run/saslauthd/mux.accept saslauthd[1978] :detach_tty : master pid is: 0 saslauthd[1978] :ipc_init : listening on socket: /var/spool/postfix/var/run/saslauthd/mux saslauthd[1978] :main : using process model saslauthd[1978] :have_baby : forked child: 1979 saslauthd[1978] :have_baby : forked child: 1980 saslauthd[1978] :have_baby : forked child: 1981 saslauthd[1978] :have_baby : forked child: 1982 saslauthd[1978] :get_accept_lock : acquired accept lock Disable debugging and all is well: OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd" Cheers Mike
