fre, 2003-04-04 kl. 10:26 skrev Philip Hazel:
> > To be precisely: Our current problem is not LDAP data with pathological
> > characters to be matched, but local parts from nevelope senders with leading
> > white space (and worse) to be not matched. Eventually this would work with
> > the current ldap_quote_dn both ways, but ot should do so as implmenetation
> > of the RFC, not as a side affect, of course.
> As I am not an LDAP person, I am sitting on the sidelines waiting to see
> how this discussion turns out.
Well, it forced me to spend a useless morning reading really old and
somewhat newer x500 and ldap rfcs I'd really rather not know about
(since simple quote_ldap works for me with Relative Domain Components -
RDNs - like "cn=frigg+uid=xizzy" together with Exim 4.14.) At least I
know that rfc1485 from 1993 exists, is obsolete and was replaced by
rfc1779 from 1995, which essentially says the same, only a little more
of it.
If (Exim 4.14, Openldap 2.1.16, which is LDAPv3 with v2 allowed in my
setup) I do 'exim -bt xizzy', Exim knows it's really Frigg (an ldap user
and my pedigree Norwegian Forest, NFO) and where to send his mail.
Killing two birds and replying both to Marian's and your posting:
Marian's obviously tried and quote_ldap_dn doesn't work for him/her. But
quote_ldap_dn and quote_ldap do different things. So maybe he/she would
like to try again with quote_ldap and see what happens. I have no idea
what basic LDAP he/she is using, nor how it reacts to Exim's parsing.
Maybe other LDAP/Exim users on the list could comment; as I said, it
works fine for me as it is.
I look forward to the results.
Best,
Tony
--
Tony Earnshaw
e-post: tonni@???
www: http://www.billy.demon.nl
