12 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Maildrop & LDAP
FromSent OnAttachments
Daniel L. MillerMar 25, 2007 5:25 pm 
Sam VarshavchikMar 25, 2007 5:50 pm 
Daniel L. MillerMar 27, 2007 1:20 pm 
Sam VarshavchikMar 27, 2007 3:32 pm 
Daniel L. MillerMar 28, 2007 3:13 am 
Sam VarshavchikMar 28, 2007 4:09 am 
Daniel L. MillerMar 28, 2007 10:30 pm 
Tony EarnshawMar 29, 2007 12:23 am 
Daniel L. MillerMar 29, 2007 8:17 am 
Tony EarnshawMar 29, 2007 8:38 am 
Daniel L. MillerMar 29, 2007 9:58 am 
Tony EarnshawMar 29, 2007 10:40 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 & LDAPActions...
From:Tony Earnshaw (ton@hetnet.nl)
Date:Mar 29, 2007 12:23:20 am
List:net.sourceforge.lists.courier-maildrop

Daniel L. Miller wrote, on 29. mar 2007 07:30:

[...]

Put domain.com/user in another LDAP attribute.

That's exactly what I DON'T want to do! Otherwise I'd have to define that mail directory for every virtual user - I want the system to do it automatically.

Is it possible for the global /etc/maildroprc to override the value of $HOME (prior to the initial chdir)? Or some other way of have the home directory specified via the command-line?

See maildropfilter (man 7 maildropfilter/maildropfilter.html) for environment variables.

FWIW the (Open)Ldap setup for Barlaeus Academy in Amsterdam adds new virtual users where all their LDAP attributes are derived from ASCII first-name middle name(s) last-name using a script, the first year or so combined shell and awk, latterly Perl. Amongst these are their $HOME and Maildir, used i.a. by authlib/maildrop. The whole process is 100% automated and all I needed from the administration was a file with a list of users, hundreds can be added at the same time. Same for removing users who have left.

Best,

--Tonni