Re: Postfix + SASL + PAM

4 msg	MX sequence question
2 msg	assistance with a filter rule
1 msg	error on list
7 msg	Why is this valid?
2 msg	Address Verification

Postfix + SASL + PAM
\ Eddy Ilg (29 Jun 2007)
. \ Andreas Winkelmann (30 Jun 2007)

4 msg	Automatically ban a server after too many 550 R...
4 msg	PDF spam - how to stop
1 msg	Procmail in master.cf
2 msg	Mail delivered only localy
3 msg	postfix parameters given to maildrop
5 msg	how to report a possible spammer
7 msg	Problems with SPAM
5 msg	can't get postfixadmin to work with postfix
4 msg	confusion with postfix+spamassassin+amavisd-new
2 msg	Pleae HELP [warning: dict_ldap_open:]
2 msg	duplicated messages
10 msg	Upgrading From 2.3.6
4 msg	lost connection after DATA
4 msg	Making postfix hand old deferred messages somew...

Subject:	Re: Postfix + SASL + PAM
Group:	Postfix-users
From:	Andreas Winkelmann
Date:	30 Jun 2007

On Friday 29 June 2007 18:05, Eddy Ilg wrote:

> thanks to this list I now have postfix talking to saslauthd.
>
> My saslauthd shall authenticate via pam_mysql. Therefore I created the
> file /etc/pam.d/smtp as follows:

> auth required pam_mysql.so user=maildaemon host=xy passwd=xxxxxxxx
> db=dexter-sys table=mbs usercolumn=username passwdcolumn=password crypt=0

The accout-Stack is missing. saslauthd uses auth and account.

> The query is actually run on server xy (checked the mysql log) and it is
> correct. But I keep getting the following in /var/log/auth.log:
>
> Jun 29 18:02:36 saslauthd[17541]: rel_accept_lock : released accept lock
> Jun 29 18:02:36 saslauthd[17542]: get_accept_lock : acquired accept lock
> Jun 29 18:02:36 saslauthd[17541]: (pam_unix) could not identify user
> (from getpwnam(mail-client-1))
> Jun 29 18:02:36 saslauthd[17541]: DEBUG: auth_pam: pam_acct_mgmt failed:
> User not known to the underlying authentication module
> Jun 29 18:02:37 saslauthd[17541]: do_auth : auth failure:
> [user=mail-client-1] [service=smtp] [realm=] [mech=pam] [reason=PAM acct
> error]
>
> The thing I'm most concerned about is the pam_unix line. Where does that
> come from?
>
> Any ideas what I'm missing? How could I turn on more sasl/pam debugging?

--
Andreas