18 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Re: replacing procmai...
FromSent OnAttachments
David RelsonJun 21, 2004 5:56 pm 
PollywogJun 21, 2004 6:20 pm 
Sam VarshavchikJun 21, 2004 7:01 pm 
PollywogJun 21, 2004 7:31 pm 
David RelsonJun 21, 2004 8:18 pm 
Robin Lynn FrankJun 21, 2004 9:05 pm 
Ron JohnsonJun 22, 2004 1:33 am 
Matthias AndreeJun 22, 2004 3:26 am 
David RelsonJun 22, 2004 5:04 am 
Tony EarnshawJun 22, 2004 5:08 am 
David RelsonJun 22, 2004 5:19 am 
Devin RubiaJun 22, 2004 7:34 am 
Ron JohnsonJun 22, 2004 8:15 am 
Robin Lynn FrankJun 22, 2004 8:25 am 
Matthias AndreeJun 22, 2004 8:29 am 
Nick SimicichJun 22, 2004 11:32 am 
David RelsonJun 22, 2004 2:27 pm 
Robin Lynn FrankJun 22, 2004 4:07 pm 
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] Re: replacing procmail with maildropActions...
From:Robin Lynn Frank (rlfr@paradigm-omega.com)
Date:Jun 21, 2004 9:05:54 pm
List:net.sourceforge.lists.courier-maildrop

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160

On Monday 21 June 2004 20:18, David Relson wrote:

On Mon, 21 Jun 2004 22:00:58 -0400

Sam Varshavchik wrote:

Pollywog writes:

I would try to determine the owner of the maildrop process,

The owner of the maildrop process is the userid the message is being delivered to.

Hi Sam,

What you say is consistent with my experiments, including use of strace to see what's happening. I've tried giving ownership "root:mail" to /var/log/maildrop.log and making my test user a member of group "mail", but that doesn't work either.

Is there any way for maildrop to have a single logfile for all users? As the sysadmin, that would be very useful for me (as well as the capability I had with procmail).

If maildrop's processes are owned by the user being delivered to, then it stands to reason that the only way you are going to be able to open a cntral og file is if it is world-writeable and that is not an option I'd care to use.

iD8DBQFA17ACo0pgX8xyW4YRA2HHAKDMZDZmXcHw0ZOtfa61g7LwgD2O5gCeNgN4 n/fpkQ2I1oY9ajxZ3rG+avo= =0QBz -----END PGP SIGNATURE-----