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:Tony Earnshaw (ton@hetnet.nl)
Date:Jan 15, 2007 8:43:28 am
List:net.sourceforge.lists.courier-maildrop

Giulio Fidente wrote:

Uhmmm ... maildrop can create both the user's (even virtual users') $HOME/Maildir/ and all subdirectories; the only directory it cannot create is the user's $HOME directory.

`test -d $HOME/Maildir/` if( $RETURNCODE == 1 ) { `/usr/bin/maildirmake $HOME/Maildir/` }

thank you tony, anyway I think the question remains.

for example, in a standard environment with only posix accounts the 'Maildir' directory is strictly related to the email messaging system, the $HOME directory is not and most probably already exist... so the courier-maildrop works in the right way

but in a larger environment with multiple domains and eventually separate stores, the accounts will be not posix but virtual and even if the courier-maildrop contemplates this case, it doesn't fit well... simply because if the $HOME directory is not already present, it does not deliver the email

No indeed. The $HOME directory has to exist before $HOME/Maildir/ can be created and that is why God invented Unix and shell scripting (the devil Perl), just to take care of such eventualities.

--Tonni