Log mailbox uid MTA option

Transaction logging MTA options:  (0-3)
Messages delivered to an IMAP store are tagged with a UID and the folder&#x27;s UIDVALIDITY value upon insertion. The  MTA option provides the means to log this type of information, which can be useful when there is a need to correlate a message in the store with MTA actions. Prior to MS 8.0 the field consisted of these two values delimited by a colon. in MS 8.0 and later release two additional fields have been added: One for the message digest and another for the name of the folder the message is actually delivered to. Note that the message digest is only included when one is calculated for other reasons.

The  MTA option defaults to 0. Setting bit 0 (value 1) logs the UID and UIDVALIDITY of messages delivered by the   channel to the store. The UID and UIDVALIDITY appears immediately after the LDAP uid. 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 LDAP uid.

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

It&#x27;s a simple matter to log this information in the case of ims-ms channel. But in the case of LMTP things are not so simple - the information naturally exists in the LMTP server but not the client. An LMTP extension is needed to pass the information to the client for logging purposes.

Consequently, as of MS 8.0.1.2, the LMTP client and server have been enhanced to support a new UID extension. This extension, if present, provides a single UID parameter on the MAIL FROM command that accepts the values "NO" or "RET". If the latter is specified the final LMTP responses to DATA/BDAT will include the UID, UIDVALIDITY, digest value (if available), and optionally the folder if different from INBOX, separated by colons and enclosed in angle brackets. For example: S: 220 multke.mrochek.com -- Server LMTP (Oracle Communications Messaging Server 8.0.1.2 64bit (built Sep 19 2015)) C: LHLO multke.mrochek.com S: 250-multke.mrochek.com S: 250-8BITMIME S: 250-UID S: 250-PIPELINING S: 250-CHUNKING S: 250-XDFLG S: 250-XQUOTA S: 250-XAFLG S: 250-ENHANCEDSTATUSCODES S: 250-HELP S: 250 SIZE 0 C: MAIL FROM:&#x3c;&#x3e; UID=RET S: 250 2.5.0 Address Ok. C: RCPT TO:&#x3c;test1+folder@ims-ms-daemon&#x3e; XDFLGS=5 S: 250 2.1.5 test1@ims-ms-daemon OK. C: RCPT TO:&#x3c;test2@ims-ms-daemon&#x3e; S: 250 2.1.5 test2@ims-ms-daemon OK. C: DATA S: 354 Enter mail, end with a single ".". C: Subject: Test message C: C: This is a test. C:. S: 250 2.5.0 &#x3c;1445028362:2::folder&#x3e; Delivery to user OK S: 250 2.5.0 &#x3c;1440097745:2:&#x3e; Delivery to user OK This extension is enabled by default and cannot be disabled. The LMTP client will use if it present to obtain UID information to use in conjunction with the  MTA option as well as the recall facility.

Additionally, as of MS 8.0.1.2 the  MTA option now enables logging of UID information in the S records logged by the LMTP server. Note that this logging does not depend on use of the LMTP extension.

Compatibility note: Additional information will be added to this field in the future. When that happens it will appear as additional colon-separated values. Any code written to process this field needs to take this into account.

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