Log callout delays MTA option

Transaction logging MTA options:  (0-3)
The MTA can optionally use timers to measure the total time the MTA spends waiting for various external components to return a response. The  MTA option controls the logging of this timer information. Bit 0 (value 1), if set, causes the callout logging information to be logged immediately after delivery flags in "E" (enqueue) log records. The XML attribute name in XML format logs is " ". Bit 1 (value 1), if set, causes callout logging information to be included in the   mapping probe, again immediately after delivery flags. In both cases the information is formatted as described below.

Timings are done on a per-message basis.

The following callout timers have been implemented:



 Time spent waiting for spam filters 1-8. ( -  ) 

 Time spent waiting for       mapping routine callouts. 

 Time spent in the following specific mappings waiting for routine callouts: 

  

  

  

  

  </li>

  </li>

  </li>

  </li>

 </li>

</ul>

</li>

 Rewrite rule routine callouts. </li>

 Time spent creating an SMTP transaction for the MTA to process;    (note that this necessarily includes MTA processing time). </li>

 Time spent writing the message file(s) to the MTA queue area. </li>

 Time used by the Indexed Search Converter (ISC) when operating as part of  the LMTP server. </li>

 Time spent creating an LMTP transaction for the store to process;    (note that this necessarily includes MTA processing time). </li>

 Time spent writing the message file(s) to the store. </li>

</ul>

When logging this information, it is formatted in the order and with delimiters as follows (note that the field names are specified in the preceding list): S1,S2,S3,S4,S5,S6,S7,S8:MC,PA,FA,OSA,SA,OMA,MA,AW,RV,S:RR:STT,QW,RD Each value appears an an integer time in centiseconds followed by a semicolon and an integer use count: T;U Any value consisting of a zero-time;zero-use-count pair will be omitted entirely. Use counts of 1 are also omitted. Finally, zero elements of the comma-separated sublists may be truncated from the right.

In the specific case of spam filter wait timers, an outright spam filter failure is indicated by presence of an " " suffix followed by an integer code which indicates the phase where the failure occurred. The code values are:

Parsers should be aware that additional, colon-delimited elements may be added to the list as a whole, comma-separated elements may be added to sublists, and even semicolon-separated elements may be added to individual timer values.

Some samples of the timers field in XML format: cd="1410,,,15:::123,25" cd="1243,,,21:::127,33" cd="172:1855;5,,107,248,400,500,600::4836,14" cd=":::1222,11"

See also:
 * enable_delay_timers MTA Option
 * Transaction logging MTA options
 * MTA transaction logging
 * log_format MTA Option
 * Triggering effects from transaction logging with LOG_ACTION
 * Mapping entry templates
 * PORT_ACCESS mapping table
 * FROM_ACCESS mapping table
 * Recipient access mapping tables
 * AUTH_REWRITE mapping table
 * Sieve custom tests via mappings
 * Rewrite routine substitutions