Difference between revisions of "Log diagnostics MTA option"

From Messaging Server Technical Reference Wiki
Jump to: navigation, search
m (Bulk update)
m (Bulk update)
 
(5 intermediate revisions by one user not shown)
Line 5: Line 5:
 
== Transaction logging MTA options:  <code>log_diagnostics</code> (0-3) ==
 
== Transaction logging MTA options:  <code>log_diagnostics</code> (0-3) ==
  
(New in 7.0-3.01.) Bit 0 (value 1), if set in <code>log_diagnostics</code>,  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 table#LOG_ACTION_mapping_table|<code>LOG_ACTION</code> 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 <code>log_reason</code> MTA option) and before the time-in-queue field (see the <code>log_queue_time</code> MTA option). In XML-compatible format  ([[log_format MTA option#log_format|<code>log_format</code>]] set to 4), diagnostic information, if enabled, appears as the <code>di</code> attribute.  
+
(New in 7.0-3.01.) Bit 0 (value 1), if set in <code>log_diagnostics</code>,  causes diagnostics information to appear in certain log entries. Bit 1 (value 2), if set, causes diagnostics information to be included in  [[Triggering effects from transaction logging with LOG_ACTION#Triggering_effects_from_transaction_logging_with_LOG_ACTION|<code>LOG_ACTION</code> 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 "<code>U</code>" 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 <code>log_reason</code> MTA option) and before the time-in-queue field (see the <code>log_queue_time</code> MTA option). In XML or JSON format  ([[log_format MTA option#log_format|<code>log_format</code>]] set to 4 or 5, respectively), diagnostic information, if enabled, appears as the <code>di</code> attribute.
 +
 
 +
Normally the <code>di</code> attribute only appears in XML or JSON format logs if there is diagnostic information to log. As of MS 8.0.2.3, 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.  
 
This option defaults to 1 in order to maintain compatibility with previous releases, where diagnostics information was always logged.  
Line 12: Line 14:
 
See also:
 
See also:
 
* [[Transaction logging MTA options#Transaction_logging_MTA_options|Transaction logging MTA options]]
 
* [[Transaction logging MTA options#Transaction_logging_MTA_options|Transaction logging MTA options]]
* [[LOG_ACTION mapping table#LOG_ACTION_mapping_table|LOG_ACTION mapping table]]
+
* [[Triggering effects from transaction logging with LOG_ACTION#Triggering_effects_from_transaction_logging_with_LOG_ACTION|Triggering effects from transaction logging with LOG_ACTION]]
 
* [[MTA transaction logging#MTA_transaction_logging|MTA transaction logging]]
 
* [[MTA transaction logging#MTA_transaction_logging|MTA transaction logging]]
* [[log_reason MTA option#log_reason|log_reason Option]]
+
* [[log_reason MTA option#log_reason|log_reason MTA Option]]
* [[log_queue_time MTA option#log_queue_time|log_queue_time Option]]
+
* [[log_remote_mta MTA option#log_remote_mta|log_remote_mta MTA Option]]
* [[log_format MTA option#log_format|log_format Option]]
+
* [[log_queue_time MTA option#log_queue_time|log_queue_time MTA Option]]
 +
* [[log_format MTA option#log_format|log_format MTA Option]]
 
[[Category: MTA]]
 
[[Category: MTA]]
 
[[Category: Reference]]
 
[[Category: Reference]]

Latest revision as of 12:18, 30 November 2018



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 8.0.2.3, 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: