------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
http://www.exim.org/bugzilla/show_bug.cgi?id=458 Summary: Expansion condition: forall and/or forany Product: Exim Version: N/A Platform: All OS/Version: All Status: NEW Keywords: work:small Severity: wishlist Priority: medium Component: String expansion AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [email protected] Purpose: To do something useful with $recipients without resorting to filters or perl, and to process the results of DKIM signature verification in the future. Suggested syntax: forany {<string1>}{<string2>} or, perhaps more analogous to and and or, forany {<string1>}{<cond1>} string1 is expanded and treated as a list. Each item in the list is, in turn, put in a variable (either $value or a new one called e.g. $item). Then string2 is expanded or cond1 evaluated. If the result for any item true, forany returns true and no more evaluations are performed. If the result is false for all items, forany returns false. The opposite holds for forall (forall {list}{cond} is the same as !forany {list}{!cond}). To be useful, forall/forany must be able to handle different kinds of lists (different separators and separators within quoted strings not to be treated as separators). But that is better accomplished by improving the generic list-handling functions. -- Configure bugmail: http://www.exim.org/bugzilla/userprefs.cgi?tab=email -- ## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
