>>On Mon, 22 Apr 2002, Matthew Byng-Maddick wrote:
>
>> Actually this should probably be a FAQ item, shouldn't it? I found at least
>> three references just now, while searching the archives.
>
>It is on my list for adding to the Exim 4 FAQ. I don't know when I'll
>get round to it, however.
>
>But I have done something else. In 4.03 I improved convert4r4 to try to
>fix the problem:
>
>25. Updated convert4r4 to check for colons that look as if they are part of
> expansion items in require_files lists (e.g. ${lc:xxxx}). In Exim 3, the
> whole list was expanded before splitting up, but in Exim 4, the splitting
> happens first, so such colons must be doubled. The conversion script now
> doubles such colons, and outputs a warning message. The test for one of
> these colons is a match against "\$\{\w+:".
>
>--
>Philip Hazel University of Cambridge Computing Service,
>ph10@??? Cambridge, England. Phone: +44 1223 334714.
O.K. now I convert my config, so the there is no more problem within the
require lists. But first I have run your convert script of version 4.04. But
the script did not doubles such colons in my configuration.
But what is about the other error message while testing local delivery?
failed to expand condition"${if and { {! match{$header_X_Mailman}{'2.0.5'}}{!
match{$header_rpscan}{'by RP-MailScan'}}{ eq{Y}{${lookup mysql{SELECT
activate FROM aresponse WHERE domain LIKE '${quote_mysql:$domain}' AND
username LIKE '${quote_mysql:$local_part}'}{$value}{fail}}}}}{true}{false}}"
for autoresponse router: missing 2nd string in {} after "match"
Steffen Herold
