On Sun, 2009-06-21 at 17:05 +0200, Rafał Radecki wrote:
> Yes, but in /usr/lib/sasl2/smtpd.conf i have:
>
> pwcheck_method: auxprop
> sql_engine: pgsql
> sql_user: postfix
> sql_passwd: postfix
> sql_hostnames: localhost
> sql_database: postfix
> sql_select: SELECT password FROM mailbox WHERE username='%...@%r'
> mech_list: login plain
> log_level: 4
>
> 2009/6/21 EASY steve.h...@digitalcertainty.co.uk
> <steve.h...@digitalcertainty.co.uk>
>
> On Sun, 2009-06-21 at 15:16 +0100, Steve wrote:
> > On Sun, 2009-06-21 at 15:58 +0200, Rafał Radecki wrote:
> > > I corrected my mistake but it doesn't help. Any other
> ideas?
> > What are the logs saying?
> >
>
> OFF LIST RESPONSE RECEIVED;
>
> >/var/log/maillog:
>
> >Jun 21 17:54:00 localhost postfix/smtpd[3091]: warning: SASL
> authentication problem: unable to open Berkeley
> db /etc/sasldb2: No such
> file or directory
> >Jun 21 17:54:00 localhost last message repeated 3 times
> >Jun 21 17:54:00 localhost postfix/smtpd[3091]: warning:
> localhost.localdomain[127.0.0.1]: SASL LOGIN authentication
> failed:
> authentication failure
> >Jun 21 17:55:04 localhost postfix/smtpd[3091]: lost
> connection after
> AUTH from localhost.localdomain[127.0.0.1]
>
>
> To my eyes: Berkeley db /etc/sasldb2 != PostgreSQL back end
>
>
Clearly it's looking at the wrong backend. Are there any more clues in
the syslog at all? Did you bounce everything after fixing the typo?
>
>
>
