Log message id MTA option

Transaction logging MTA options:  (0-7)
The  MTA option primarily  controls whether or not message IDs are saved in the    file or included in    mapping probes. Bit 0 (value 1), if set, enables message ID logging in MTA transaction logging. When message ID logging is enabled, the message ID will be logged after the final form envelope To address entry---and after the message file name, if   is also enabled. In XML or JSON format ( set to  4 or 5, respectively), message ID logging, if enabled, appears as the   attribute. As of MS 6.3p1, enabling XML or JSON format ( set to 4 or 5) causes the default for   to be 1 (message  ID logging enabled); with any other format, the default is 0 (message ID logging disabled), as in previous versions.

Multiple message IDs can appear, separated by commas. When mutiple IDs are present, the first is the ID of the message being logged and subsequent IDs are the IDs of related messages, e.g., when a DSN or MDN is generated and enqueued by the MTA, the second message ID will be that of the message the DSN or MDN is in regards to.

Normally the  attribute only appears in XML or JSON format logs if there is message id information to log. As of MS 8.0.2.3, setting bit 2 (value 4) will cause the attribute to appear unconditionally.

Note that the  option&#x27;s transaction log field is also used in  authentication " " records to record the  SASL error, and in SMTP ETRN " " records to record the host name from the client ETRN command.

New in 7.0-3.01, bit 1 (value 2), if set, causes message ID information to be included in   mapping  probes.

See also:
 * Transaction logging MTA options
 * MTA transaction logging
 * log_format MTA Option
 * Triggering effects from transaction logging with LOG_ACTION
 * log_filename MTA Option
 * error_text MTA options