Log uid MTA option

Transaction logging MTA options:  (0-7)
Certain alias operations, particularly alias expansion of user addresses, involve looking up LDAP entries with uid attributes. When such entries are encountered, the uid is carried through the uid expansion process and, in the case of delivering to the Message Store, the uid is typically incorporated into the resulting address. The  MTA option provides the means to log such uids. This can be useful when there is a need to identify the last LDAP entry involved in the alias expansion. Note that uids are only logged on message enqueue operations; there is no uid available to log on message dequeues.

The  MTA option defaults to 0. Setting bit 0 (value 1) logs any available uid. The uid appears immediately after the initial recipient address. A " " attribute is used in the XML or JSON log format (  set to 4 or 5, respectively). If bit 1 (value 2) is set in the  MTA option, then the uid appears in the    mapping table probe immediately after the initial destination address field.

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

See also:
 * Transaction logging MTA options
 * MTA transaction logging
 * log_format MTA Option
 * Triggering effects from transaction logging with LOG_ACTION