On May 12 Kevin M. Barrett wrote:
> I have an off topic question regarding SASLAUTHD in a NIS
>environment, I'm in the process of deploying a second mail server in a NIS
>environment, the first one was run on the NIS Master so the shadow file was
>local, the second one will be on a NIS Slave so there will be no shadow
>file to speak of. What is the correct way to do simple plain text auth?
One way would be saslauthd -a pam.. If you're really using NIS and not
NIS+ you may be able to use crypt and the passwd map directly in your
authenticator!
> I also seem to be having a more basic issue with saslauthd, even
>with a local account in the password/shadow files the second server is
>saying the connection is refused as the log shows below:
>
>[code]
>2004-05-12 22:09:43 fixed_login authenticator failed for
>(kmb-dell.chantrynetworks.com) [192.168.5.123]: 435 Unable to authenticate
>at present (set_id=kmb): cannot connect to saslauthd daemon at
>/var/run/saslauthd/mux: Connection refused
>[/code]
It looks like saslauthd is not running..
What does testsaslauthd report?
