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 17, 2007 2:15:37 am
List:net.sourceforge.lists.courier-maildrop

Giulio Fidente wrote:

Christian Affolter wrote:

Uhm I'm sorry, I forgot to mention that I'm using courier-authlib with a LDAP backend. The clue is that I've specified an absolute path for the maildir attribute:

homeDirectory: /var/mail maildir: /var/mail/example.org/user/Maildir/

thank you Christian...

...after your interesting post, I've leaved a relative path into the maildir attribute (because it's appended to the homedirectory parameter, so dynamically constructed by maildrop) and then placed the maildrop filter rules in the $HOME/.mailfilter file (home of the vmail user)... so we can have specific virtual rules for virtual users (such as the maildir creation)

about user's specific .mailfilter file, we can put the real $HOME directory into the LDAP homeDirectory attribute so the user's .mailfilter file is executed instead of the generic virtual users .mailfilter file and only in this case we have to create manually the $HOME directory

seems this way we have preserved all the functionality offered by maildrop and create can automatically the maildir (plus the maildir path)