https://bugs.exim.org/show_bug.cgi?id=2956
--- Comment #7 from Andrew Aitchison <exim@???> ---
> It's using a hardwired config file path, at least in the testsuite.
> Noticing the -C the testharness gave it would be good;
I've got that working, which confuses me. I had expected that to pass one of
the configs in test/confs/
> but for production use - how about using `exim -bP localhost_number'
> as a default for no "-C foo" given?
That makes some sense, but exim_msgtime has perl taint set, so I cannot
easily run a binary by name given as an argument.
Also, do we know the name of the exim executable at make time ?
I think $(BIN_DIRECTORY) gives us the path, but Debian and Ubuntu change the
name to exim4.
It isn't working in attachment 1435, but after a bug-fix, the build now
correctly writes the configfile list into the script and I can search that for
localhost_number.
--
You are receiving this mail because:
You are on the CC list for the bug.
