 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
12 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Maildrop & LDAP| From | Sent On | Attachments |
|---|---|---|
| Daniel L. Miller | Mar 25, 2007 5:25 pm | |
| Sam Varshavchik | Mar 25, 2007 5:50 pm | |
| Daniel L. Miller | Mar 27, 2007 1:20 pm | |
| Sam Varshavchik | Mar 27, 2007 3:32 pm | |
| Daniel L. Miller | Mar 28, 2007 3:13 am | |
| Sam Varshavchik | Mar 28, 2007 4:09 am | |
| Daniel L. Miller | Mar 28, 2007 10:30 pm | |
| Tony Earnshaw | Mar 29, 2007 12:23 am | |
| Daniel L. Miller | Mar 29, 2007 8:17 am | |
| Tony Earnshaw | Mar 29, 2007 8:38 am | |
| Daniel L. Miller | Mar 29, 2007 9:58 am | |
| Tony Earnshaw | Mar 29, 2007 10:40 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [maildropl] Maildrop & LDAP | Actions... |
|---|---|---|
| From: | Daniel L. Miller (dmil...@amfes.com) | |
| Date: | Mar 29, 2007 9:58:22 am | |
| List: | net.sourceforge.lists.courier-maildrop | |
Tony Earnshaw wrote:
Daniel L. Miller wrote, on 29. mar 2007 17:17:
[...]
. IS it possible to override?
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.
I may have to go there to accomplish what I want - just frustrating. Postfix and Dovecot handle it so elegantly with a minimum of configuration and data - I'd really like to have Maildrop do the same.
The thing is, Barlaeus needs LDAP for *so* many other things (like gdm logins, Postfix, Samba/Windows, you name it) that fuck Courier IMAP, fuck maildrop, fuck all authlib, if *they* don't work with LDAP, then they're banned to outer space.
For us, LDAP is the corner stone of all our administration. If other things don't work with LDAP, then they're useless. Use Dovecot if you like, Qmail, Exim, Cyrus, anything; if they work with your setup, well and good. But for us, Courier, Postfix, gdm, Samba are utterly dependent on LDAP and OpenLDAP is the be-all and end-all.
Luckily for us, Courier, Postfix, Samba, gdm, shell logins (like ssh and scp) all work perfectly with LDAP.
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 ;)
Best,
--Tonni
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.
-- Daniel