Victor Ustugov via Exim-users wrote on 26.05.2023 22:44:
> Jeremy Harris via Exim-users wrote on 26.05.2023 20:50:
>> On 26/05/2023 18:28, Victor Ustugov via Exim-users wrote:
>>> Please show me how you are going to extract the address without the
>>> regular expression from the header shown above.
>>
>> Why without? Using ${addresses: } does seem to work ok
>> for this example:
>>
>> /considering: ${addresses:=?utf-8?Q?My=20Bizness:=20Inc.?=
>> <charles@???>}
>> /considering: =?utf-8?Q?My=20Bizness:=20Inc.?= <charles@???>}
>> |-------text: =?utf-8?Q?My=20Bizness:=20Inc.?= <charles@???>
>> |considering: }
>> |--expanding: =?utf-8?Q?My=20Bizness:=20Inc.?= <charles@???>
>> \_____result: =?utf-8?Q?My=20Bizness:=20Inc.?= <charles@???>
>> |-----op-res: charles@???
>> |--expanding: ${addresses:=?utf-8?Q?My=20Bizness:=20Inc.?=
>> <charles@???>}
>> \_____result: charles@???
>
> I got an empty result. So i wrote about this example.
>
> # exim -be '${address:=?utf-8?Q?My=20Bizness:=20Inc.?=
> <charles@???>}'
Just now I noticed the difference.
You have used ${addresses:
I have used ${address:
It looks like ${addresses: considers there are two addresses in the
header with a colon and simply ignores the part of the header before the
colon.
Ok.
> test without colon:
>
> # exim -be '${address:=?utf-8?Q?My=20Bizness=20Inc.?=
> <charles@???>}'
> charles@???
>
>
> Tested on exim 4.95 and exim 4.96.
>
>
--
Best wishes Victor Ustugov
mailto:victor@corvax.kiev.ua
public GnuPG/PGP key:
https://victor.corvax.kiev.ua/corvax.asc
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
