12 messages in net.sourceforge.lists.courier-maildrop[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:[maildropl] Maildrop & LDAPActions...
From:Daniel L. Miller (dmil@amfes.com)
Date:Mar 25, 2007 5:25:06 pm
List:net.sourceforge.lists.courier-maildrop

Hi!

I'm in the middle of migrating our mail server to a new configuration, and I've run across a stumbling block. I'm use Postfix for my MTA, and I'm storing the virtual user information in a LDAP database.

All user mail is supposed to be delivered to /var/mail/<domain>/<username>. My problem is how to tell maildrop to use the information in LDAP properly.

In Postfix, I can define the mail root as /var/mail, and I can use the LDAP filter to return a result of "/<domain>/<user>/" by just processing the mail field of "user@domain". So, at least for Postfix, I don't have to actually store each user's mail folder in the LDAP database - it gets generated from the mail address and the defined root folder.

Can I do this using Maildrop? If it makes any difference, I am running on an Ubuntu/Debian server.