Thanks for doing some testing around the quotes, was that with using /usr/bin/bash?
Also the lead I had was the changelog entry from upstream:
JH/24 The ${run} expansion item now expands its command string elements after
splitting. Previously it was before; the new ordering makes handling
zero-length arguments simpler. The old ordering can be obtained by
appending a new option "preexpand", after a comma, to the "run".
So I tried using ,preexpand to hopefully get it to work and unfortunately just see a parsing error now, similar to [0].
Thanks for doing some testing around the quotes, was that with using /usr/bin/bash?
Also the lead I had was the changelog entry from upstream:
JH/24 The ${run} expansion item now expands its command string elements after
splitting. Previously it was before; the new ordering makes handling
zero-length arguments simpler. The old ordering can be obtained by
appending a new option "preexpand", after a comma, to the "run".
So I tried using ,preexpand to hopefully get it to work and unfortunately just see a parsing error now, similar to [0].
[0] - https:/ /www.mail- archive. com/search?<email address hidden> &q=subject: %22%5C% 5Bexim% 5C%5D+Failed+ to+expand+ ACL+string% 22&o=newest& f=1