Here's the debug for {${sg {$value}{\.list}{}}}fail}:
842757 postfork: delivery-local
842757 search_open: dsearch "/opt/lsoft/listserv/home"
842757 search_find: file="/opt/lsoft/listserv/home"
842757 key="johnnies-test-list-2.list" partial=-1 affix=NULL starflags=0
opts="ret=key,filter=file"
842757 LRU list:
842757 5/opt/lsoft/listserv/home
842757 End
842757 internal_search_find: file="/opt/lsoft/listserv/home"
842757 type=dsearch key="johnnies-test-list-2.list" opts="filter=file"
842757 file lookup required for johnnies-test-list-2.list
842757 in /opt/lsoft/listserv/home
842757 creating new cache entry
842757 lookup yielded: johnnies-test-list-2.list
842757 delivery-local forking for pipe-tpt-cmd
Here's the debug for {${sg {$value}{\\.list}{}}}fail}::
842792 postfork: delivery-local
842792 search_open: dsearch "/opt/lsoft/listserv/home"
842792 search_find: file="/opt/lsoft/listserv/home"
842792 key="johnnies-test-list-2.list" partial=-1 affix=NULL starflags=0
opts="ret=key,filter=file"
842792 LRU list:
842792 5/opt/lsoft/listserv/home
842792 End
842792 internal_search_find: file="/opt/lsoft/listserv/home"
842792 type=dsearch key="johnnies-test-list-2.list" opts="filter=file"
842792 file lookup required for johnnies-test-list-2.list
842792 in /opt/lsoft/listserv/home
842792 creating new cache entry
842792 lookup yielded: johnnies-test-list-2.list
842792 delivery-local forking for pipe-tpt-cmd
Here's the debug for {${sg {$value}{\.list\n}{}}}fail}, my attempt at
terminating the pattern, which does produce a different failure message:
842852 postfork: delivery-local
842852 search_open: dsearch "/opt/lsoft/listserv/home"
842852 search_find: file="/opt/lsoft/listserv/home"
842852 key="johnnies-test-list-2.list" partial=-1 affix=NULL starflags=0
opts="ret=key,filter=file"
842852 LRU list:
842852 5/opt/lsoft/listserv/home
842852 End
842852 internal_search_find: file="/opt/lsoft/listserv/home"
842852 type=dsearch key="johnnies-test-list-2.list" opts="filter=file"
842852 file lookup required for johnnies-test-list-2.list
842852 in /opt/lsoft/listserv/home
842852 creating new cache entry
842852 lookup yielded: johnnies-test-list-2.list
842852 delivery-local forking for pipe-tpt-cmd
And here's the debug for the successful {/opt/lsoft/listserv/home} {${sg
{$value}{[.]list}{}}}fail}:
842894 postfork: delivery-local
842894 search_open: dsearch "/opt/lsoft/listserv/home"
842894 search_find: file="/opt/lsoft/listserv/home"
842894 key="johnnies-test-list-2.list" partial=-1 affix=NULL starflags=0
opts="ret=key,filter=file"
842894 LRU list:
842894 5/opt/lsoft/listserv/home
842894 End
842894 internal_search_find: file="/opt/lsoft/listserv/home"
842894 type=dsearch key="johnnies-test-list-2.list" opts="filter=file"
842894 file lookup required for johnnies-test-list-2.list
842894 in /opt/lsoft/listserv/home
842894 creating new cache entry
842894 lookup yielded: johnnies-test-list-2.list
842894 delivery-local forking for pipe-tpt-cmd
I don't see a lot of difference in the logging, but I don't know any way to
make it more verbose.
On Thu, Dec 18, 2025 at 4:21 AM Jeremy Harris via Exim-users <
[email protected]> wrote:
> On 2025/12/17 8:30 PM, Johnnie Adams via Exim-users wrote:
> > I have made this lookup work by doing something which it seems I
> > shouldn't've had to do: I replaced the escaped period with a bracketed
> > period, thus: {${sg {$value}{[.]list}{}}}fail} . I tried other things
> > before this, like stripping the slash and doubling the slash, but none of
> > those worked. Should I report this as a bug, or is there something deep I
> > don't get?
> Look carefully at the debug for the (whole) expansion, using the
> backslashed period
> version. I think you'll find that the initial string-processing interprets
> the backslash, leaving just a period. This is then the regex, passed to
> the
> regex engine; and a period there is "any single char". Presumably that is
> not
> what you wanted, and you wanted to get the sequence "backslash, period" as
> the
> regex.
>
> The "doubled backslash" should have done that. I'd suggest looking at the
> debug for that case, to determine where in the processing sequence it does
> not result in what you expect.
> --
> 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/
>
--
John Adams
Senior Linux/Middleware Administrator | Information Technology Services
+1-501-916-3010 | [email protected] | http://ualr.edu/itservices
*UA Little Rock*
Reminder: IT Services will never ask for your password over the phone or
in an email. Always be suspicious of requests for personal information that
come via email, even from known contacts. For more information or to
report suspicious email, visit IT Security
<http://ualr.edu/itservices/security/>.
--
## 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/
