[Postfixbuch-users] saslauthd stumm machen

[m.lindeman]

Hier meine /etc/pam.d/pop

auth sufficient pam_mysql.so user=mail passwd=xxxxxx host=localhost db=mail
table=accountuser usercolumn=username passwdcolumn=password crypt=1

account required pam_mysql.so user=mail passwd=xxxxx host=localhost db=mail
table=accountuser usercolumn=username passwdcolumn=password crypt=1


----- Original Message -----
From: "Andreas Winkelmann" <ml at awinkelmann.de>
To: <postfixbuch-users at listi.jpberlin.de>
Sent: Saturday, June 25, 2005 11:04 AM
Subject: Re: [Postfixbuch-users] saslauthd stumm machen


Am Saturday 25 June 2005 10:34 schrieb m.lindeman:

> Ich hab hier ein kleines Problem .
> Ich hab Postfix und Cyrus via saslauthd (pam) mit Auth gegen ein
> Mysql-Datenbank laufen. Funzt auch prächtig. Mein eigentiches Problem
> ist der Logfile Traffic, den mit der saslauthd verursacht.
>
> Für jede POP Abfrage hab ich folgenden eintrag in warn oder messages
> stehen:
>
> Jun 25 10:10:27 amigang saslauthd[1202]: pam_sm_authenticate called.
> Jun 25 10:10:27 amigang saslauthd[1202]: dbuser changed.
> Jun 25 10:10:27 amigang saslauthd[1202]: dbpasswd changed.
> Jun 25 10:10:27 amigang saslauthd[1202]: host changed.
> Jun 25 10:10:27 amigang saslauthd[1202]: database changed.
> Jun 25 10:10:27 amigang saslauthd[1202]: table changed.
> Jun 25 10:10:27 amigang saslauthd[1202]: usercolumn changed.
> Jun 25 10:10:27 amigang saslauthd[1202]: passwdcolumn changed.
> Jun 25 10:10:27 amigang saslauthd[1202]: crypt changed.
> Jun 25 10:10:27 amigang saslauthd[1202]: db_connect  called.
> Jun 25 10:10:27 amigang saslauthd[1202]: returning 0 .
> Jun 25 10:10:27 amigang saslauthd[1202]: db_checkpasswd called.
> Jun 25 10:10:27 amigang saslauthd[1202]: pam_mysql: where clause =
> Jun 25 10:10:27 amigang saslauthd[1202]: SELECT password FROM accountuser
> WHERE username='UserXXX' Jun 25 10:10:27 amigang saslauthd[1202]: sqlLog
> called.
> Jun 25 10:10:27 amigang saslauthd[1202]: pam_mysql: error: sqllog set but
> logtable not set Jun 25 10:10:27 amigang saslauthd[1202]: pam_mysql:
error:
> sqllog set but logmsgcolumn not set Jun 25 10:10:27 amigang
> saslauthd[1202]: pam_mysql: error: sqllog set but logusercolumn not set
Jun
> 25 10:10:27 amigang saslauthd[1202]: pam_mysql: error: sqllog set but
> loghostcolumn not set Jun 25 10:10:27 amigang saslauthd[1202]: pam_mysql:
> error: sqllog set but logtimecolumn not set Jun 25 10:10:27 amigang
> saslauthd[1202]: returning 0 .
> Jun 25 10:10:27 amigang saslauthd[1202]: returning 0.
> Jun 25 10:10:27 amigang saslauthd[1202]: pam_mysql: acct_mgmt called but
> not implemented. Dont panic though :)

> Wie krieg ich das Plappermaul zum schweigen? Die Logfiles sind so leider
> nicht arg brauchbar.

Zeig doch mal die pam-config (/etc/pam.d/pop*). Ich würde mich nicht wundern
dort was von "debug" zu lesen...

--
Andreas
--
_______________________________________________
Postfixbuch-users mailingliste
Heinlein Professional Linux Support GmbH

Postfixbuch-users at listi.jpberlin.de
http://listi.jpberlin.de/mailman/listinfo/postfixbuch-users