Log conversion tag MTA option

Logging Conversion Tags: (bitmask)
New in 7.0.5. The  MTA option causes a field recording any conversion tags  to be included in MTA message transaction log file entries (both "E" and "D") and/or    mapping table  probes.

Bit 0 (value 1) enables including the field in MTA message transaction log file entries; bit 1 (value 2) enables including the field in   mapping table probes. If enabled, this field appears after the "time in queue" field ( option) and before the IMAP flags field (  option). The XML or JSON format tag for this field is "tg". The default is 0 (even in XML or JSON format logging operation).

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

As of MS 8.0.2.3, bit 3 (value 8) will cause the first conversion tag associated with each message recipient, if present, to be treated as an additional "virtual channel" by the MTA counter subsystem. This "channel" will then appear in counter output along with all the other channels. Note that no attempt is made to distinguish these virtual channels from normal channels; use of unique names must be dealt with by appropriate configuration.

As of MS 8.1.0.3, bit 4 (value 16) will cause the conversion tags associated with the current message being dequeued to be logged in the extra field of any connection log records.

See also:
 * Transaction logging MTA options
 * Triggering effects from transaction logging with LOG_ACTION
 * Conversions MTA options
 * log_queue_time MTA Option
 * log_imap_flags MTA Option
 * log_format MTA Option
 * Conversion tags