Etch sasl weirdness

[Hans du Plooy <koffiejunkielistlurker@koffiejunkie.za.net>]

Hi guys,

I'm setting up an Etch server for postfix with smtp auth.   I changed 
/etc/default/saslauthd so that the mux file gets made under 
/var/spool/postfix/var/run/saslauthd.  I restarted saslauthd, and 
checked that it's working right.  It is making the file in the right 
place, and ps shows me that it is reading the right settings:

# ps xf
3521 ?        Ss     0:00 /usr/sbin/saslauthd -a pam -c -m 
/var/spool/postfix/var/run/saslauthd -r -n 5
3526 ?        S      0:00  \_ /usr/sbin/saslauthd -a pam -c -m 
/var/spool/postfix/var/run/saslauthd -r -n 5
3527 ?        S      0:00  \_ /usr/sbin/saslauthd -a pam -c -m 
/var/spool/postfix/var/run/saslauthd -r -n 5
3528 ?        S      0:00  \_ /usr/sbin/saslauthd -a pam -c -m 
/var/spool/postfix/var/run/saslauthd -r -n 5
3529 ?        S      0:00  \_ /usr/sbin/saslauthd -a pam -c -m 
/var/spool/postfix/var/run/saslauthd -r -n 5

But I'm getting this:

# testsaslauthd -u user -p password
connect() : No such file or directory

and when strace it, I see:

connect(3, {sa_family=AF_FILE, path="/var/run/saslauthd/mux"}, 110) = -1 
ENOENT (No such file or directory)

So saslauthd so sasl seems to be ignoring the -m stuff.  If I make a 
symling  /var/run/saslauthd pointing to 
/var/spool/postfix/var/run/saslauthd it works fine.

Is this a bug or am I missing something I should have done?

Thanks
Hans