On Thu, Nov 01, 2001 at 02:04:56PM -0500, Brian Clark wrote: > #define AUTH_PASSWD 0 > #define AUTH_SHADOW 0 > #define AUTH_PAM 1 > #define AUTH_PAM_USERPASS 0 > > First I used AUTH_MAN_USERPASS, but it failed, so I switched it to Did you install pam_userpass and stack it for popa3d? If not then it couldn't have worked. lftp ftp.openwall.com:/pub/projects/pam/modules> ls -l | grep pam_userpass-0.4 -rw-r--r-- 1 ftp ftp 3948 Jun 14 07:58 pam_userpass-0.4.tar.gz -rw-r--r-- 1 ftp ftp 331 Jun 14 07:59 pam_userpass-0.4.tar.gz.sign > AUTH_PAM and it appeared to go just fine. I could pop and receive mail. > > Later I noticed this while tailing the log to make sure everything was > OK: > > Nov 1 14:18:10 cla popa3d[15217]: connect from 123.456.789.10 (123.456.789.10) > Nov 1 14:18:10 cla PAM-warn[15217]: service: popa3d [on terminal: <unknown>] > Nov 1 14:18:10 cla PAM-warn[15217]: user: (uid=0) -> foo [remote: ?nobody@?nowhere] > Nov 1 14:18:10 cla PAM-warn[15217]: service: popa3d [on terminal: <unknown>] > Nov 1 14:18:10 cla PAM-warn[15217]: user: (uid=0) -> foo [remote: ?nobody@?nowhere] > Nov 1 14:18:10 cla popa3d[15217]: Authentication passed for foo You seem to have pam_warn somewhere in the PAM stack for popa3d. Why, do you need it? -- /sd
