------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1150 Todd Lyons <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Todd Lyons <[email protected]> 2012-10-31 20:08:57 --- I have one more use case where this ${addresses: } parsing isn't working properly. This case won't matter whether it's raw headers or not. In the below construction, I am extracting the first domain in the From header: # exim -be '${domain:${extract{1}{:}{${addresses:From: "[email protected]" <[email protected]>}}}}' progressivedesktoptraining.com Compared to this (not really invalid, but it is missing the quotes, which might make it fall afoul of RFC 2822, thus resulting in a blank return) From header: # exim -be '${domain:${extract{1}{:}{${addresses:From: [email protected] <[email protected]>}}}}' _a_blank_line_for_output_ The parser seems to be requiring the quotes to function properly, which might be bacause missing quotes make it fall afoul of RFC 2822, thus resulting in a blank return value (just guessing). Maybe a function to bring a line into RFC 2822 compliance would be useful (or impossible). I'm digging into the ${addresses: } parser now. -- Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
