On 13/02/2019 12:39, Mike Brudenell via Exim-users wrote: >>> exim -v -be '${address:Pete(A nice \) chap) <pete@???>}'
>>> gives the empty string, suggesting Exim thinks it's a parse error
>>
>> You'd be needing to double the backslash, for the string-parsing
>> stage of the 822 address there, to actually get a backslash as
>> part of the 822 address. Do that, and it's fine and gets
>> the right result for the expansion.
>>
>
> Umm… That address string is taken straight out of the RFC
Yes, but irrelevant.
> Or would Exim, on encountering that particular From header,
But you're not dealing with a From: header. You're only doing
a ${address:foo} expansion with a literal string for foo,
in this test. And "foo" gets string-processed, which means
backslash-interpretation for escaping.
--
Cheers,
Jeremy
