> Crazedfred: > > >? Crazedfred <crazedf...@yahoo.com>: > > > > What is the result of:find / -name smtpd.conf > > > > > > sudo find / -name smtpd.conf > > > /usr/lib/sasl2/smtpd.conf > > > read the debian documentation! > > Could you elaborate? > Am I looking for the wrong file? > > I have seen several hints on this mailing list that Debian Postfix > wants to read /etc/postfix/sasl/smtpd.conf.
That's exactly where it is on mine. --- Strange. I'm on Debian 6, with all the packages that Patrick mentions in his script recording, and that file did not exist: $ cat /etc/postfix/sasl/smtpd.conf cat: /etc/postfix/sasl/smtpd.conf: No such file or director So, I just copied the file over: $ sudo cp /usr/lib/sasl2/smtpd.conf /etc/postfix/sasl/smtpd.conf $ cat /etc/postfix/sasl/smtpd.conf pwcheck_method: saslauthd mech_list: login plain Restarted both services: $ sudo service saslauthd restart Stopping SASL Authentication Daemon: saslauthd. Starting SASL Authentication Daemon: saslauthd. $ sudo service postfix restart Stopping Postfix Mail Transport Agent: postfix. Starting Postfix Mail Transport Agent: postfix. However, Postfix still won't accept my login: $ telnet localhost 25 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. 220 MyComputer ESMTP Postfix (Debian/GNU) auth plain MY-HASH 535 5.7.8 Error: authentication failed: authentication failure The good news, is that "saslfinger -s" is now reporting the right methods (strangely one file is listed twice): -- content of /usr/lib/sasl2/smtpd.conf -- pwcheck_method: saslauthd mech_list: login plain -- content of /etc/postfix/sasl/smtpd.conf -- pwcheck_method: saslauthd mech_list: login plain -- content of /etc/postfix/sasl/smtpd.conf -- pwcheck_method: saslauthd mech_list: login plain -- mechanisms on localhost -- 250-AUTH PLAIN LOGIN Looks like the same failure as before: postfix/smtpd[30926]: connect from localhost.localdomain[127.0.0.1] postfix/smtpd[30926]: match_hostname: localhost.localdomain ~? 127.0.0.0/8 postfix/smtpd[30926]: match_hostaddr: 127.0.0.1 ~? 127.0.0.0/8 postfix/smtpd[30926]: > localhost.localdomain[127.0.0.1]: 220 MyComputer ESMTP Postfix (Debian/GNU) postfix/smtpd[30926]: xsasl_cyrus_server_create: SASL service=smtp, realm=(null) postfix/smtpd[30926]: name_mask: noanonymous postfix/smtpd[30926]: watchdog_pat: 0xb922b518 postfix/smtpd[30926]: < localhost.localdomain[127.0.0.1]: auth plain MY-HASH postfix/smtpd[30926]: xsasl_cyrus_server_first: sasl_method plain, init_response MY-HASH postfix/smtpd[30926]: xsasl_cyrus_server_first: decoded initial response postfix/smtpd[30926]: warning: SASL authentication failure: Password verification failed postfix/smtpd[30926]: warning: localhost.localdomain[127.0.0.1]: SASL plain authentication failed: authentication failure postfix/smtpd[30926]: > localhost.localdomain[127.0.0.1]: 535 5.7.8 Error: authentication failed: authentication failure postfix/smtpd[30926]: watchdog_pat: 0xb922b518 postfix/smtpd[30926]: smtp_get: EOF This is frustrating, because it says the SASL authentication fails, when it clearly works: $ sudo testsaslauthd -u "t...@example.com" -p "testtest123" 0: OK "Success." Patrick, I watched your script demonstration but I'm afraid that besides the difference between our authentication choices (you set it up to authenticate local users, mine hits an LDAP tree) our setup appears to be very similar. And since SASL itself is succeeding, I'm assuming the error can't be there...
