

![]() | 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: |
7 messages in net.sourceforge.lists.courier-maildrop[maildropl] Maildrop and LDAP authent...| From | Sent On | Attachments |
|---|---|---|
| Davide Ferrari | Feb 28, 2007 5:15 am | |
| Christian Affolter | Feb 28, 2007 5:41 am | |
| Davide Ferrari | Feb 28, 2007 6:30 am | |
| Christian Affolter | Feb 28, 2007 7:34 am | |
| Davide Ferrari | Feb 28, 2007 7:47 am | |
| Christian Affolter | Feb 28, 2007 8:12 am | |
| Davide Ferrari | Feb 28, 2007 9:03 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: | [maildropl] Maildrop and LDAP authentication | Actions... |
|---|---|---|
| From: | Davide Ferrari (davi...@atrapalo.com) | |
| Date: | Feb 28, 2007 5:15:59 am | |
| List: | net.sourceforge.lists.courier-maildrop | |
Hi
I know this is a FAQ but I cannot find out what happens in my scenario, and moreover I do not get exactly what doc says about this.
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. 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?
I'll try to clarify what happens to me, I have this in my postfix's main.cf:
virtual_mailbox_maps = ldap:accounts,ldap:alternate
accounts_server_host = ad.server accounts_search_base = ou=Users,dc=domain,dc=com accounts_query_filter = (&(objectClass=user)(mail=%s)(accountStatus=active)) accounts_result_attribute = mailMessageStore accounts_result_format = %s/Maildir/ accounts_scope = sub accounts_cache = yes accounts_bind = no accounts_version = 3
## Accounts with alternatemail emails
alternate_server_host = ad.server alternate_search_base = ou=Users,dc=domain,dc=com alternate_query_filter = (&(objectClass=user)(mailAddressAlias=%s) (accountStatus=active)) alternate_result_attribute = mailMessageStore alternate_result_format = %s/Maildir/ alternate_scope = sub alternate_cache = yes alternate_bind = no alternate_version = 3
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}
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.
May you give me some hints on what's happening there? I'm a bit confused currently...
Thanks in advance
-- Davide Ferrari System Administrator http://www.atrapalo.com







