[Pkg-exim4-users] Re: cannot connect to /var/run/saslauthd/mux

Christian Schmidt Christian.Schmidt at chemie.uni-hamburg.de
Sat Apr 14 10:49:40 UTC 2007

Hello Nikolaus,

Nikolaus Rath, 13.04.2007 (d.m.y):

> Christian Schmidt <Christian.Schmidt at 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:
The corresponding authenticator looks like this:
  driver = cyrus_sasl
  public_name = PLAIN
  server_set_id = $1

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

More information about the Pkg-exim4-users mailing list