------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=672 Summary: strict_acl_vars failures in the unused half of a conditional Product: Exim Version: 4.69 Platform: x86 OS/Version: Linux Status: NEW Severity: bug Priority: medium Component: String expansion AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [email protected] Created an attachment (id=232) --> (http://bugs.exim.org/attachment.cgi?id=232) Patch to disable strict_acl_vars when expanding the unused half of a conditional Both of these will give an unknown variable error instead of the expected "ok" when strict_acl_vars is set: ${if ={0}{1} {$acl_m_unset_variable}{ok}} ${if ={0}{0} {ok}{$acl_m_unset_variable}} It is counterintuitive that the non-matching result of a conditional can still cause unknown variable errors when that half has no other side effects. It also renders the "isset" conditional in my patch to bug #474 rather useless. The attached patch fixes the issue by turning off strict_acl_vars when expanding the non-matching result. -- Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email -- ## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
