Devin Rubia wrote:

This is up to your configuration. the example I posted require that you define $maildir and $folder correctly. Clearly, if you define folder=/proc/acpi, things won't go right :)

if the maildir|folder was not present, it will be created. Then the second attempt will probably fail again, and you have the same result as without automatic creation. If errors don't happen often, then it's ok. Otherwise,

exception { to $folder } `test ...` ...

the difference here is that if the first attempt works, then you won't go through the `test ...` and second attempt.

now, there is also a second approach: assuming you support '+' addresses, you can put the maildir creation part in a block that is only exectued if mail is sent to user+welcome@domain, and make sure to send a welcome message to the new user (This may contain few recommendations and whatever you want). you can even have the command to replace the .mailfilter once the welcome message was delivered...

I didn't mean to discourage creation ahead of time (It is by far the best option), but there is nothing bad in having a second opportunity to perform this creation.

There are situations where this is desirable: - when one doesn't want to run remote privileged tasks, it is safer to let the MDA create the maildir for a virtual account. - one "quarantine" method uses a Junk folder if the recipient wants it...

Note that one still has to create the subdirectoy that will host the maildirs. If using a "deep" maildir layout, this would require an mkdir -p before the maildirmake. but one must be careful not to create random directories/files "imagined" by an attacker.