10 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] maildrop and maildir ...
FromSent OnAttachments
Giulio FidenteJan 15, 2007 2:17 am 
Christian AffolterJan 15, 2007 2:55 am 
Christian AffolterJan 15, 2007 6:13 am 
Tony EarnshawJan 15, 2007 6:38 am 
Giulio FidenteJan 15, 2007 8:21 am 
Tony EarnshawJan 15, 2007 8:43 am 
Devin RubiaJan 15, 2007 9:22 am 
Giulio FidenteJan 15, 2007 9:40 am 
Giulio FidenteJan 15, 2007 10:54 am 
Giulio FidenteJan 17, 2007 2:15 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 and maildir creation: it can't, why?Actions...
From:Giulio Fidente (gfid@babel.it)
Date:Jan 15, 2007 9:40:26 am
List:net.sourceforge.lists.courier-maildrop

Devin Rubia wrote:

Indeed. Which is why you put the creation of $HOME and $DEFAULT into your account creation scripts where it belongs and _not_ in your mailfilters.

it's real, but we are speaking about maildrop not only mailfilter... infact the reason why I'm using maildrop is the quotacheck that maildrop/imapd/pop3d implements

Putting the $DEFAULT creation into your mailfilter means that the test will have a useful outcome when the account receives its very first e-mail but that test then gets invoked uselessly for the thousands upon thousands of e-mails that follow. If you are running a mail site of any size at all, then those disk accesses and processor cycles start to add up. Why not just get rid of it and do it the right way from the start?

absolutely exact, the postfix virtual infact seems a little bit slower than courier-maildrop... but it do the job, elsewhere infact someone thinks that a delivery agent should check and eventually create the maildir, but it should not check the quota in courier style

so?