Author: Sam Michaels Date: To: matt CC: exim-users Subject: Re: [exim] Breakages possible from 4.51 to 4.60? (also saslauthd)
On 1/22/06, Matt Sealey <matt@???> wrote: > A small, OTHER question, I recently updated saslauthd from FreeBSD
> ports and exim lost it's authentication - it was complaining about
> not being able to acess /var/state/saslauthd/mux (which exists on
> my system as /var/run/saslauthd/mux and always has). I hacked it by
> symlinking state -> run, since it doesn't exist on FreeBSD, but is
> there a way to change the ${saslauthd.. expansion to use a different
> socket, if it is actually Exim that is complaining?
chmod o+x /var/run/saslauthd
My directory always has the wrong permissions when the daemon starts.
> Should I be using a better authentication for saslauthd than the
> server_condition = ${if saslauthd{{$1}{$2}}{1}{0}} syntax? I only
> need LOGIN and PLAIN to support Outlook and Mac Mail.App.
I have saslauthd using the "-a shadow" argument to completely bypass
PAM...so that's all I use.
