Re: [exim] ${address: foo(comment)@bar.org}

Top Page
Delete this message
Reply to this message
Author: Jasen Betts
Date:  
To: exim-users
Subject: Re: [exim] ${address: foo(comment)@bar.org}
On 2019-02-15, Jasen Betts via Exim-users <exim-users@???> wrote:
> On 2019-02-14, Jeremy Harris via Exim-users <exim-users@???> wrote:
>> Summary:
>>
>> On 13/02/2019 05:41, Jasen Betts via Exim-users wrote:
>>> Should it be doing that?
>> They should be stripped.
>>
>>> (I could write a patch if this is a bug)
>>
>> That would be very useful.


> I'll also have a look at the code behind "exim -t" email header parsing,


it turned out that the exim -t header passing works correctly but the
expansion code was misusing that parsing code. the fixed code is actually
shorter that the old code.

I have submitted a patch:

https://bugs.exim.org/show_bug.cgi?id=2375

I'm not sure if I should be free()ing "t" in that code - the old code
wasn't. I guess exim will clean that up automatically.

--
When I tried casting out nines I made a hash of it.