sim085 writes:

There's nothing really to understand. maildrop retrieves the recipient's account home directory, uid, and gid, reads the mail filter, and carries out the instruction. maildrop is no different than any other process on the system. Its access to files and directories is governed by the same permissioning system that apply to all other processes, as far as file access goes. There's nothing mysterious about it, it's rather straightforward.

You tell me. Whatever you specified each mail account's uid and gid, in the mail account database you configured courier-authlib to use, that's what it is. But, as I just said, unless you're invoking maildrop as root, it's inapplicable, and you just said that you're not invoking maildrop as root, but as some kind of virtual user. As you know, a process that's not running as root cannot just magically change its userid or groupid to something else. That would break Unix security and the way that it worked for the last 40 years. So, if you are invoking maildrop as some other non-root user, it will necessary have to run using the given uid and gid, and that's who must have write permission on the mail directory.

------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects