7 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Maildrop and LDAP aut...
FromSent OnAttachments
Davide FerrariFeb 28, 2007 5:15 am 
Christian AffolterFeb 28, 2007 5:41 am 
Davide FerrariFeb 28, 2007 6:30 am 
Christian AffolterFeb 28, 2007 7:34 am 
Davide FerrariFeb 28, 2007 7:47 am 
Christian AffolterFeb 28, 2007 8:12 am 
Davide FerrariFeb 28, 2007 9:03 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 and LDAP authenticationActions...
From:Christian Affolter (c.af@stepping-stone.ch)
Date:Feb 28, 2007 5:41:37 am
List:net.sourceforge.lists.courier-maildrop

Hi

I have maildrop 2.0.2 installed as standalone with authlib and ldap enabled (on Gentoo Linux). I want to integrate maildrop with postfix 2.2.10 and I have read README.postfix but I don't understand where can I customize what maildrop is looking for in the LDAP tree.

You'll have to configure your courier-authlib, so that it uses the LDAP authentication module. Have a look at http://www.courier-mta.org/authlib/README_authlib.html (authldap authentication module).

I'm using as LDAP backend ActiveDirectory on Windows2003R2, and I've added to every user a few attributes to integrate well with my existing postfix+ldap configuration. But why is this readme talking about specific LDAP schemas?

with virtual(8) MDA everything works smoothly: first it looks for the desired address in the "mail" attribute, if it doesn't exists, looks for it in the "mailAddressAlias" field, and delivers to $mailMessagestore/Maildir.

I use this technique to, well you may know, have an user receiving mails to another mail address (not his/her main address).

Changing MDA to maildrop, with this in master.cf

maildrop unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/bin/maildrop -d ${user}@${nexthop} ${recipient} ${user} ${nexthop} ${sender}

I'm simply using: maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient}

delivery if the destination address is present in account part (so it's in the LDAP "mail" field) works perfectly with maildrop as well, but trying to use the "alternate" part, it throws me the typical "Command output: Invalid user" error.

Again, how does the LDAP configuration for courier-authlib (authldaprc) looks like?

regards Chris