SASL authentication failure: cannot connect to saslauthd server: No such file or directory

[QPMReinhard]

Ubuntu Linux 24.04.1
Virtualmin Version 7.20.2

I have read and tryed all the topics but have no luck. …

when connecting to the mailserver to send a mail The result is always
warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory

the status of the saslauthd.service seems OK with
: listening on socket: /var/spool/postfix/var/run/saslauthd/mux

the directory of /var/spool/postfix/var/run/saslauthd is
-rw------- 1 root root 0 Nov 5 15:16 cache.flock
-rw------- 1 root root 986112 Nov 5 15:16 cache.mmap
srwxrwxrwx 1 root root 0 Nov 5 15:16 mux
-rw------- 1 root root 0 Nov 5 15:16 mux.accept
-rw------- 1 root root 6 Nov 5 15:16 saslauthd.pid

is 0 byte for the “mux” ok `?

incoming mails are also ok.

The very funny thing is, it works yesterday al pretty well…

[shoulders]

@QPMReinhard

The very funny thing is, it works yesterday al pretty well…

Did your server reboot ? Did you change some SASL settings in Postfix and they were not applied until the server rebooted?

[QPMReinhard]

i’ve rebooted it in the morning … but why does the settings crash…
and “what kind of settings” ?
noting has changed

[shoulders]

Postfix and Cyrus SASL Authentication Server show green?

[QPMReinhard]

Jep, all running

[QPMReinhard]

a testsaslauthd brings these results.
testsaslauthd -u username -p password
connect() : No such file or directory

testsaslauthd -f /var/spool/postfix/var/run/saslauthd/mux -u username -p password
0: OK "Success.

???
looks like postfix doesnt use the right directory

[shoulders]

I am sure some else had this exact problem on the forum

[shoulders]

Have a look on this thread

Warning: SASL authentication failure: cannot connect to saslauthd server: Permission denied

do this ln -s /var/spool/postfix/var/run/saslauthd /var/run/saslauthd before you run this and see if that makes testsaslauthd happy

[QPMReinhard]

it does not… same result.
testsaslauthd -u username -p password
connect() : No such file or directory

testsaslauthd -f /var/spool/postfix/var/run/saslauthd/mux -u username -p password
0: OK "Success.

mail.log file says
warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory

[QPMReinhard]

i have changed the end of /etc/default/saslauthd to
START=yes
OPTIONS=“-c -m /var/run/saslauthd -r”
PARAMS=“-m /var/run/saslauthd -r”

this was
OPTIONS=“-c -m /var/spool/postfix/var/run/saslauthd -r”
PARAMS=“-m /var/spool/postfix/var/run/saslauthd -r”

and i don’t know how these lines have changed…
what else - it works .

[QPMReinhard]

But… the virtualmin server status is like this.

[shoulders]

So the Cyrus SASL service is running but is showing as inactive on the status widget in your image above?

[QPMReinhard]

after a reboot does not start again
after resetting the
OPTIONS=“-c -m /var/spool/postfix/var/run/saslauthd -r”

the service starts but mail.log says
cannot connect to saslauthd server: No such file or directory

doing a
ln /var/spool/postfix/var/run/saslauthd /var/run

then it works.

looks like /var/run is a tempfs so i had to create that link after reboot.

[Joe]

Why wouldn’t you start/enable it with systemctl?

The fact that your saslauthd configuration was broken means Virtualmin installation didn’t complete (in which case, your system probably has other problems), or you’ve uninstalled and reinstalled saslauthd (which you generally shouldn’t do).