![]() |
SASL AUTH with postfix on Sarge
Hi,
I'm desperately trying to authenticate via sasl2 through postfix installed on a Debian Sarge. I wanted to use sasldb authentication, so I created a test account : login:test password:test with no realm info. TLS support in postfix is not activated at the moment. Here's the output for a local telnet test: Code:
# telnet localhost 25Code:
warning: SASL authentication failure: Password verification failedCode:
# testsaslauthd -u test -p test -f /var/spool/postfix/var/run/saslauthd/muxThanks for any assistance to solve this problem.;) I already spent a couple of days tearing my hair off on this issue, but I could not find neither any valuable info on the internet nor any workaround on my own.:mad: Sorry for all the code provided... Here is my main.cf: Code:
smtpd_banner = $myhostname ESMTP (Debian/GNU)Code:
smtp inet n - - - - smtpdCode:
pwcheck_method: auxprop |
Did you create the user's password with saslpasswd2? See
Code:
man saslpasswd2 |
yes, exactly what I did...:)
|
Same problem as Keulu
Hello!
I have the same problem as Keulu here and I can't find any solution to the problem. I had a completely new installation of Debian 3.1 when starting to install according to the "Perfect Setup" for the correct version of Debian. I followed every step by copying and pasting, but still the SMTP AUTH functionality doesn't work. Everytime I try to connect with the client (Microsoft Outlook Express & others) the password isn't accepted. In the logfile I get the following error everytime I try to authenticate a user: Aug 28 09:57:10 postfix/smtpd[12365]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory I have checked with testsaslauthd and it responds OK. I have set password with saslpasswd2 to no awail. What else can I try? Can I do other checks to see if everything is working? Since the logfile is referring to that smtpd is unable to connect to saslauthd is there anything I can do to make sure it is connecting? How does it connect? Is it using a pipe or a socket? If the pipe is known perhaps one can try that, manually? I am out of options right now. I have checked every place on Internet I can find that discuss this problem. It was so easy for version 3.0 of Debian. Everything worked directly. Please help! |
Quote:
Code:
ps aux | grep saslauthd |
Hello, thanks for the reply!
I just got it working... I changed in my client from port 465 tcp to use port 25 tcp. In the earlier version I had to use port 465 and not 25 to get it working. Why is it different now?? |
I guess the process on port 465 isn't running chrooted, as is the process on port 25. You can check in /etc/postfix/master.cf.
|
| All times are GMT +2. The time now is 09:49. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.