[exim-dev] [Bug 747] New: ${extract in the untaken branch of…

Top Page
Delete this message
Reply to this message
Author: Mike Cardwell
Date:  
To: exim-dev
Subject: [exim-dev] [Bug 747] New: ${extract in the untaken branch of a conditional
------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=747
           Summary: ${extract in the untaken branch of a conditional
           Product: Exim
           Version: 4.66
          Platform: Other
        OS/Version: Windows
            Status: NEW
          Severity: bug
          Priority: medium
         Component: ACLs
        AssignedTo: nigel@???
        ReportedBy: exim-users@???
                CC: exim-dev@???



As per the exim-users list:

================================================================================
# exim -be '${if match{1}{(1)}
                 {${extract {$1}{} {true} }}
                 {false} }'
true
# exim -be '${if match{1}{(2)}
                 {${extract {$1}{} {true} }}
                 {false} }'
Failed: first argument of "extract" must not be empty
#


Why does it fail the second time? Surely it should have just printed out
the word "false" ? The match doesn't succeed so surely the second time
the ${extract} shouldn't even be attempted?
================================================================================

Tony Finch's response was:

================================================================================
I think this is a bug in the way Exim handles ${extract in the untaken
branch of a conditional.
================================================================================

4.66 is the latest running version of exim I have to test this with.

Mike


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email