On Mon, May 27, 2002 at 02:08:56PM -0700, Chuck Yerkes wrote: | 1) As mail comes in, I'd like to be lookup the username into a | make (ldap eventually, but .db for now) to get where her spool | is. So "lisa" would return either /var/spool/$COMPANY/lisa" | or, for better security, just "$COMPANY/lisa" ($COMPANY would | just be the company she is with). | | Goal: This lets me separate users by some logical groupings, cause I'm | hosting a few people. | Eventually, perhaps a $PREFIX based on which interface they attach to...
Assuming you have IP addresses to spare, you could do this by making Qpopper listen on multiple addresses, and have each instance load its own config file that defines spool-dir as needed. For example: 192.168.0.1 -> load /etc/pop-company1.conf -> set spool-dir = "company1" 192.168.0.2 -> load /etc/pop-company2.conf -> set spool-dir = "company2" | 2) Replace the getpw*() calls with a "popper_getpwent()" which will | first to a real getpw*(), then will call my own. So if the user | doesn't exist in /etc/passwd but I have them in /etc/popper.passwd | it WILL work. (LDAP also a goal). | Goal: Let me have pop-only users that don't have "real" accounts. | Machine has no PAM, so that's out, unfo (NetBSD and OpenBSD). This would be quite useful. However, you'll still need some magic to make your MTA deliver to a spool for a non-existent user. -James
