Re: [Exim] LDAP lookup in rewrite rule (Exim 3.33)

I see!
I had overlook that total.

Now I try to quote the colon somehow.
I tried this
"${lookup ldap {ldap":"//mailserv ...
and that
"${lookup ldap {ldap%3a//mailserv ...

In both cases Exim report no failure somewhere.
:-)
But nothing happens.
No ldap lookup is started.
(As I could see in the syslogs)
:-(
When I hand over this expressions to "exim -be" I receive the following error message:
Failed: lookup of "ldap":"//mailserv.fh-giessen.de/ou=groups,o=FH%20Giessen,c=DE?cn?sub?(mail=testlist*)" gave DEFER: malformed parameter setting precedes LDAP URL
or (for the second version)
Failed: lookup of "ldap%3a//mailserv.fh-giessen.de/ou=groups,o=FH%20Giessen,c=DE?cn?sub?(mail=testlist*)" gave DEFER: malformed parameter setting precedes LDAP URL

If I type in some random chosen symbols instead of the quoted colon I get the same error message from "exim -be"
and also nothing from Exim self.

So I think it would be the best to change the separator symbol from ':' to something other.
Is this possible?
I found no configuration option.
But maybe I overlook something (once again).

Sorry to annoy you.


- oliver



>> errors_to = ${lookup ldap {ldap://mailserv.fh-giessen.de/o=FH%20Giessen,c=DE?errorsTo?sub?(&(cn=$local_part)(objectclass=rfc822mailgroup))} {$value} {postmaster}}
>>
>> It's working perfectly for years (since Exim 2), without quotes.
>> So I was thinking I could port this expression simply to the header_rewrite setting in one of my mailman list transports.
>>
>> headers_rewrite = *@*fh.giessen.de "${lookup ldap {ldap://mailserv.fh-giessen.de/ou=groups,o=FH%20Giessen,c=DE?cn?sub?(mail=$local_part*)}{$value@???}fail}" t
>
>Doh!
>
>I've just woken up. headers_rewrite is a *list*. By default, the list
>separator is a colon. Does that give you enough clue? :-)