Slavko via Exim-users wrote on 12.04.2023 22:38:
>>>> Hi, I have a variable to extract the email address in from header set like
>>>> this:
>>>>
>>>> ${lc:${address:$h_From:}}
>>>
>>> Header is valid, but after decoding it contains comma without
>>> qoutes, the comma is address separator and thus results in
>>> list of two "addresses", first without valid address, thus empty...
>>>
>>> Use raw header for address extracting -- $rh_From: that works
>>> for both, quoted and encoded content...
>>
>>
>> What about the colon without encoding?
>>
>> From: =?utf-8?Q?My=20Bizness:=20Inc.?= <char...@example.org>
>
> AFAIK colon have to be encoded, quote from by RFC 2047, section
> 5 (the From: and similar):
>
> characters that may be used in a "Q"-encoded 'encoded-word' is
> restricted to: <upper and lower case ASCII letters, decimal digits,
> "!", "*", "+", "-", "/", "=", and "_">
I'm not talking about what should be encoded, but about what can be
received in a real email from a spammer, some kind of script or
something like that.
--
Best wishes Victor Ustugov
mailto:vic...@corvax.kiev.ua
public GnuPG/PGP key: https://victor.corvax.kiev.ua/corvax.asc
--
## 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/
