[exim-dev] [Bug 1733] New: ! inlist {<string1>}{<string2>} d…

Page principale
Supprimer ce message
Répondre à ce message
Auteur: admin
Date:  
À: exim-dev
Sujet: [exim-dev] [Bug 1733] New: ! inlist {<string1>}{<string2>} does not work
https://bugs.exim.org/show_bug.cgi?id=1733

            Bug ID: 1733
           Summary: ! inlist {<string1>}{<string2>} does not work
           Product: Exim
           Version: 4.80
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: String expansion
          Assignee: nigel@???
          Reporter: tony@???
                CC: exim-dev@???


The "!" negation operator does not work. The condition returns the same value
with and without the "!" infront of inlist operator:


where $received_protocol = bsmtp-sa, we get the following result:

root@ws1:/opt/spin3# exim -be -Mset 1a1pme-0001VG-Dj '${if inlist
{$received_protocol}{bsmtp-sa:local} {true}{false}}'
true
root@ws1:/opt/spin3# exim -be -Mset 1a1pme-0001VG-Dj '${if !inlist
{$received_protocol}{bsmtp-sa:local} {true}{false}}'
true

Running the above string testing produces the same values in both cases. This
is incorrect. The second test should return false due to the addition of "!",
but it returns true instead.

--
You are receiving this mail because:
You are on the CC list for the bug.