Thank you for the quick update.
Unfortunately "inlisti" does not match against wildcard records like
"*@gmail.com" so we had to change our condition.
On Wed, Mar 30, 2016 at 9:22 PM, Jeremy Harris <jgh@???> wrote:
> On 30/03/16 17:53, Konstantin wrote:
>> I have a condition which seem worked on old exim server version 4.72.
>>
>> condition = ${if match_address{$local_part@$domain}{
>> ${lookup{$sender_address}wildlsearch{/etc/exim/allow_senders}} }
>> {yes}{no} }
>>
>> Content of /etc/exim/allow_senders
>> sender@???: *@gmail.com : *@yahoo.com
>> ...
>> sender2@???: rcpt1@??? : *@yahoo.com : rcpt2@???
>>
>> On the new exim version 4.85 it is failed with error:
>> Failed: missing or misplaced { or }
>>
>> Can someone please help me to find where is the problem in this rule.
>
>
> http://exim.org/exim-html-current/doc/html/spec_html/ch-string_expansions.html#SECTexpcond
>
> on match_address (via match_local_part)
>
> "Note that <string2> is not itself subject to string expansion".
>
> (the usage was a common security problem). Consider using "inlisti"
> or "inlist" instead. Since 4.77.
> --
> Cheers,
> Jeremy
>
>
> --
> ## List details at https://lists.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/
--
This message was delivered using 100% recycled electrons.
