2 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] maildrop concurrency
FromSent OnAttachments
Ed WildgooseMar 31, 2005 1:45 am 
Tony EarnshawMar 31, 2005 9:22 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] maildrop concurrencyActions...
From:Tony Earnshaw (ton@billy.demon.nl)
Date:Mar 31, 2005 9:22:44 am
List:net.sourceforge.lists.courier-maildrop

Ed Wildgoose:

How safe is maildrop with simultaneous deliveries?

Very. I've never had any "accidents" in many months of using maildrop on an 1150+ user site (low volume, though). There's no reason why there should be.

I have a vmail setup where all users get a single home dir ("/home/vmail/domain.com"), and then their maildirs are in subdirs of this single home dir.

More or less the same here.

What are the risks of letting postfix try to deliver 2 or more simultaneous virtual deliveries to this setup?

On my site. Postfix hands to dspam, which hands to maildrop. Postfix doesn't deliver the messages, maildrop does.

Note: I use a bunch of xfilter commands and otherwise flex maildrop quite a bit. So the question really is whether maildrop is creating any named temp files which are going to be clobbered by another simultaneous instance?

Each message that is created is unique and no xfilter rules I know of create conflicting tmp files (apart from transient files in subdirs of Maildir). Which would yours be?

Next question. If I have two domains in seperate home dirs THEN can I do multiple deliveries? ie if there are temp files getting clobbered then are they in /tmp or in the home dir?

maildrop runs as a separate instance for each delivery. AFAIK, unless you have quite specific xfilter rules in which you yourself create tmp files, none are created. And if you create your own tmp files, then you're responsible for seeing to it that they are unique.

--Tonni