Hi,

I've just compiled maildrop 1.5.3 with ldap support and I'm having problems 'cause my LDAP base contains spaces.

I configure maildrop's ldap.conf to use binddn 'cn=Admin,ou=Service,o=My Organization'

when I invoke maildrop manually maildrop -d us...@mydomain.com

I get maildrop: signal 0x0B

However, browsing the ldap log I see it's trying to bind using a wrong dn (log lines manually folded):

Jul 11 16:44:19 dedos slapd[4355]: conn=1937 fd=15 \ ACCEPT from IP=127.0.0.1:4622 (IP=0.0.0.0:389) Jul 11 16:44:19 dedos slapd[4361]: bind: invalid dn \ ('cn=Admin,ou=Service,o=My) Jul 11 16:44:19 dedos slapd[4361]: conn=1937 op=0 \ RESULT tag=97 err=34 text=invalid DN Jul 11 16:44:19 dedos slapd[4355]: conn=1937 fd=15 closed

Now, no matter what quotes I use (or no quote at all) in the ldap.conf line, it doesn't work:

With: binddn 'cn=Admin,ou=Service,o=My Organization' I get: Jul 11 16:44:19 dedos slapd[4361]: bind: invalid dn \ ('cn=Admin,ou=Service,o=My)

With: binddn "cn=Admin,ou=Service,o=My Organization" I get: Jul 11 16:44:19 dedos slapd[4361]: bind: invalid dn \ ("cn=Admin,ou=Service,o=My)

With: binddn cn=Admin,ou=Service,o=My Organization I get: Jul 11 16:44:19 dedos slapd[4361]: bind: invalid dn \ ("cn=Admin,ou=Service,o=My")

(note, unlike the first and second ones, the last one has opening _and_ closing quotes, but none of them gets the " Organization" part...)

I tried using "\ " and "%20" to no avail (I didn't expected that would work, anyway).

I _can't_ change the base LDAP tree since it is used in lots of places (by widely different software which never had a problem with embedded spaces), is there a way that maildrop be able to understand a blank space within a dn?

Any ideas?

----------------------------------------------------------- I.R.S.: We've got what it takes to take what you've got!