-## $Cambridge: exim/doc/doc-src/FAQ.src,v 1.8 2009/11/05 19:37:00 nm4 Exp $
##
## This file is processed by Perl scripts to produce an ASCII and an HTML
## version. Lines starting with ## are omitted. The markup used with paragraphs
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
Q0311: When a DNS lookup for MX records fails to complete, why doesn't Exim
- send the messsage to the host defined by the A record?
+ send the message to the host defined by the A record?
A0311: The RFCs are quite clear on this. Only if it is known that there are no
MX records is an MTA allowed to make use of the A record. When an MX