On 01/30/18 23:25 +0100, Michael Rüger wrote:
root@cyrus3:~ # ls -la /var/run/saslauthd/
total 13
drwxr-x--- 2 cyrus saslauth 5 Jan 30 21:40 .
drwxr-xr-x 6 root wheel 15 Jan 30 21:40 ..
srwxrwxrwx 1 root saslauth 0 Jan 30 21:40 mux
-rw------- 1 root saslauth 0 Jan 30 21:40 mux.accept
-rw------- 1 root saslauth 6 Jan 30 21:40 saslauthd.pid
On 01/30/2018 05:06 PM, Michael Rüger wrote:
I’m trying to set up imapd to use saslauthd for authentication.
I have already a running saslauthd which uses PAM. I can run this
root@cyrus3:/ # testsaslauthd -u mike -p mike
0: OK "Success.“
Michael,
A permissions issue with saslauthd is typically on the containing
directory. Try:
ls -ld /var/run/saslauthd
And adjust permissions or group membership. Try running testsaslauthd as
the cyrus user to verify permissions.
On 01/31/18 00:51 +0100, Michael Rüger wrote:
After enabling debug and restarting saslauthd and retrigger imtest, saslauthd gets no request.
root@cyrus3:/etc # /usr/local/etc/rc.d/saslauthd restart
Stopping saslauthd.
Waiting for PIDS: 88717.
Starting saslauthd.
saslauthd[90858] :main : num_procs : 5
saslauthd[90858] :main : mech_option: NULL
saslauthd[90858] :main : run_path : /var/run/saslauthd
saslauthd[90858] :main : auth_mech : pam
saslauthd[90858] :ipc_init : using accept lock file: /var/run/saslauthd/mux.accept
saslauthd[90858] :detach_tty : master pid is: 0
saslauthd[90858] :ipc_init : listening on socket: /var/run/saslauthd/mux
saslauthd[90858] :main : using process model
saslauthd[90858] :have_baby : forked child: 90859
saslauthd[90859] :get_accept_lock : acquired accept lock
saslauthd[90858] :have_baby : forked child: 90860
saslauthd[90858] :have_baby : forked child: 90861
saslauthd[90858] :have_baby : forked child: 90862
If not a permissions issue, then you may need to explicitly configured the
path to the mux in imapd.conf with:
sasl_saslauthd_path: /var/run/saslauthd/mux
But this is unlikely if testsaslauthd has knowledge of the correct mux
location.
--
Dan White
