------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://www.exim.org/bugzilla/show_bug.cgi?id=452
------- Comment #1 from ph10@??? 2007-02-05 14:46 -------
A brief look at this shows that it is quite a lot of work. For a start, a
decision is needed as to whether to use a single variable such as
$list_matched_item, or to have separate variables for each case that can match
in one of these lists: host,domain,local_part,ip,address,sender. A way of
ensuring that the right variable is set at the bottom level when there are
nested (named) lists is needed - and not reset at the top level. The issue of
when to reset the variables must be addressed. None of the
${host,domain,local_part,sender}_data variables are currently set in string
expansions - they are set only in routers and ACLs. If these and the new
variables are to be available after ${if match_xxx then not only must the
values be in the right type of memory, but we also need to think about scope
and when they are reset, especially in connection with nested ${if items.
Finally, a check is needed to ensure that it all works with cached lookups. //
Sadly, what looks like a straightforward upgrade is much messier than it seems,
because of the way the existing implementation is done. At the moment,
therefore, I am just going to leave this waiting on the list.
--
Configure bugmail:
http://www.exim.org/bugzilla/userprefs.cgi?tab=email
