Re: [exim] issue with ${reduce and ${extract

On 2017-02-25 at 22:25 -0500, Phil Pennock wrote:
> 20fcb1e7be45177beca2d433f54260843cc7c2f6 is the first bad commit
> commit 20fcb1e7be45177beca2d433f54260843cc7c2f6

> At this point, I suspect that the issue is the current line 4974 of
> expand.c, where `lookup_value = NULL` while skipping, but if
> lookup_value was set _before_ skipping, this stomps on it.

Nope, because that's for ${run...} and we're not in that logic.

I'm perplexed. Either my bisect run-script is bad, or we are relying
upon a reset of `lookup_value = save_lookup` happening while skipping,
for good logic. I hope it's not the latter.

-Phil