On Wed, 1 Aug 2007, Magnus Holmgren wrote:
I' had trouble seeing the benefit of adding true and false as trivial
conditions, taking no arguments.
Note also that Exim expands left to right. You are asking for something
like {$something} to work as a condition if the expansion of $something
exim 4.66
assuming this:
set acl_c_pref_av_run = 1
set acl_m_msg_av_allowed = true
this:
condition = ${if and {{$acl_c_pref_av_run}
{$acl_m_msg_av_allowed}} {true}{false}}
is giving me the following error:
${if and {{$acl_c_pref_av_run}{$acl_m_msg_av_allowed}} {true}
{false}}:
On Wed, Aug 01, 2007 at 12:24:40PM -0500, Brian Blood wrote:
set acl_c_pref_av_run = 1
set acl_m_msg_av_allowed = true
this:
condition = ${if and {{$acl_c_pref_av_run}
{$acl_m_msg_av_allowed}} {true}{false}}
is giving me the following error:
${if and
On Aug 1, 2007, at 12:46 PM, Dean Brooks wrote:
Exim's expansion syntax is not a programming language.
Could have fooled me! :-)
IFs, ANDs, ORs, and now FORANY and FORALL, oh my!!
I sure as heck treat it/push it like a programming language.
It's just
a set of string expansion
On Wednesday 01 August 2007 20:34, Brian Blood wrote:
On Aug 1, 2007, at 12:46 PM, Dean Brooks wrote:
Certain condition= statements in ACL will accept values such as true
or 1 to indicate a positive value, but that is only after regular
string expansions have been performed on the value of
