On 18-Mar-2009, at 02:38, Patrick Ben Koetter wrote:
* LuKreme <krem...@kreme.com>:
path to which socket there?
$ ls -ls /var/run/saslauthd/
total 2
0 srwxrwxrwx 1 root postfix 0 Mar 17 03:52 mux
mux it is.
Starting saslauthd.
saslauthd[91067] :main : could not chdir to: /var/run/
saslauthd/mux
saslauthd[91067] :main : chdir: No such file or directory
saslauthd[91067] :main : Check to make sure the directory
exists and is
saslauthd[91067] :main : writeable by the user this process
runs as.
If I set it to /var/run/saslauthd/ it starts up
root 91078 0.0 0.3 5168 1924 ?? Is 8:24AM 0:00.01 /usr/
local/sbin/saslauthd -a pam -m /var/run/saslauthd/
pwcheck_method: saslauthd
mech_list: plain login
Read it this way: libsasl use saslauthd to process authentication.
saslauthd
use PAM as backend. PAM use PAM mysql as backend ...
Ok, but I still get:
submit-tls/smtpd[91093]: Anonymous TLS connection established from
c-67-164-162-51.hsd1.co.comcast.net[67.164.162.51]: TLSv1 with cipher
AES128-SHA (128/128 bits)
submit-tls/smtpd[91093]: warning: SASL authentication failure: Can
only find author (no password)
submit-tls/smtpd[91093]: warning:
c-67-164-162-51.hsd1.co.comcast.net[67.164.162.51]: SASL PLAIN
authentication failed: bad protocol / cancel
submit-tls/smtpd[91093]: lost connection after AUTH from
c-67-164-162-51.hsd1.co.comcast.net[67.164.162.51]
Is there anyway to test sasl locally and verbosely so that I can get a
better idea of what's going on. Something like authtest for courier?
Looking a lot I see that most people are creating a plaintext password
field for the mysql database, I assume to get around this exact issue.
Is dovecot better in this regard?
--
Quis custodiet opsos custodes
