Log transactionlog MTA option

Transaction logging MTA options:  (0-3)
(New in MS 8.0.) The  MTA option controls whether  Sieve   action  strings are included in  MTA message transaction log records. The option defaults to 0, meaning that such Sieve actions are not logged. Setting bit 0 (value 1) causes the   string to be logged at the very end of  enqueue ("E") records. The XML/JSON attribute name in XML/JSON format logs (  set to 4 or 5, respectively) is " ". Setting bit 1 (value 2) causes the  string to be included in the   mapping table  probe, again at the very end.

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

For instance, with MTA message transaction logging enabled (the  channel option set for all  channels) and with   also set: msconfig&#x3e; show logging role.channel:defaults.logging msconfig&#x3e; set log_transactionlog 1 then an MTA system filter  (see for instance the   command  ) including: require "variables"; if header :matches "subject" "&#x2a;" {transactionlog "${0}";} will cause MTA message transaction log records to include the contents of the Subject: header line. (Note that merely logging the Subject: header line of messages passing through the MTA could instead be achieved via use of  or   .  But the Sieve script approach allows more fine-tuning, as a Sieve script can be coded with complex logic  dependent upon other message details, such as message sender or recipient, presence of specific strings in the header,  etc.)

See also:
 * MTA transaction logging
 * log_format MTA Option
 * Sieve supported extensions
 * Triggering effects from transaction logging with LOG_ACTION
 * logging Option
 * Sieve filters: types of scripts
 * log_header MTA Option
 * logheader Option
 * Sieve filter log and debug MTA options
 * Transaction logging MTA options