If you are running Exim with an alternate configuration file using a
command such as \"exim -C altconfig..."\, remember that the use of -C
- takes away Exim's root privilege, unless \\TRUSTED_CONFIG_PREFIX_FILE\\
+ takes away Exim's root privilege, unless \\TRUSTED_CONFIG_LIST\\
is set in \(Local/Makefile)\ and the corresponding file contains a
prefix which matches the alternative configuration file being used.
includes the case where Exim re-execs itself to regain root privilege.
Thus it can't write to the spool.
- The fix for this is to use the \\TRUSTED_CONFIG_PREFIX_LIST\\ build-time
+ The fix for this is to use the \\TRUSTED_CONFIG_LIST\\ build-time
option. This defines a file containing a list of 'trusted' prefixes for
configuration files. Any configuration file specified with -C, if it
matches a prefix listed in that file, will be used without dropping root
# to override values with -D and assumes that these will be passed through to
# the delivery processes. As of Exim 4.73, this is no longer the case by
# default. Going forward, we strongly recommend that you use a shim Exim
-# configuration file owned by root stored under TRUSTED_CONFIG_PREFIX_LIST.
+# configuration file owned by root stored under TRUSTED_CONFIG_LIST.
# That shim can set macros before .include'ing your main configuration file.
#
# As a strictly transient measure to ease migration to 4.73, the