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:Pollywog (lin@shadypond.com)
Date:Jun 21, 2004 7:31:38 pm
List:net.sourceforge.lists.courier-maildrop

On 06/22/2004 02:00 am, 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.

That is a similar problem I had when I set up Procmail to deliver mail on a system using Postfix with Cyrus IMAP. The systemwide part worked fine, but I had problems with user's procmailrc's and had to make them all owned cyrus:<username> IIRC and readable by cyrus and the user. It was more trouble than it was worth.