@Jeremy I think location is no problem since the address is successfully
extracted in most cases. Only this one problem, because the encoded
comma
Simple put that line in some file and try itself by -bem, eg:
Thank you Slavko so i will not bother list with that kind of question!
${address:} expansion is following RFC 2822... so maybe its ok and the
importance is $h_ should never be used with ${address:} because that
address expansion will decode it anyway??
Hard to say, headers can be broken (by mistake or by purpose)
in many ways
Also question about $h_ decoding, I dont remember if quoting is
required
if it is encoded like my exmaple. Is the example a invalid header
because
it needs quoting? Or is the problem that i'm using two unrelated steps
for
full parsing? ($h_ then ${address:})
Looking like RFC2822 requires quote when have comma in display-name but
doesn't talk about when encoding used on display-name so I still dont
know if its valid header. I will guess that it is required to decode
then parse as normal non-encoded rfc2822 header, thus this header is not
valid?
If that's right then using $h_ to do decoding then ${address:} to parse
and extract address is ok even though its two separate operations.
Otherwise, exim would need an operation that does both in once
(does ${address:} do decoding or only parsing?)
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
