[exim-dev] [Bug 458] Various expansion items and conditions …

Top Page
Delete this message
Reply to this message
Author: bug458
Date:  
To: exim-dev
Old-Topics: [exim-dev] [Bug 458] New: Expansion condition: forall and/or forany
Subject: [exim-dev] [Bug 458] Various expansion items and conditions iterating over lists
------- 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





------- Comment #19 from kjetilho@??? 2007-02-11 03:46 -------
I like map/filter/reduce very much!

(In reply to comment #18)

>     {${map {${addresses:$recipients}}


so ${addresses:} will accept space delimited addresses? looks like it from a
quick glance at the patch. I'm a bit worried about syntactically incorrect
headers being misparsed, e.g.:

To: someone@??? <someone@???>

this is a violation of RFC 2821 (a display name can't be a mail address without
quoting), but the code will parse $h_To: as a list of two addresses. I would
prefer it if ${addresses explicitly used commas to separate the elements.

ideally, Exim should be able to see that $recipients is used in a list context
(to use Perl terminology) so that you don't need the extra call. or perhaps

${map {< $recipients} ...}

to tell ${map that the list is space separated, or do we need a ${split for
this? btw, ${join can be implemented trivially with ${reduce :-)

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