On Wed, Jan 17, 2007 at 01:20:32AM +0100, mouss wrote:
Devin Rubia wrote:
Yes. $HOME should always be expected to exist for a number of good
reasons.
Now, seeing as you have this piece of goodness:
authldaprc:LDAP_HOMEDIR mailMessageStore
you should be golden. However, is you are doing something nasty like
having your Maildirs being created in your mail filters, then you get
what you deserve.
why?
See my discussion in the recent thread: "maildrop
and maildir creation: it can't, why?"
Unless I missed it, I guess you're talking about the performance issue
of doing the tests for all messages. If it's this, then it's
nitpicking. we can also speak about fork/exec-ing an MDA for each
message... (I am not advocating the creation of maildirs from
maildroprc, just pointing out the relativity of the "debate").
anyway, if it's just to avoid the `test` command, you can do it this way:
...
exception {
to $folder
}
maildirmake -f $folder $maildir
to $folder
...
Which would be better but doesn't maildrop create a mbox file if the
maildir doesn't exist? Also, what happens when the customer is over
quota or some other error interfere with delivery?
That said, it's not just the performance issues I'm concerned with.
It's just one more thing to go wrong and I believe it should be done on
the front end with account creation where I can deal with it right away
and not on the back end when the user starts receiving e-mail.
33 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Avoiding '/usr/bin/ma...
