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 10:40:08 am
List:net.sourceforge.lists.courier-maildrop

Daniel L. Miller wrote, on 29. mar 2007 18:58:

[...]

As said, LDAP is the corner stone, everything else is purely incidental. Also luckily for us, Sam Varshavchik appreciates that. I've tried both Dovecot and Cyrus for IMAP and for us the just do not work. Courier does, happy marriage ;)

I'm not disputing any of that at all! My issue is not a problem with LDAP - but merely a stubborn refusal to put up with (as I see it) redundant data - whether hand entered or script generated. Given a root folder (/var/mail), a domain, and a username, my other services are able to build a path for mail handling. I just wanted to be able to use Maildrop in the same way - without explicitly defining a.mail delivery path for each user.

Ok.

(Aside: "shrug ...")

--Tonni

-- Tony Earnshaw Email: tonni at hetnet dot nl