mouss wrote:
[snip]
I see no postfix logs, nor any explanation of what problem you have.
Bloody hell, thought they were in the same logfile; my apologies. The
issue is that while IMAP works correctly authenticating against
authdaemond, any attempt I make to authenticate via SASL fails according
to postfix, yet succeeds according to authdaemond.
As to logs, here you go:
Dec 2 15:10:03 alcatraz postfix/smtpd[16120]: warning: where.i.sit:
address not listed for hostname HOSTNAME
Dec 2 15:10:03 alcatraz postfix/smtpd[16120]: connect from
unknown[where.i.sit]
Dec 2 15:10:06 alcatraz postfix/smtpd[16120]: warning: SASL
authentication failure: could not verify password
Dec 2 15:10:06 alcatraz postfix/smtpd[16120]: warning: SASL
authentication failure: Password verification failed
Dec 2 15:10:06 alcatraz postfix/smtpd[16120]: warning:
unknown[where.i.sit]: SASL PLAIN authentication failed: generic failure
Dec 2 15:10:06 alcatraz authdaemond: Authenticated: sysusername=<null>,
sysuserid=1008, sysgroupid=1008, homedir=/usr/local/virtual/,
address=...@sequestered.net, fullname=Jay Chandler,
maildir=sequestered.net/j...@sequestered.net/, quota=1024000000S,
options=<null>
Dec 2 15:10:06 alcatraz authdaemond: Authenticated:
clearpasswd=omgponies, passwd=$1$6dICANHAZPONIEZ?$Z1ySHXcliB8vx0jqwZ9Bp1
Dec 2 15:10:06 alcatraz postfix/smtpd[16120]: warning: SASL
authentication failure: could not verify password
Dec 2 15:10:06 alcatraz postfix/smtpd[16120]: warning:
unknown[where.i.sit]: SASL LOGIN authentication failed: generic failure
Dec 2 15:10:06 alcatraz authdaemond: Authenticated: sysusername=<null>,
sysuserid=1008, sysgroupid=1008, homedir=/usr/local/virtual/,
address=...@sequestered.net, fullname=Jay Chandler,
maildir=sequestered.net/j...@sequestered.net/, quota=1024000000S,
options=<null>
Dec 2 15:10:06 alcatraz authdaemond: Authenticated:
clearpasswd=omgponies, passwd=$1$6dICANHAZPONIEZ?$Z1ySHXcliB8vx0jqwZ9Bp1
Someone else reports the same issue at
http://lists.freebsd.org/pipermail/freebsd-questions/2009-September/205525.html
but there are no replies. I could switch over to dovecot and be done
with this, but I'd rather figure out what the underlying error is first...
-- Corey / KB1JWQ
