[exim-dev] [Bug 2579] New: ${if def:recipients ...} should b…

Top Page
Delete this message
Reply to this message
Author: admin
Date:  
To: exim-dev
Subject: [exim-dev] [Bug 2579] New: ${if def:recipients ...} should behave as testing other variables that do not exist (yet)
https://bugs.exim.org/show_bug.cgi?id=2579

            Bug ID: 2579
           Summary: ${if def:recipients ...} should behave as testing
                    other variables that do not exist (yet)
           Product: Exim
           Version: 4.93
          Hardware: All
                OS: All
            Status: NEW
          Severity: bug
          Priority: medium
         Component: String expansion
          Assignee: unallocated@???
          Reporter: hs@???
                CC: exim-dev@???


Using `${if def:domain ...}` prevents from using $domain in places where it is
not (yet) set. But using `${if def:recipients ...}` fails with complaints about
an unknown variable in places where it is not (yet) available.

I believe, the behviour of `def:recipients` should match the behaviour of the
other def: tests. Doesn't matter whether $recipients is filled "on demand" or
nor. Because this is not obvious to the user.

Maybe returning "" (instead of NULL) from fn_recipients() in expand.c would do
it.
(I'm just running the testsuite, to see if it breaks other pieces.)

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