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
For my tests I replaced "mail=$local_part*" by "mail=testlist*", cause I tested the string with "exim -be" too (successfully).
But in the Exim configuration it produced the described failure and Exim only accept it in quotes.
With "exim -be" there is no need for quoting the same is true for the "errors_to" option.
>If I had to guess I'd suspect you are using a macro and that the macro
>appears somewhere else as well...
Not knowingly :-)
Do you (principle) think it should work ?
Why I need no quotes in the "errors_to" option ?
Is the parser working there in a different way ?
- oliver
complete message from yesterday: >> headers_rewrite = *@*fh.giesssen.de "${lookup ldap {ldap://mailserv.fh-giessen.de/ou=groups,o=FH%20Giessen,c=DE?cn?sub?(mail=testlist*)}{$value@???}fail}" t
>>
>> I don't get a configuration error when I restart Exim, but when I try to deliver a mail by the use of this director
>> Exim writes the following error output to his mainlog:
>> 2002-04-10 08:49:50 16vBrD-000818-00 failed to open //mailserv.fh-giessen.de/ou=groups,o=FH%20Giessen,c=DE?cn?sub?(mail=testlist*)}{$value@???}fail}" when checking for Oliver.Egginger@??? in "//mailserv.fh-giessen.de/ou=groups,o=FH%20Giessen,c=DE?cn?sub?(mail=testlist*)}{$value@???}fail}"": No such file or directory >That doesn't make much sense. That phrase "when checking for" suggests
>that it is looking for an addres in an address list. Is the
>headers_rewrite setting the only place you have that string in your
>configuration?
>
>If I had to guess I'd suspect you are using a macro and that the macro
>appears somewhere else as well...
