I compiled qpopper 4.0.4 with the following options:
/configure --disable-check-pw-max --enable-log-login --enable-shy --with-pam I also changed the default mailbox path to /mail/users, but I can't remember the switch right now :-) For pam.d auth, I created the following /etc/pam.d/pop3 file: auth required /lib/security/pam_userdb.so db=/etc/mail/passwords account required /lib/security/pam_userdb.so db=/etc/mail/passwords The db was build with the following command: db_load -T -t hash -f passwords.txt /etc/mail/passwords.db The passwords.txt contained the username on line 1 and the password on line 2 etc. Incoming mails are saved to /mail/users via procmail. That works fine so far If I build the db with a user:pass combo that is a real user (also in /etc/passwd), then the authentication works. Otherwise, it doesn't. And now I'm wondering what the userdb.so module is good for if the users need to be in /etc/passwd. All I'm trying to do it getting the mails saved in [EMAIL PROTECTED] (what would work with sendmail/procmail). But how can I make qpopper (or pam.d) accept users with the username [EMAIL PROTECTED] and the pass foobar (without creating real accounts for them). Any suggestions? You'd make me really happy, cuz I'm working on this for quite a couple of days now. (btw, any other solution/approch for the virtual user hosting with qpopper is also welcome (exept the mysql.patch, because it doesn't seem to work for me) Thanks Sven
