Re: [Exim] possible conversion issue

Top Page
Delete this message
Reply to this message
Author: Philip Hazel
Date:  
To: John Jetmore
CC: exim-users
Subject: Re: [Exim] possible conversion issue
On Wed, 26 Feb 2003, John Jetmore wrote:

> I ran it through the convert4r4 script included with
> exim-4.12, and it changed the rule to this:
>
>   require_files = \
>       ${extract{3}{:}{\
>         ${lookup{$domain}dbmnz{/path/to/file.db}{$value}}\
>       }}/${substr_0_1::${lc::$local_part}}/${lc::$local_part}/vacation

>
> Note that it doubled the colons where they occurred in an expansion
> operator, but not where it was standing as an extraction delimeter.


It's very cautious, and not very clever. :-(

> Before you tell me to RTFM, I saw the "require_files" warning that was
> spit out on STDERR, I just thought maybe the script could be expanded to
> look for something like this. =)


Problem is, it would have to analyze the string in a lot of detail to
discover for sure that that particular colon was not an item separator
(and so had to be doubled). I suppose it could just guess that "{:}"
wasn't going to be a separator, but how common is this particular case
likely to be? In other words, is it worth my spending time on it instead
of on other things that need doing? My current feeling is that the
answer is "no", I'm afraid.

Thanks for taking time to raise the issue.

Philip

--
Philip Hazel            University of Cambridge Computing Service,
ph10@???      Cambridge, England. Phone: +44 1223 334714.