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:David Relson (rel@osagesoftware.com)
Date:Jun 22, 2004 2:27:47 pm
List:net.sourceforge.lists.courier-maildrop

On Tue, 22 Jun 2004 10:15:05 -0500 Ron Johnson wrote:

On Tue, 2004-06-22 at 12:29 +0200, Tony Earnshaw wrote:

tir, 22.06.2004 kl. 10.33 skrev Ron Johnson:

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.

I'll settle for putting individual logs in each user's home directory.

What about a world-writable directory like, say, /usr/local/data ?

Flies in the face of all that's sensible. Flies in the face of the whole concept of security. Why should it be necessary? Redesign maildrop's logging.

You want secure logging?

"I'll settle for putting individual logs in each user's home directory."

It works for me....

----------------------------------------------------------------- Ron Johnson, Jr. ron.@cox.net Jefferson, LA USA

Ron,

Individual logs leaves out two things that I, as sysadmin, consider important:

1 - Easily monitored logs (to check for problems, performance, whatever...)

2 - The ability to use filters and divert spam, viruses, etc to a central place, like the sysadmin.

David