My apologies then for not being more clear in my request. I've been a UNIX admin for a number of years, and quite understand the uid/gid concept. All of my previous experience, though, has been with local users having passwd accounts on the mail server.
Here's what I want to do: I have Postfix receive mail, then send it over to a particular Maildir for a user to find connecting to Courier POP3, authenticated via an LDAP database (for security and for single-signon reasons, no local passwd accounts). I have the POP3 authentication working. I have the correct Maildir to look in for the users (in my case at the moment, one particular test user). I'm trying to get Maildrop to pass from incoming Postfix over to the Maildir that Courier POP3 will look in. Eventually I want to put ClamAV and Spamassassin in-line, but I'm trying to start as simply as possible. I guess I am blocking on how to get Maildrop to verify that the particular rcpt to: address is valid, and how to tell Maildrop where to place the message under these circumstances. I'm under the impression that Courier and Maildrop would use a single local (passwd) user to own the various Maildirs, differentiating based on the particular mail recipient address in question, as in: /var/spool/courier/user1/ /var/spool/courier/user2/ /var/spool/courier/user3/ all owned by courier:courier, with user courier having home directory of /var/spool/courier. I'm not finding much documentation telling me how to make Maildrop look in the LDAP database to verify the user (if that's what is needed). Again, I apologize for not being clearer with my original request. On Thu, 2004-07-15 at 18:18, Sam Varshavchik wrote: > Eric N. Valor writes: > > > Seeing as how the ultimate recipient of the message DOES NOT HAVE A > > LOCAL UID/GID (as I've clearly stated a few times prior), > > There is no such thing as an “ultimate recipient”. When an E-mail is > received, it does not end up in a posession of some organic entity. It gets > delivered to a mailbox. That's where the E-mail is ultimately received. > And for the last couple of decades, each file on a UNIX/Posix system has an > associated userid and a groupid, which are defined as the owners of that > file or directory. > > > The documentation available on courier-mta.org (specifically the > > maildrop and makeuserdb pages) seem much more focussed on local users > > (those with UNIX accounts on the machine), hence my requests. > > The only difference between a “local” and a “virtual” user, is that the > specification of a local user originates from the same database that the > system's login(1), passwd(1), and many other utilities use to specify what > makes a user; and a “virtual” user is defined by some separate database. > > In both cases, however, the same exact data items define what a user is: > home directory, userid, and groupid (perhaps embellished with some optional > attributes, such as a personal name). For “local” users, this information > is typically found in the /etc/passwd file. The corresponding information > for “virtual” users comes from someplace else. In this case it's the userdb > file. In other cases it can be a LDAP directory, or a MySQL database. But > the basic information is identical in every way, in either case, the only > difference is where it comes from. -- Eric N. Valor [EMAIL PROTECTED] PGP Key 2048/1024 227B04CB Key Fingerprint = 766C CA15 0FFF E54B 2FEE C7D7 0F87 3AFB 227B 04CB : This Space Intentionally Left Blank :
signature.asc
Description: This is a digitally signed message part
