# Validate Exim configure file syntax

This function evaluates and validates an Exim configuration file's syntax.

Note:

On servers that run CentOS 7, you may see a named warning about the absence of SPF resource
records on DNS.
  * This warning is not relevant on CentOS 7 servers, because
  RFC 7208 deprecated SPF records.
  CentOS 7 servers use TXT records instead of SPF records.
  * Red Hat 7.1 and CentOS 7.1 both contain bind-9.9.4-23.el7, which is an updated version of
  BIND that complies with RFC 7208. To resolve this issue, update your operating system to a
  version that contains the updated version of BIND. For more information, read the
  Red Hat Bugzilla case about SPF record errors.

Endpoint: GET /validate_exim_configuration_syntax
Version: 11.136.0.13
Security: BasicAuth

## Query parameters:

  - `cfg_text` (string)
    The Exim configuration file's raw text.

Note:

If you do not use this parameter, the function will analyze Exim's current configuration.
    Example: "RAW_CONFIGURATION_TEXT"

  - `section` (string)
    The Exim configuration file's section to check.

Note:

If you use this parameter, pass only the desired section to validate as the
cfg_text value.
    Example: "acl"

## Response 200 fields (application/json):

  - `data` (object)
    An object containing a valid or invalid Exim configuration information.

  - `metadata` (object)

  - `metadata.command` (string)
    The method name called.
    Example: "validate_exim_configuration_syntax"

  - `metadata.output` (string)
    The function's raw HTML output, if any exists.

  - `metadata.reason` (string)
    The reason the API function failed when the metadata.result field is 0. This field may display a success message when a function succeeds.
    Example: "OK"

  - `metadata.result` (integer)
    * 1 — Success.
* 0 — Failed. Check the reason field for more details.
    Enum: 1, 0

  - `metadata.version` (integer)
    The version of the API function.
    Example: 1