Hello Dan, here you go:
/etc/postfix/sasl/smtpd.conf pwcheck_method: saslauthd mech_list: plain login allow_plaintext: true auxprop_plugin: sql sql_engine: mysql sql_hostnames: 127.0.0.1 sql_user: xxx sql_passwd: xxx sql_database: xxx sql_select: select password from mail_user where email = '%u@%r' /etc/pam.d/smtp and /etc/pam.d/smtpd: auth required pam_mysql.so user=xxx passwd=xxx host=127.0.0.1 db=xxx table=mail_user usercolumn=email passwdcolumn=password crypt=1 account sufficient pam_mysql.so user=xxx passwd=xxx host=127.0.0.1 db=xxx table=mail_user usercolumn=email passwdcolumn=password crypt=1 I am not quite sure which one is used by postfix... > My belief is that this type of issue is due to a memory leak in the > specific PAM module, or due to the way saslauthd uses pam - it only uses > the auth and account facilities and not the session or password facilities, > which may prevent the module from performing it's memory cleanup. So does the work around work anyway? It seems that I not fully understand what is going on. Anyway, if I restart saslauthd after the problem is there everything works right away like there was never a problem. Cheers, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
