11 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Fwd: maildrop + ldap...
FromSent OnAttachments
Brad AskewJul 20, 2006 9:52 am 
Tony EarnshawJul 20, 2006 10:10 pm 
Chida NJul 20, 2006 11:56 pm 
Tony EarnshawJul 21, 2006 12:36 am 
Brad AskewJul 21, 2006 7:13 am 
Brad AskewJul 21, 2006 8:09 am 
Tony EarnshawJul 21, 2006 11:17 pm 
Brad AskewJul 26, 2006 6:43 am 
Brad AskewJul 26, 2006 6:44 am 
Tony EarnshawJul 26, 2006 10:01 pm 
Tony EarnshawJul 27, 2006 11:40 pm 
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] Fwd: maildrop + ldap how toActions...
From:Tony Earnshaw (teri@barlaeus.nl)
Date:Jul 27, 2006 11:40:03 pm
List:net.sourceforge.lists.courier-maildrop

to den 27.07.2006 Klokka 21:33 (-0500) skreiv Brad Askew:

[...]

From what I can tell, maildrop is getting the right directory from ldap, if you look at the results. The question is, why does maildrop insist on saying "changing to /home/vmail" (the wrong dir) when run as vmail, and when run as root, "changing to /home/vmail/domains" (the correct dir). I have the LDAP_MAILDIR in authldaprc set to /home/vmail/domains and it looks like maildrop is getting this attribute properly.

I tried to point out that this should be LDAP_HOMEDIR.

E.g. I have: LDAP_HOMEDIR mailMessageStore as well as: LDAP_MAILDIR mailMessageStore

So there is a way to force maildrop to use this? Can you show me an example of how you extract this information using the $HOME variable?

OU=`echo $HOME | cut -d/ -f4` UID=`echo $HOME | cut -d/ -f5` VHOME="/home/vmail/$OU/$UID"

[...]

to "$VHOME/Maildir"

--Tonni

-- Tony Earnshaw tonni at barlaeus.nl