When my saslauthd is started its run with the -m /var/run/saslauthd. Here is
the output of `lsof -nU | grep saslauthd':
saslauthd 5630 root 3u unix 0xf6389400 86047552 socket
saslauthd 5630 root 5u unix 0xf26f8100 86047553
/var/run/saslauthd/mux
saslauthd 5631 root 3u unix 0xf6389400 86047552 socket
saslauthd 5631 root 5u unix 0xf26f8100 86047553
/var/run/saslauthd/mux
saslauthd 5632 root 3u unix 0xf6389400 86047552 socket
saslauthd 5632 root 5u unix 0xf26f8100 86047553
/var/run/saslauthd/mux
saslauthd 5634 root 3u unix 0xf6389400 86047552 socket
saslauthd 5634 root 5u unix 0xf26f8100 86047553
/var/run/saslauthd/mux
saslauthd 5635 root 3u unix 0xf6389400 86047552 socket
saslauthd 5635 root 5u unix 0xf26f8100 86047553
/var/run/saslauthd/mux
When I first started setting up sasl support for exim after giving up on
pam, I got the usual access denied. So I gave the exim user ownership of
the /var/run/saslauthd/ directory and it changed from access denied to the
connection refused. From what I can tell exim should be able to find the
socket file without a problem. It has the required permissions on the
directory, and it knows the correct directory to look in. Also as
illustrated above saslauthd is creating its socket file in the same place
exim is looking for it. I have made sure that saslauthd is working with the
testsaslauthd and I even did an strace on it to make sure. It seems to be a
problem with the communication between exim and saslauthd (obviously lol).
Connection refused makes it sound like exim is looking in the right place
but for some reason the requests to saslauthd aren't getting through.
However since its a socket I wouldn't think anything like a firewall would
interfere since exim should just communicate directly with the socket.
Any more ideas as to whats causing this or suggestions about ways to find
out? Thanks.
Stanislaw Halik-2 wrote:
>
> On Wed, Dec 06, 2006, Stanislaw Halik wrote:
>> On Tue, Dec 05, 2006, JerseyDevil wrote:
>
>>> I am also trying [...] The exim user also has access to the socket
>>> directory. However, I keep getting a '435 Unable to authenticate at
>>> present (set_id=test): cannot connect to saslauthd daemon at
>>> /var/run/saslauthd: Connection refused' message when trying to login
>> ~~~~~~~~~~~~~~~~~~
>>> for smtp.
>
>> That's not where the saslauthd socket is being created. Check it with
>> `lsof -n | grep saslauthd'.
>
> Or better yet, use `lsof -nU | grep saslauthd'
> ~
> --
> Unix stuff :: http://tehran.lain.pl
> Yet Another RBL :: http://rbl.lain.pl
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
>
>
--
View this message in context:
http://www.nabble.com/exim4%2C-saslauthd%2C-pam%2C-tried-everything.-tf2764689.html#a7724894
Sent from the Exim Users mailing list archive at Nabble.com.
