Comment 1 for bug 721108

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Unfortunately, this is the way upstream Exim has decided to fix the security issue. Use of macros is no longer supported. Even the WHITELIST_D_MACROS compile time option is just temporary and will be removed in later versions.

Here is a extract from the new EDITME file that has some information:

# By contrast, you might be maintaining a system which relies upon the ability
# 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_LIST.
# That shim can set macros before .include'ing your main configuration file.

In other words, for each macro that you used to be using, you should create a new configuration file that includes the main configuration file. These configuration files should be set as "trusted" by being listed in /etc/exim4/trusted_configs.

We apologize for the inconvenience.