12 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Unable to create a do...
FromSent OnAttachments
sim085Jun 17, 2009 7:39 am 
Sam VarshavchikJun 17, 2009 3:10 pm 
sim085Jun 17, 2009 3:22 pm 
Sam VarshavchikJun 17, 2009 3:53 pm 
sim085Jun 17, 2009 4:43 pm 
Sam VarshavchikJun 17, 2009 5:52 pm 
sim085Jun 18, 2009 1:13 am 
sim085Jun 18, 2009 2:37 am 
Sam VarshavchikJun 18, 2009 3:18 pm 
sim085Jun 19, 2009 12:45 am 
sim085Jun 19, 2009 7:13 am 
sim085Jun 20, 2009 12:35 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Unable to create a dot-lock at ...Actions...
From:sim085 (sim@hotmail.com)
Date:Jun 18, 2009 1:13:34 am
List:net.sourceforge.lists.courier-maildrop

Sam Varshavchik wrote:

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.

I set the uid and gid of every user equal to 5000 which represents the 'virtual' user, the same one used to start maildrop from postfix. At the moment I did not create a maildroprc under /etc/courier/ file because I do not want to define any rules (I just want to mail to be delivered to the right directories).

Sam Varshavchik wrote:

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.

What I can not understand is that if maildrop is being started by using the 'virtual' user then why can't maildrop access a directory on which the 'virtual' user does have rights (Considering that all uid and gid in the database point to this same user).

Sam Varshavchik wrote:

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.

This is what I have. MailDrop is started with the 'virtual' user and this user has access to the virtual directory under mail. Here is a list of rights on the virtual directory under mail (I used to command ls -l /var/spool/mail/ to get this result):

drwxr-sr-x 2 virtual virtual 4096 2009-06-17 16:43 virtual

I understand the point you are making about needing to be 'root' to be able to change to other users. However I do not need to change to any user since maildrop is started with the 'virtual' user and all accounts in my database are marked with the 'virtual' user uid and gid values (therefore the same).

------------------------------------------------------------------------------ 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