Hi!

I've managed to (ab)use maildorp for maildir creation. I've specified a directory which is always accessible as the users mail home dir (I'm using the same for every user). This prevents early chdir failures so that the global maildroprc script gets executed nonetheless.

The global maildroprc script then checks for the presence of the users maildir ($DEFAULT inside the script). If the maildir doesn't exists, a bash script gets called, which creates a fresh maildir.

However with the above solution you loose the ability to process user defined maildrop scripts (located in $HOME/.mailfilter). To bypass this issue, my global maildroprc includes the users .mailfilter in the last step.

All required values for a maildir creations are present within the various maildroprc variables and especially the combination of the 'test -d' command and the $RETURNCODE variable. See: http://www.courier-mta.org/maildrop/?maildropfilter.html

But keep in mind, that maildrop wasn't designed for maildir creation and that the above solution abuses the intended purpose of the mail home dir and maildir. Anyway it works quite well for my needs.

I think this has been discussed more than once in the past ;)

Hope this helps!

regards Chris