7.3 Preprocessor Configuration

MFL preprocessor is configured using the preprocessor statement (default values shown):

preprocessor {
  # Enable preprocessor
  enable yes;
  # Preprocessor command line stub.
  command "m4 -s";
  # Pass current include path to the preprocessor via -I options.
  pass-includes false;
  # Pass to the preprocessor the feature definitions via -D options
  # as well as any -D/-U options from the command line
  pass-defines true;
  # Name of the preprocessor setup file.  Unless absolute, it is
  # looked up in the include path.
  setup-file "pp-setup";
}

Its substatements are:

preprocessor: enable bool

Enable or disable preprocessor. If disabled in configuration file, preprocessor can be forcefully enabled in the command line by using the --preprocessor option.

preprocessor: command string

The stub for the preprocessor command line. Before use, it will be eventually augmented by -I and -D options, depending on the pass-includes and pass-defines settings in this section. This is described in detail in Configuring Preprocessor.

preprocessor: pass-includes bool

If true the directories from include search path (see include search path will be passed to the preprocessor via the -I options.

preprocessor: pass-defines bool

If true, the -D options defining optional features will be passed to the preprocessor (e.g. -DWITH_DKIM), as well as any -D and -U options from the mailfromd command line.

preprocessor: setup-file string

Name of the preprocessor setup file (see Preprocessor). Unless string begins with a slash, the file with this name is looked up in the current include search path (see include search path). If found, its absolute name is passed to the preprocessor as its first argument.

If string begins with a slash, it is passed to the preprocessor as is.