https://bugs.exim.org/show_bug.cgi?id=2861
Bug ID: 2861
Summary: ret=key for a non-lookup list search
Product: Exim
Version: 4.95
Hardware: x86
OS: Linux
Status: NEW
Severity: wishlist
Priority: low
Component: List matching
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
We have the ret=key option for single-key lookups, which affects the
secondary result when the primary, from the context the lookup is done in, is
the boolean success value.
It would be nice to be able to do the same when an explicit list is the
search source.
For example, a tainted IP string extracted from a message header could
be detainted by comparison against an explicit list of acceptable IPs:
${if match_ip,ret=key {$h_remote_ip:} {192.168.443.0/24} {$value}}
(That assumes a) the option syntax & placement b) using $value)
See also bug 452, which could be ret=full.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim
details at http://www.exim.org/ ##
