![]() |
Cannot connect to saslauthd server: Permission denied
Hi all,
I saw the other thread on this (chmod 777 .... and so on) and that did not work. I am still getting this error. Here's my postfix configuration (main.cfg). Please let me know what other information I can provide: there's obviously a permissions problems here but I thought saslauthd ran as root. Code:
# See /usr/share/postfix/main.cf.dist for a commented, more complete versionCheers, Migm |
Please run
Code:
adduser postfix sasl |
Quote:
Thanks for your help. I had already tried this still getting the following Code:
Apr 26 10:55:19 tcc1 postfix/smtpd[21126]: warning: SASL authentication failure: cannot connect to saslauthd server: Permission deniedCode:
postfix:x:110:120::/var/spool/postfix:/bin/falseCode:
sasl:x:1001:postfix |
Well, i got it to work, but I am not confident that my methodology was very secure.
I ran smtpd with strace debugging turned on and saw the reason that things weren't working was that postfix was searching for my saslauthd file in /var/run/saslauthd. The only mention of the /var/run directory i saw was in the saslauthd init.d file, which i changed to reflect the /var/spool/postfix/var/run/saslauthd directory. That didn't work, so I ended up copying and linking all the files necessary from the /spool directory into the /var/run/saslauthd directory. I can't imagine this is terribly secure? Where is postfix pulling this /var/run directory from, anyway? If i can change that, I'd rather delete what I've done and do it the correct way. Thanks! migm |
Postfix is running chrooted, so /var/run translates to /var/spool/postfix/var/run.
|
Quote:
|
i found a basic solution described here: http://www.ehcp.net/?q=node/149#comment-668
|
"Cannot connect to saslauthd server: Permission denied" was caused by permission errors for me. Changed /var/run/saslauthd permissions, chmod a+rx and things worked.
Postfix was not chroot'd and there was no group for saslauthd to add Postfix. |
Quote:
|
password
For those that all of the above doesn't solve the problem... check your password!
If it has a '#' sign all that is after the # gets ignored in "/etc/pam.d /smtp" and therefore you will have these nice errors in /var/log/auth.log : pam_mysql - required option "db" is not set DEBUG: auth_pam: pam_authenticate failed: Error in service module Source: here. |
| All times are GMT +2. The time now is 11:29. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.