------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1150 --- Comment #3 from Phil Pennock <[email protected]> 2011-09-08 10:54:05 --- Behaviour is correct. % mimehdr_string -d '=?iso-8859-2?Q?Kr=F3l=2C_Piotr?=' Król, Piotr The comma (hex 2C) separates list items, so once you've decoded the header, without quotes around the name, you have two items in the address-list, "Król" without an address, and "Piotr" with. Adding quotes automatically would break what the actual content is, for comparisons. I'm too tired to be definitive, but I'm not spotting a reasonable change to Exim's behaviour here, so I think that ${addresses:...} is only safe with the raw header. Perhaps there should be enough context propagation to have Exim warn if using non-raw headers inside something like ${addresses:..}, which ignores the MIME-encodable portions anyway? -- 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/ ##
