Thanks Jeremy for clarifying. I've since resolved the problem by writing a log filter tool which intercepts all the root-level 'Considering: ...' log entries, looks up the raw expansion expressions in the (post-preprocessing) config, then patches in the lvalue names and config line numbers just above them.
Cheers David On Sun, 17 Sept 2023 at 07:02, Jeremy Harris via Exim-users < [email protected]> wrote: > On 16/09/2023 00:26, David McNab via Exim-users wrote: > > However, the log entries for expansions don't seem to show lvalues. > > (assuming you mean "debug output"; -d does not write to the > Exim mainlog, paniclog or message-log) > > That's because an expansion is only the bit starting with the $. > It is not the entire ACL line or option line; there is no lvalue > as far as the expansion goes. > > What you're asking for is more detail on what causes the expansion, > I think. To cover every possible place would be lots of > codework; nobody's put in the effort so far. > > > Which specific foo= ? > -- > Cheers, > Jeremy > > > -- > ## subscription configuration (requires account): > ## > https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ > ## unsubscribe (doesn't require an account): > ## [email protected] > ## Exim details at http://www.exim.org/ > ## Please use the Wiki with this list - http://wiki.exim.org/ > -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## [email protected] ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
