Nikolaus Rath
2007-Apr-03 09:05 UTC
[Pkg-exim4-users] cannot connect to /var/run/saslauthd/mux
Hello,
I have added Debian-exim to the sasl group:
[0] nelarikon:/etc/exim4/conf.d# groups Debian-exim
Debian-exim : Debian-exim sasl
The permissions for /var/run/saslauthd seem also correct:
[0] nelarikon:/etc/exim4/conf.d# dir /var/run/saslauthd/
total 12K
drwx--x--- 2 root sasl 4.0K Apr 3 09:53 .
drwxr-xr-x 15 root root 4.0K Apr 3 09:19 ..
srwxrwxrwx 1 root root 0 Apr 3 09:53 mux
-rw------- 1 root root 0 Apr 3 09:53 mux.accept
-rw------- 1 root root 6 Apr 3 09:53 saslauthd.pid
However, exim still produces this error:
[0] nelarikon:~# exim4 -d+auth -bh 127.0.0.1
Exim version 4.50 uid=0 gid=0 pid=22336 D=fbb95cfd
[...]
AUTH PLAIN [snip]
SSMTP<< AUTH PLAIN [snip]
host in smtp_accept_max_nonmail_hosts? yes (matched "*")
Running saslauthd authentication for user ""
saslauthd userid='''' servicename=''''
realm=''''
Cannot connect to saslauthd daemon (at
''/var/run/saslauthd/mux''): Permission denied
saslauthd: query failed (cannot connect to saslauthd daemon at
/var/run/saslauthd/mux: Permission denied)
plain_saslauthd_server authenticator:
$1 = \0user\0pass
expansion failed: cannot connect to saslauthd daemon at /var/run/saslauthd/mux:
Permission denied
SMTP>> 435 Unable to authenticate at present
When I change the permissions to "chmod 711 /var/run/saslauthd",
everything works fine. So it seems that exim is not really running as
user Debian-exim. Is there any way I can check this? (Yes, I restarted
after adding Debian-exim to the sasl group).
Or am I missing something very obvious?
Thanks in advance,
--Nikolaus
--
"de.alt.comp.kde Dumm und trotzdem UNIX verwenden? KDE ist die
Loesung."
Sven Paulus in <67hu21$43r$1@imperator.oops.sub.de>
Jonathan GF
2007-Apr-04 21:16 UTC
[Pkg-exim4-users] cannot connect to /var/run/saslauthd/mux
Hi, confirm in your exim4.conf / configure you have the following directives: exim_group = Debian-exim exim_user = Debian-exim Best regards, Jonahan GF On 4/3/07, Nikolaus Rath <Nikolaus@rath.org> wrote:> > Hello, > > I have added Debian-exim to the sasl group: > > [0] nelarikon:/etc/exim4/conf.d# groups Debian-exim > Debian-exim : Debian-exim sasl > > The permissions for /var/run/saslauthd seem also correct: > > [0] nelarikon:/etc/exim4/conf.d# dir /var/run/saslauthd/ > total 12K > drwx--x--- 2 root sasl 4.0K Apr 3 09:53 . > drwxr-xr-x 15 root root 4.0K Apr 3 09:19 .. > srwxrwxrwx 1 root root 0 Apr 3 09:53 mux > -rw------- 1 root root 0 Apr 3 09:53 mux.accept > -rw------- 1 root root 6 Apr 3 09:53 saslauthd.pid > > However, exim still produces this error: > > [0] nelarikon:~# exim4 -d+auth -bh 127.0.0.1 > Exim version 4.50 uid=0 gid=0 pid=22336 D=fbb95cfd > [...] > AUTH PLAIN [snip] > SSMTP<< AUTH PLAIN [snip] > host in smtp_accept_max_nonmail_hosts? yes (matched "*") > Running saslauthd authentication for user "" > saslauthd userid='''' servicename='''' realm='''' > Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): > Permission denied > saslauthd: query failed (cannot connect to saslauthd daemon at > /var/run/saslauthd/mux: Permission denied) > plain_saslauthd_server authenticator: > $1 = \0user\0pass > expansion failed: cannot connect to saslauthd daemon at > /var/run/saslauthd/mux: Permission denied > SMTP>> 435 Unable to authenticate at present > > > When I change the permissions to "chmod 711 /var/run/saslauthd", > everything works fine. So it seems that exim is not really running as > user Debian-exim. Is there any way I can check this? (Yes, I restarted > after adding Debian-exim to the sasl group). > > Or am I missing something very obvious? > > Thanks in advance, > > --Nikolaus > -- > "de.alt.comp.kde Dumm und trotzdem UNIX verwenden? KDE ist die > Loesung." > Sven Paulus in <67hu21$43r$1@imperator.oops.sub.de> > > > _______________________________________________ > Pkg-exim4-users mailing list > Pkg-exim4-users@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users >-- si secretum tibi sit, tege illud, vel revela -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/pkg-exim4-users/attachments/20070403/88634f18/attachment.html
Nikolaus Rath
2007-Apr-05 18:08 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
Hello, These lines were not present in the default configuration of the sarge package, so I assumed that exim was compiled with reasonable defaults. I have added them now nevertheless and it still does not work (same error). Best, Nikolaus "Jonathan GF" <jonathan@surestorm.com> writes:> Hi, > > confirm in your exim4.conf / configure you have the following directives: > > exim_group = Debian-exim > exim_user = Debian-exim > > > Best regards, > > Jonahan GF > > > On 4/3/07, Nikolaus Rath <Nikolaus@rath.org> wrote: >> >> Hello, >> >> I have added Debian-exim to the sasl group: >> >> [0] nelarikon:/etc/exim4/conf.d# groups Debian-exim >> Debian-exim : Debian-exim sasl >> >> The permissions for /var/run/saslauthd seem also correct: >> >> [0] nelarikon:/etc/exim4/conf.d# dir /var/run/saslauthd/ >> total 12K >> drwx--x--- 2 root sasl 4.0K Apr 3 09:53 . >> drwxr-xr-x 15 root root 4.0K Apr 3 09:19 .. >> srwxrwxrwx 1 root root 0 Apr 3 09:53 mux >> -rw------- 1 root root 0 Apr 3 09:53 mux.accept >> -rw------- 1 root root 6 Apr 3 09:53 saslauthd.pid >> >> However, exim still produces this error: >> >> [0] nelarikon:~# exim4 -d+auth -bh 127.0.0.1 >> Exim version 4.50 uid=0 gid=0 pid=22336 D=fbb95cfd >> [...] >> AUTH PLAIN [snip] >> SSMTP<< AUTH PLAIN [snip] >> host in smtp_accept_max_nonmail_hosts? yes (matched "*") >> Running saslauthd authentication for user "" >> saslauthd userid='''' servicename='''' realm='''' >> Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): >> Permission denied >> saslauthd: query failed (cannot connect to saslauthd daemon at >> /var/run/saslauthd/mux: Permission denied) >> plain_saslauthd_server authenticator: >> $1 = \0user\0pass >> expansion failed: cannot connect to saslauthd daemon at >> /var/run/saslauthd/mux: Permission denied >> SMTP>> 435 Unable to authenticate at present >> >> >> When I change the permissions to "chmod 711 /var/run/saslauthd", >> everything works fine. So it seems that exim is not really running as >> user Debian-exim. Is there any way I can check this? (Yes, I restarted >> after adding Debian-exim to the sasl group). >> >> Or am I missing something very obvious? >> >> Thanks in advance, >> >> --Nikolaus >> -- >> "de.alt.comp.kde Dumm und trotzdem UNIX verwenden? KDE ist die >> Loesung." >> Sven Paulus in <67hu21$43r$1@imperator.oops.sub.de> >> >> >> _______________________________________________ >> Pkg-exim4-users mailing list >> Pkg-exim4-users@lists.alioth.debian.org >> http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users >> > > > > -- > si secretum tibi sit, tege illud, vel revela > _______________________________________________ > Pkg-exim4-users mailing list > Pkg-exim4-users@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users--Nikolaus -- Gef?hrlich wird es, wenn die Dummen fleissig werden
Jonathan GF
2007-Apr-05 19:31 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
Under which user is exim running? On 4/5/07, Nikolaus Rath <Nikolaus@rath.org> wrote:> Hello, > > These lines were not present in the default configuration of the sarge > package, so I assumed that exim was compiled with reasonable defaults. > I have added them now nevertheless and it still does not work (same > error). > > Best, > Nikolaus > > > "Jonathan GF" <jonathan@surestorm.com> writes: > > Hi, > > > > confirm in your exim4.conf / configure you have the following directives: > > > > exim_group = Debian-exim > > exim_user = Debian-exim > > > > > > Best regards, > > > > Jonahan GF > > > > > > On 4/3/07, Nikolaus Rath <Nikolaus@rath.org> wrote: > >> > >> Hello, > >> > >> I have added Debian-exim to the sasl group: > >> > >> [0] nelarikon:/etc/exim4/conf.d# groups Debian-exim > >> Debian-exim : Debian-exim sasl > >> > >> The permissions for /var/run/saslauthd seem also correct: > >> > >> [0] nelarikon:/etc/exim4/conf.d# dir /var/run/saslauthd/ > >> total 12K > >> drwx--x--- 2 root sasl 4.0K Apr 3 09:53 . > >> drwxr-xr-x 15 root root 4.0K Apr 3 09:19 .. > >> srwxrwxrwx 1 root root 0 Apr 3 09:53 mux > >> -rw------- 1 root root 0 Apr 3 09:53 mux.accept > >> -rw------- 1 root root 6 Apr 3 09:53 saslauthd.pid > >> > >> However, exim still produces this error: > >> > >> [0] nelarikon:~# exim4 -d+auth -bh 127.0.0.1 > >> Exim version 4.50 uid=0 gid=0 pid=22336 D=fbb95cfd > >> [...] > >> AUTH PLAIN [snip] > >> SSMTP<< AUTH PLAIN [snip] > >> host in smtp_accept_max_nonmail_hosts? yes (matched "*") > >> Running saslauthd authentication for user "" > >> saslauthd userid='''' servicename='''' realm='''' > >> Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): > >> Permission denied > >> saslauthd: query failed (cannot connect to saslauthd daemon at > >> /var/run/saslauthd/mux: Permission denied) > >> plain_saslauthd_server authenticator: > >> $1 = \0user\0pass > >> expansion failed: cannot connect to saslauthd daemon at > >> /var/run/saslauthd/mux: Permission denied > >> SMTP>> 435 Unable to authenticate at present > >> > >> > >> When I change the permissions to "chmod 711 /var/run/saslauthd", > >> everything works fine. So it seems that exim is not really running as > >> user Debian-exim. Is there any way I can check this? (Yes, I restarted > >> after adding Debian-exim to the sasl group). > >> > >> Or am I missing something very obvious? > >> > >> Thanks in advance, > >> > >> --Nikolaus > >> -- > >> "de.alt.comp.kde Dumm und trotzdem UNIX verwenden? KDE ist die > >> Loesung." > >> Sven Paulus in <67hu21$43r$1@imperator.oops.sub.de> > >> > >> > >> _______________________________________________ > >> Pkg-exim4-users mailing list > >> Pkg-exim4-users@lists.alioth.debian.org > >> http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users > >> > > > > > > > > -- > > si secretum tibi sit, tege illud, vel revela > > _______________________________________________ > > Pkg-exim4-users mailing list > > Pkg-exim4-users@lists.alioth.debian.org > > http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users > > > --Nikolaus > -- > Gef?hrlich wird es, wenn die Dummen fleissig werden > > > _______________________________________________ > Pkg-exim4-users mailing list > Pkg-exim4-users@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users >-- Jonathan GF si secretum tibi sit, tege illud, vel revela
Ross Boylan
2007-Apr-05 19:53 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
On Thu, Apr 05, 2007 at 07:58:18PM +0200, Nikolaus Rath wrote:> Hello, > > These lines were not present in the default configuration of the sarge > package, so I assumed that exim was compiled with reasonable defaults. > I have added them now nevertheless and it still does not work (same > error). > > Best, > Nikolaus > > > "Jonathan GF" <jonathan@surestorm.com> writes: > > Hi, > > > > confirm in your exim4.conf / configure you have the following directives: > > > > exim_group = Debian-exim > > exim_user = Debian-exim > > > > > > Best regards, > > > > Jonahan GF > > > > > > On 4/3/07, Nikolaus Rath <Nikolaus@rath.org> wrote: > >> > >> Hello, > >> > >> I have added Debian-exim to the sasl group: > >> > >> [0] nelarikon:/etc/exim4/conf.d# groups Debian-exim > >> Debian-exim : Debian-exim sasl > >> > >> The permissions for /var/run/saslauthd seem also correct: > >> > >> [0] nelarikon:/etc/exim4/conf.d# dir /var/run/saslauthd/ > >> total 12K > >> drwx--x--- 2 root sasl 4.0K Apr 3 09:53 . > >> drwxr-xr-x 15 root root 4.0K Apr 3 09:19 .. > >> srwxrwxrwx 1 root root 0 Apr 3 09:53 mux > >> -rw------- 1 root root 0 Apr 3 09:53 mux.accept > >> -rw------- 1 root root 6 Apr 3 09:53 saslauthd.pid > >> > >> However, exim still produces this error: > >> > >> [0] nelarikon:~# exim4 -d+auth -bh 127.0.0.1 > >> Exim version 4.50 uid=0 gid=0 pid=22336 D=fbb95cfd > >> [...] > >> AUTH PLAIN [snip] > >> SSMTP<< AUTH PLAIN [snip] > >> host in smtp_accept_max_nonmail_hosts? yes (matched "*") > >> Running saslauthd authentication for user "" > >> saslauthd userid='''' servicename='''' realm='''' > >> Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): > >> Permission denied > >> saslauthd: query failed (cannot connect to saslauthd daemon at > >> /var/run/saslauthd/mux: Permission denied) > >> plain_saslauthd_server authenticator: > >> $1 = \0user\0pass > >> expansion failed: cannot connect to saslauthd daemon at > >> /var/run/saslauthd/mux: Permission denied > >> SMTP>> 435 Unable to authenticate at present > >> > >> > >> When I change the permissions to "chmod 711 /var/run/saslauthd", > >> everything works fine. So it seems that exim is not really running as > >> user Debian-exim. Is there any way I can check this? (Yes, I restarted > >> after adding Debian-exim to the sasl group). > >> > >> Or am I missing something very obvious? > >> > >> Thanks in advance, > >> > >> --Nikolaus > >> > >> > >> _______________________________________________ > >> Pkg-exim4-users mailing list > >> Pkg-exim4-users@lists.alioth.debian.org > >> http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users > >> > > > > > > > > > --NikolausUsing the split configuration (which is post-sarge, I think) and exim4 I have # Local users for whom we want IMAP delivery localpartlist imap_users = user1:user2 MAIN_TRUSTED_USERS = uucp:cyrus in a file I dropped under conf.d/main The localpart list is only because I''m only doing Cyrus for some users (see router coming up next), and cyrus is a trusted user so SIEVE redirect will work (though this is not your current problem) conf.d/850_local_imap_user imap_user: debug_print = "R: imap_user for $local_part@$domain" driver = accept local_parts = +imap_users transport = cyrus conf.d/50_rb_cyrus # Deliver to local cyrus IMAP server via LMTP cyrus: debug_print = "T: cyrus for $local_part@$domain" driver = lmtp delivery_date_add envelope_to_add return_path_add user = cyrus socket = /var/run/cyrus/socket/lmtp batch_max = 40 Notice I set the user to cyrus. If you''re trying to do this as Debian-exim, that may be your problem. Do you know that SASL is operating properly outside of exim? It is famously cranky. Ross
Jonathan GF
2007-Apr-05 22:13 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
if you exec an ls -ltr of that file does it exist? Is readeable? On 4/5/07, Nikolaus Rath <Nikolaus@rath.org> wrote:> Hello, > > These lines were not present in the default configuration of the sarge > package, so I assumed that exim was compiled with reasonable defaults. > I have added them now nevertheless and it still does not work (same > error). > > Best, > Nikolaus > > > "Jonathan GF" <jonathan@surestorm.com> writes: > > Hi, > > > > confirm in your exim4.conf / configure you have the following directives: > > > > exim_group = Debian-exim > > exim_user = Debian-exim > > > > > > Best regards, > > > > Jonahan GF > > > > > > On 4/3/07, Nikolaus Rath <Nikolaus@rath.org> wrote: > >> > >> Hello, > >> > >> I have added Debian-exim to the sasl group: > >> > >> [0] nelarikon:/etc/exim4/conf.d# groups Debian-exim > >> Debian-exim : Debian-exim sasl > >> > >> The permissions for /var/run/saslauthd seem also correct: > >> > >> [0] nelarikon:/etc/exim4/conf.d# dir /var/run/saslauthd/ > >> total 12K > >> drwx--x--- 2 root sasl 4.0K Apr 3 09:53 . > >> drwxr-xr-x 15 root root 4.0K Apr 3 09:19 .. > >> srwxrwxrwx 1 root root 0 Apr 3 09:53 mux > >> -rw------- 1 root root 0 Apr 3 09:53 mux.accept > >> -rw------- 1 root root 6 Apr 3 09:53 saslauthd.pid > >> > >> However, exim still produces this error: > >> > >> [0] nelarikon:~# exim4 -d+auth -bh 127.0.0.1 > >> Exim version 4.50 uid=0 gid=0 pid=22336 D=fbb95cfd > >> [...] > >> AUTH PLAIN [snip] > >> SSMTP<< AUTH PLAIN [snip] > >> host in smtp_accept_max_nonmail_hosts? yes (matched "*") > >> Running saslauthd authentication for user "" > >> saslauthd userid='''' servicename='''' realm='''' > >> Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): > >> Permission denied > >> saslauthd: query failed (cannot connect to saslauthd daemon at > >> /var/run/saslauthd/mux: Permission denied) > >> plain_saslauthd_server authenticator: > >> $1 = \0user\0pass > >> expansion failed: cannot connect to saslauthd daemon at > >> /var/run/saslauthd/mux: Permission denied > >> SMTP>> 435 Unable to authenticate at present > >> > >> > >> When I change the permissions to "chmod 711 /var/run/saslauthd", > >> everything works fine. So it seems that exim is not really running as > >> user Debian-exim. Is there any way I can check this? (Yes, I restarted > >> after adding Debian-exim to the sasl group). > >> > >> Or am I missing something very obvious? > >> > >> Thanks in advance, > >> > >> --Nikolaus > >> -- > >> "de.alt.comp.kde Dumm und trotzdem UNIX verwenden? KDE ist die > >> Loesung." > >> Sven Paulus in <67hu21$43r$1@imperator.oops.sub.de> > >> > >> > >> _______________________________________________ > >> Pkg-exim4-users mailing list > >> Pkg-exim4-users@lists.alioth.debian.org > >> http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users > >> > > > > > > > > -- > > si secretum tibi sit, tege illud, vel revela > > _______________________________________________ > > Pkg-exim4-users mailing list > > Pkg-exim4-users@lists.alioth.debian.org > > http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users > > > --Nikolaus > -- > Gef?hrlich wird es, wenn die Dummen fleissig werden > > > _______________________________________________ > Pkg-exim4-users mailing list > Pkg-exim4-users@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users >-- Jonathan GF si secretum tibi sit, tege illud, vel revela
Nikolaus Rath
2007-Apr-07 10:08 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
Hi, How exactly do I find this out? Here is what ps shows: [0] ebox:/etc/logcheck# ps axl | grep exim 4 108 5144 1 15 0 9392 2456 - Ss ? 0:00 /usr/sbin/exim4 -bd -q30m 0 0 3987 1736 17 0 1548 472 pipe_w S+ pts/0 0:00 grep exim [0] ebox:/etc/logcheck# grep 108 /etc/passwd Debian-exim:x:108:108::/var/spool/exim4:/bin/false Best, Nikolaus "Jonathan GF" <jonathan@surestorm.com> writes:> Under which user is exim running? > > On 4/5/07, Nikolaus Rath <Nikolaus@rath.org> wrote: >> Hello, >> >> These lines were not present in the default configuration of the sarge >> package, so I assumed that exim was compiled with reasonable defaults. >> I have added them now nevertheless and it still does not work (same >> error). >> >> Best, >> Nikolaus >> >> >> "Jonathan GF" <jonathan@surestorm.com> writes: >> > Hi, >> > >> > confirm in your exim4.conf / configure you have the following directives: >> > >> > exim_group = Debian-exim >> > exim_user = Debian-exim >> > >> > >> > Best regards, >> > >> > Jonahan GF >> > >> > >> > On 4/3/07, Nikolaus Rath <Nikolaus@rath.org> wrote: >> >> >> >> Hello, >> >> >> >> I have added Debian-exim to the sasl group: >> >> >> >> [0] nelarikon:/etc/exim4/conf.d# groups Debian-exim >> >> Debian-exim : Debian-exim sasl >> >> >> >> The permissions for /var/run/saslauthd seem also correct: >> >> >> >> [0] nelarikon:/etc/exim4/conf.d# dir /var/run/saslauthd/ >> >> total 12K >> >> drwx--x--- 2 root sasl 4.0K Apr 3 09:53 . >> >> drwxr-xr-x 15 root root 4.0K Apr 3 09:19 .. >> >> srwxrwxrwx 1 root root 0 Apr 3 09:53 mux >> >> -rw------- 1 root root 0 Apr 3 09:53 mux.accept >> >> -rw------- 1 root root 6 Apr 3 09:53 saslauthd.pid >> >> >> >> However, exim still produces this error: >> >> >> >> [0] nelarikon:~# exim4 -d+auth -bh 127.0.0.1 >> >> Exim version 4.50 uid=0 gid=0 pid=22336 D=fbb95cfd >> >> [...] >> >> AUTH PLAIN [snip] >> >> SSMTP<< AUTH PLAIN [snip] >> >> host in smtp_accept_max_nonmail_hosts? yes (matched "*") >> >> Running saslauthd authentication for user "" >> >> saslauthd userid='''' servicename='''' realm='''' >> >> Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): >> >> Permission denied >> >> saslauthd: query failed (cannot connect to saslauthd daemon at >> >> /var/run/saslauthd/mux: Permission denied) >> >> plain_saslauthd_server authenticator: >> >> $1 = \0user\0pass >> >> expansion failed: cannot connect to saslauthd daemon at >> >> /var/run/saslauthd/mux: Permission denied >> >> SMTP>> 435 Unable to authenticate at present >> >> >> >> >> >> When I change the permissions to "chmod 711 /var/run/saslauthd", >> >> everything works fine. So it seems that exim is not really running as >> >> user Debian-exim. Is there any way I can check this? (Yes, I restarted >> >> after adding Debian-exim to the sasl group). >> >> >> >> Or am I missing something very obvious? >> >> >> >> Thanks in advance, >> >> >> >> --Nikolaus >> >> -- >> >> "de.alt.comp.kde Dumm und trotzdem UNIX verwenden? KDE ist die >> >> Loesung." >> >> Sven Paulus in <67hu21$43r$1@imperator.oops.sub.de> >> >> >> >> >> >> _______________________________________________ >> >> Pkg-exim4-users mailing list >> >> Pkg-exim4-users@lists.alioth.debian.org >> >> http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users >> >> >> > >> > >> > >> > -- >> > si secretum tibi sit, tege illud, vel revela >> > _______________________________________________ >> > Pkg-exim4-users mailing list >> > Pkg-exim4-users@lists.alioth.debian.org >> > http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users >> >> >> --Nikolaus >> -- >> Gef?hrlich wird es, wenn die Dummen fleissig werden >> >> >> _______________________________________________ >> Pkg-exim4-users mailing list >> Pkg-exim4-users@lists.alioth.debian.org >> http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users >> > > > -- > Jonathan GF > si secretum tibi sit, tege illud, vel revela > _______________________________________________ > Pkg-exim4-users mailing list > Pkg-exim4-users@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users--Nikolaus --> Bekomme ich das mit einer wilden Kombination aus find, sed, cp und > xargs hin oder sollte ich besser ein Perlskript schreiben?Verwende Perl. Shell will man koennen, dann aber nicht verwenden." - Marc Haber u. Kristian K?hntopp, dcoum
Nikolaus Rath
2007-Apr-07 10:10 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
Hello, [0] ebox:/etc/logcheck# su -s /bin/bash Debian-exim [0] ebox:/etc/logcheck# ls -ltr /var/run/saslauthd/mux srwxrwxrwx 1 root root 0 Apr 3 14:39 /var/run/saslauthd/mux Everything ok as far as I can tell. Best, Nikolaus "Jonathan GF" <jonathan@surestorm.com> writes:> if you exec an ls -ltr of that file does it exist? Is readeable? > > On 4/5/07, Nikolaus Rath <Nikolaus@rath.org> wrote: >> Hello, >> >> These lines were not present in the default configuration of the sarge >> package, so I assumed that exim was compiled with reasonable defaults. >> I have added them now nevertheless and it still does not work (same >> error). >> >> Best, >> Nikolaus >> >> >> "Jonathan GF" <jonathan@surestorm.com> writes: >> > Hi, >> > >> > confirm in your exim4.conf / configure you have the following directives: >> > >> > exim_group = Debian-exim >> > exim_user = Debian-exim >> > >> > >> > Best regards, >> > >> > Jonahan GF >> > >> > >> > On 4/3/07, Nikolaus Rath <Nikolaus@rath.org> wrote: >> >> >> >> Hello, >> >> >> >> I have added Debian-exim to the sasl group: >> >> >> >> [0] nelarikon:/etc/exim4/conf.d# groups Debian-exim >> >> Debian-exim : Debian-exim sasl >> >> >> >> The permissions for /var/run/saslauthd seem also correct: >> >> >> >> [0] nelarikon:/etc/exim4/conf.d# dir /var/run/saslauthd/ >> >> total 12K >> >> drwx--x--- 2 root sasl 4.0K Apr 3 09:53 . >> >> drwxr-xr-x 15 root root 4.0K Apr 3 09:19 .. >> >> srwxrwxrwx 1 root root 0 Apr 3 09:53 mux >> >> -rw------- 1 root root 0 Apr 3 09:53 mux.accept >> >> -rw------- 1 root root 6 Apr 3 09:53 saslauthd.pid >> >> >> >> However, exim still produces this error: >> >> >> >> [0] nelarikon:~# exim4 -d+auth -bh 127.0.0.1 >> >> Exim version 4.50 uid=0 gid=0 pid=22336 D=fbb95cfd >> >> [...] >> >> AUTH PLAIN [snip] >> >> SSMTP<< AUTH PLAIN [snip] >> >> host in smtp_accept_max_nonmail_hosts? yes (matched "*") >> >> Running saslauthd authentication for user "" >> >> saslauthd userid='''' servicename='''' realm='''' >> >> Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): >> >> Permission denied >> >> saslauthd: query failed (cannot connect to saslauthd daemon at >> >> /var/run/saslauthd/mux: Permission denied) >> >> plain_saslauthd_server authenticator: >> >> $1 = \0user\0pass >> >> expansion failed: cannot connect to saslauthd daemon at >> >> /var/run/saslauthd/mux: Permission denied >> >> SMTP>> 435 Unable to authenticate at present >> >> >> >> >> >> When I change the permissions to "chmod 711 /var/run/saslauthd", >> >> everything works fine. So it seems that exim is not really running as >> >> user Debian-exim. Is there any way I can check this? (Yes, I restarted >> >> after adding Debian-exim to the sasl group). >> >> >> >> Or am I missing something very obvious? >> >> >> >> Thanks in advance, >> >> >> >> --Nikolaus >> >> -- >> >> "de.alt.comp.kde Dumm und trotzdem UNIX verwenden? KDE ist die >> >> Loesung." >> >> Sven Paulus in <67hu21$43r$1@imperator.oops.sub.de> >> >> >> >> >> >> _______________________________________________ >> >> Pkg-exim4-users mailing list >> >> Pkg-exim4-users@lists.alioth.debian.org >> >> http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users >> >> >> > >> > >> > >> > -- >> > si secretum tibi sit, tege illud, vel revela >> > _______________________________________________ >> > Pkg-exim4-users mailing list >> > Pkg-exim4-users@lists.alioth.debian.org >> > http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users >> >> >> --Nikolaus >> -- >> Gef?hrlich wird es, wenn die Dummen fleissig werden >> >> >> _______________________________________________ >> Pkg-exim4-users mailing list >> Pkg-exim4-users@lists.alioth.debian.org >> http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users >> > > > -- > Jonathan GF > si secretum tibi sit, tege illud, vel revela > _______________________________________________ > Pkg-exim4-users mailing list > Pkg-exim4-users@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users--Nikolaus -- ?Wenn ich eine SuSE-CD an ein Schwein binde und dieses trete, laufen KDE & Co. auch ohne RAM recht schnell.? --Robin S. Socha in de.comp.os.unix.linux.newusers--
Nikolaus Rath
2007-Apr-07 11:08 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
Ross Boylan <ross@biostat.ucsf.edu> writes:>> >> [0] nelarikon:~# exim4 -d+auth -bh 127.0.0.1 >> >> Exim version 4.50 uid=0 gid=0 pid=22336 D=fbb95cfd >> >> [...] >> >> AUTH PLAIN [snip] >> >> SSMTP<< AUTH PLAIN [snip] >> >> host in smtp_accept_max_nonmail_hosts? yes (matched "*") >> >> Running saslauthd authentication for user "" >> >> saslauthd userid='''' servicename='''' realm='''' >> >> Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): >> >> Permission denied > > conf.d/50_rb_cyrus > # Deliver to local cyrus IMAP server via LMTP > cyrus: > debug_print = "T: cyrus for $local_part@$domain" > driver = lmtp > delivery_date_add > envelope_to_add > return_path_add > user = cyrus > socket = /var/run/cyrus/socket/lmtp > batch_max = 40 > > Notice I set the user to cyrus. If you''re trying to do this as > Debian-exim, that may be your problem.Hmm. It seems to be that this is not at all related to my problem. My problem occurs during SMTP authentication, not when exim tries to deliver something to cyrus.> Do you know that SASL is operating properly outside of exim? It is > famously cranky.Yes, it works as soon as I change the permissions of /var/run/saslauthd to world executable. Best, --Nikolaus -- ?Heute kann man ja kaum noch eine AOL-CD aus dem Fenster werfen, ohne jemanden zu treffen, der einen SuSE-Karton unter dem Arm tr?gt.? - Jochem Huhmann, de.comp.os.unix.discussion
Nikolaus Rath
2007-Apr-12 14:09 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
Hello, Nikolaus Rath <Nikolaus@rath.org> writes:> Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): Permission denied > saslauthd: query failed (cannot connect to saslauthd daemon at /var/run/saslauthd/mux: Permission denied) > plain_saslauthd_server authenticator:Is there really no one able to help with this? Seems that I don''t even receive the famous "please ask a smart question" reply... Still hoping, --Nikolaus -- (Bitte wenden)
Marc Haber
2007-Apr-12 14:18 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
On Thu, Apr 12, 2007 at 02:24:35PM +0200, Nikolaus Rath wrote:> Nikolaus Rath <Nikolaus@rath.org> writes: > > Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): Permission denied > > saslauthd: query failed (cannot connect to saslauthd daemon at /var/run/saslauthd/mux: Permission denied) > > plain_saslauthd_server authenticator: > > Is there really no one able to help with this? Seems that I don''t even > receive the famous "please ask a smart question" reply...Having no clue about sasl and cyrus, I couldn''t even judge whether you were asking a smart question or not. Sorry ;) Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don''t trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
Christian Schmidt
2007-Apr-12 16:39 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
Hello Nikolaus, Nikolaus Rath, 12.04.2007 (d.m.y):> Nikolaus Rath <Nikolaus@rath.org> writes: > > Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): Permission denied > > saslauthd: query failed (cannot connect to saslauthd daemon at /var/run/saslauthd/mux: Permission denied) > > plain_saslauthd_server authenticator: > > Is there really no one able to help with this? Seems that I don''t even > receive the famous "please ask a smart question" reply...Which user ID is your saslauthd running with? Gruss/Regards, Christian Schmidt -- Q: Why did the programmer call his mother long distance? A: Because that was her name. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-exim4-users/attachments/20070412/043ff933/attachment.pgp
Nikolaus Rath
2007-Apr-13 11:08 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
Christian Schmidt <Christian.Schmidt@chemie.uni-hamburg.de> writes:> Hello Nikolaus, > > Nikolaus Rath, 12.04.2007 (d.m.y): > >> Nikolaus Rath <Nikolaus@rath.org> writes: >> > Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): Permission denied >> > saslauthd: query failed (cannot connect to saslauthd daemon at /var/run/saslauthd/mux: Permission denied) >> > plain_saslauthd_server authenticator: >> >> Is there really no one able to help with this? Seems that I don''t even >> receive the famous "please ask a smart question" reply... > > Which user ID is your saslauthd running with?saslautd is running as root. Best, --Nikolaus -- ?Heute kann man ja kaum noch eine AOL-CD aus dem Fenster werfen, ohne jemanden zu treffen, der einen SuSE-Karton unter dem Arm tr?gt.? - Jochem Huhmann, de.comp.os.unix.discussion
Christian Schmidt
2007-Apr-13 11:31 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
Hallo Nikolaus, Nikolaus Rath, 12.04.2007 (d.m.y):> Christian Schmidt <Christian.Schmidt@chemie.uni-hamburg.de> writes: > > Hello Nikolaus, > > > > Nikolaus Rath, 12.04.2007 (d.m.y): > > > >> Nikolaus Rath <Nikolaus@rath.org> writes: > >> > Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): Permission denied > >> > saslauthd: query failed (cannot connect to saslauthd daemon at /var/run/saslauthd/mux: Permission denied) > >> > plain_saslauthd_server authenticator: > >> > >> Is there really no one able to help with this? Seems that I don''t even > >> receive the famous "please ask a smart question" reply... > > > > Which user ID is your saslauthd running with? > > saslautd is running as root.I''d try running it with the same UID that exim runs with. Gruss/Regards, Christian Schmidt -- Are you making all this up as you go along? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-exim4-users/attachments/20070413/c2b628be/attachment.pgp
Nikolaus Rath
2007-Apr-13 15:08 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
Christian Schmidt <Christian.Schmidt@chemie.uni-hamburg.de> writes:> Hallo Nikolaus, > > Nikolaus Rath, 12.04.2007 (d.m.y): > >> Christian Schmidt <Christian.Schmidt@chemie.uni-hamburg.de> writes: >> > Hello Nikolaus, >> > >> > Nikolaus Rath, 12.04.2007 (d.m.y): >> > >> >> Nikolaus Rath <Nikolaus@rath.org> writes: >> >> > Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): Permission denied >> >> > saslauthd: query failed (cannot connect to saslauthd daemon at /var/run/saslauthd/mux: Permission denied) >> >> > plain_saslauthd_server authenticator: >> >> >> >> Is there really no one able to help with this? Seems that I don''t even >> >> receive the famous "please ask a smart question" reply... >> > >> > Which user ID is your saslauthd running with? >> >> saslautd is running as root. > > I''d try running it with the same UID that exim runs with.No offense intended, but are you sure that you know what you are talking about? The whole point of saslauthd is that it runs as a different user and can therefore authenticate against databases that the exim user cannot access. Apart from that the problem is that exim cannot connect to a unix socket. I fail to see how changing the uid of a different process will influence the access rights of the exim process on an entity in the file system. Best, --Nikolaus -- $|++;@_=map{chr(ord($_)-$|)}split//,"Kvtu!bopuifs!Qfsm!Ibdlfs-";$\="\r";@a=qw( < ^ > v);$?="_"x25;until($?!~m~_~){$o=int(rand 28)+65;next if$s{$o}++;$o==91? $o=44:($o==92?$o=32:0);$g=chr$o;for(0..24){if($_[$_]=~m)$g)i){for$m(@a,$_[$_]) {substr $?,$_,$|,$m;print$?;select$/,$/,$/,0.1}}}print$?}print$/
Marc Haber
2007-Apr-14 10:15 UTC
[Pkg-exim4-users] cannot connect to /var/run/saslauthd/mux
On Tue, Apr 03, 2007 at 10:07:24AM +0200, Nikolaus Rath wrote:> I have added Debian-exim to the sasl group: > > [0] nelarikon:/etc/exim4/conf.d# groups Debian-exim > Debian-exim : Debian-exim sasl > > The permissions for /var/run/saslauthd seem also correct: > > [0] nelarikon:/etc/exim4/conf.d# dir /var/run/saslauthd/ > total 12K > drwx--x--- 2 root sasl 4.0K Apr 3 09:53 . > drwxr-xr-x 15 root root 4.0K Apr 3 09:19 .. > srwxrwxrwx 1 root root 0 Apr 3 09:53 mux > -rw------- 1 root root 0 Apr 3 09:53 mux.accept > -rw------- 1 root root 6 Apr 3 09:53 saslauthd.pid > > However, exim still produces this error: > > [0] nelarikon:~# exim4 -d+auth -bh 127.0.0.1 > Exim version 4.50 uid=0 gid=0 pid=22336 D=fbb95cfd > [...] > AUTH PLAIN [snip] > SSMTP<< AUTH PLAIN [snip] > host in smtp_accept_max_nonmail_hosts? yes (matched "*") > Running saslauthd authentication for user "" > saslauthd userid='''' servicename='''' realm='''' > Cannot connect to saslauthd daemon (at ''/var/run/saslauthd/mux''): Permission denied > saslauthd: query failed (cannot connect to saslauthd daemon at /var/run/saslauthd/mux: Permission denied) > plain_saslauthd_server authenticator: > $1 = \0user\0pass > expansion failed: cannot connect to saslauthd daemon at /var/run/saslauthd/mux: Permission denied > SMTP>> 435 Unable to authenticate at present > > > When I change the permissions to "chmod 711 /var/run/saslauthd", > everything works fine. So it seems that exim is not really running as > user Debian-exim. Is there any way I can check this? (Yes, I restarted > after adding Debian-exim to the sasl group).This seems to be an issue in a later version of exim4 in sarge. Updating to etch or taking exim 4.63 from backports.org seems to fix the issue. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don''t trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
Christian Schmidt
2007-Apr-14 10:50 UTC
[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux
Hello Nikolaus, Nikolaus Rath, 13.04.2007 (d.m.y):> Christian Schmidt <Christian.Schmidt@chemie.uni-hamburg.de> writes: > > > > I''d try running it with the same UID that exim runs with. > > No offense intended, but are you sure that you know what you are > talking about?No, obviously not. Sorry. I''ll take some more thoughts next time.> The whole point of saslauthd is that it runs as a > different user and can therefore authenticate against databases that > the exim user cannot access. Apart from that the problem is that exim > cannot connect to a unix socket. I fail to see how changing the uid of > a different process will influence the access rights of the exim > process on an entity in the file system.I got my exim working with SASL. All I had to do was creating a file /usr/lib/sasl2/exim.conf containing the following lines: pwcheck_method:saslauthd log_level:9 The corresponding authenticator looks like this: sasl_plain: driver = cyrus_sasl public_name = PLAIN server_set_id = $1 Gruss/Regards, Christian Schmidt -- You will be held hostage by a radical group. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-exim4-users/attachments/20070414/72aa4e13/attachment.pgp