20 messages in net.sourceforge.lists.courier-usersRE: [courier-users] deleting messages...
FromSent OnAttachments
Mitch (WebCob)Jan 13, 2004 11:47 am 
Chris PetersenJan 13, 2004 1:43 pm 
Mitch (WebCob)Jan 13, 2004 2:09 pm 
Mitch (WebCob)Jan 13, 2004 11:38 pm 
Jeff JansenJan 14, 2004 1:24 am 
Mitch (WebCob)Jan 14, 2004 1:51 am 
Jon NelsonJan 14, 2004 5:38 am 
Troy BenjegerdesJan 14, 2004 8:24 am 
Jon NelsonJan 14, 2004 8:32 am 
Mitch (WebCob)Jan 14, 2004 11:29 am 
Jon NelsonJan 14, 2004 12:19 pm 
Mitch (WebCob)Jan 14, 2004 1:11 pm 
Jon NelsonJan 14, 2004 1:18 pm 
Mitch (WebCob)Jan 14, 2004 1:43 pm 
Jon NelsonJan 14, 2004 2:05 pm 
Mitch (WebCob)Jan 14, 2004 2:42 pm 
Sam VarshavchikJan 14, 2004 3:23 pm 
Mitch (WebCob)Jan 14, 2004 3:53 pm 
Jon NelsonJan 14, 2004 4:13 pm 
Jon NelsonJan 14, 2004 4:20 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: [courier-users] deleting messages reviewed...Actions...
From:Jon Nelson (jnel@jamponi.net)
Date:Jan 14, 2004 1:18:42 pm
List:net.sourceforge.lists.courier-users

On Wed, 14 Jan 2004, Mitch \(WebCob\) wrote:

You were against a "special case" patch for dev-null - which I agree is not needed now that I know the "one true way"(tm)

What I was pondering was a general patch which would make communicating with filter daemons (listening on file sockets or char devices) possible - and that would be to skip the locking in these cases where it has no point - it would have the side effect of allowing /dev/null to work, but that's not my point here... It would allow direct delivery to things like spamd without a stub spamc program to manage the socket.

And maildrop does some kind of locking (flock?)? I apologize, I'm coming into this discussion at the end. Please describe what you are trying to do (specifically), what you think the problem is, what maildrop's behavior is, etc...