Log filter MTA option

Transaction logging MTA options:  (0-7)
The  option controls whether or not any mailbox filter actions (Sieve filter actions) applicable to the message are logged in enqueue "E" records or included in    mapping probes. Bit 0 (value 1), if set, causes filter information to appear in log entries. New in 7.0-3.01, bit 1 (value 2), if set, causes filter information to be included in  mapping probes. This information appears after the optional "intermediate" and "original" forms of the destination address (see the   MTA option), before the  SMTP diagnostic field (which itself only appears for SMTP messages). In XML or JSON format (  set to 4 or 5, respectively),  Sieve filter action(s) logging, if enabled, appears as the   attribute. The filter action(s) will be enclosed within single quote characters.

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

As of MS 6.3p1, enabling XML or JSON format ( set to 4 or 5) causes the default for   to be 1 (Sieve filter action logging enabled); with any other format, the default is 0, (Sieve filter actions are not logged), as in previous versions. With  set to 1, one might see, for instance &#x27;fileinto "SPAM"&#x27; or &#x27;redirect "user@domain.com"&#x27; As of 8.0, a " " clause may also be present; see the discussion in Sieve warn extension.

Note that the case of a " " action is special, due to the inherent nature of the " " action. In this case, what occurs is the enqueue of a new message (a Message Disposition Notification)  by the original enqueuing channel to the  process channel,  and that new message has an implicit   occurring. As there is no enqueue of the rejected message, the " " does not show up in the filter action field of any transaction log record.

As of MS 8.0, the maximum size of the  field (the maximum length of the string recording what Sieve actions were applied) has been increased from 256 to 1024 characters.

See also:
 * MTA transaction logging
 * Triggering effects from transaction logging with LOG_ACTION
 * log_format MTA Option
 * Notification message types
 * Process and reprocess channels
 * Sieve warn extension
 * Sieve filter log and debug MTA options
 * Transaction logging MTA options