On Sun January 17 2010, Paul Cartwright wrote: > What does /var/log/exim4/mainlog say when you try to authenticate?
when I do a ps saslauthd I see this: ps -ef|grep sasl root 8458 1 0 08:12 ? 00:00:00 /usr/sbin/saslauthd -a pam -c -m /var/spool/postfix/var/run/saslauthd -r -n 5 root 8459 8458 0 08:12 ? 00:00:00 /usr/sbin/saslauthd -a pam -c -m /var/spool/postfix/var/run/saslauthd -r -n 5 root 8462 8458 0 08:12 ? 00:00:00 /usr/sbin/saslauthd -a pam -c -m /var/spool/postfix/var/run/saslauthd -r -n 5 root 8464 8458 0 08:12 ? 00:00:00 /usr/sbin/saslauthd -a pam -c -m /var/spool/postfix/var/run/saslauthd -r -n 5 root 8466 8458 0 08:12 ? 00:00:00 /usr/sbin/saslauthd -a pam -c -m /var/spool/postfix/var/run/saslauthd -r -n 5 yet mux is here: ls -l /var/spool/postfix/var/run/saslauthd total 932 -rw------- 1 root root 0 2010-01-17 08:12 cache.flock -rw------- 1 root root 945152 2010-01-17 08:12 cache.mmap srwxrwxrwx 1 root root 0 2010-01-17 08:12 mux -rw------- 1 root root 0 2010-01-17 08:12 mux.accept -rw------- 1 root root 5 2010-01-17 08:12 saslauthd.pid where is the config file that tells it where saslauthd is? I stopped saslauthd, and restarted it with this line: # /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -r -n 5 and IT WORKED. so I need to find out what is making saslauthd go to the wrong place. -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 http://usdebtclock.org/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
