Log_diagnostics MTA option

From Messaging Server Technical Reference Wiki
Revision as of 12:18, 30 November 2018 by BulkPageCreator (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Transaction logging MTA options: log_diagnostics (0-3)

(New in 7.0-3.01.) Bit 0 (value 1), if set in log_diagnostics, causes diagnostics information to appear in certain log entries. Bit 1 (value 2), if set, causes diagnostics information to be included in LOG_ACTION mapping probes. For instance, in the case of "B" records (bad commands received by the SMTP server), the diagnostic field will show the SMTP server error response. In the case of connection close "C" records, the diagnostic file will show the reason why the connection was closed, e.g., reaching some session disconnect limit. In the case of authentication "U" entries (which note are generated as connection transaction entries, rather than message transaction entries), the result of an authentication attempt is shown in the diagnostic field. Appears just after the reason field (see the log_reason MTA option) and before the time-in-queue field (see the log_queue_time MTA option). In XML or JSON format (log_format set to 4 or 5, respectively), diagnostic information, if enabled, appears as the di attribute.

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

This option defaults to 1 in order to maintain compatibility with previous releases, where diagnostics information was always logged.

See also: