MESSAGE-TRACKING-MIB
AI MIB Summary
The MESSAGE-TRACKING-MIB provides standardized SNMP objects for monitoring email message delivery states, tracking identifiers, and routing history across mail transfer agents (MTAs) and mail gateways. It enables administrators to query specific message flow metrics, including delivery status, queue positions, and transmission timestamps, for troubleshooting and compliance auditing.
The MIB module describing message tracking
Main OID:
mta_message_track.1.3.6.1.3.73.2.1
67
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
67 total| Object Name |
|---|
msgTracking OBJECT IDENTIFIER .1.3.6.1.3.73.2 |
mta_message_trackThe MIB module describing message tracking MODULE-IDENTITY .1.3.6.1.3.73.2.1 |
mtaInformationTableThe table holding information about the MTA being queried. A table is used because there may be multiple MTAs at a single host. SEQUENCE OF MtaInformationEntry .1.3.6.1.3.73.2.1.1 |
mtaInformationEntryOne entry in the table holding information about the MTA being queried MtaInformationEntry .1.3.6.1.3.73.2.1.1.1 |
mtaIndexThe integer index into this table.ro INTEGER .1.3.6.1.3.73.2.1.1.1.1 |
mtaNameThe name of the MTA described in this row of the table.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.1.1.2 |
mtaMessagingTypeCommon name of the messaging system of this MTA (e.g. X.400, SMTP).ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.1.1.3 |
mtaStartTimeforRecordedInformationThe date/time of the oldest message tracking information available from this MTA.ro DateAndTime (SNMPv2-TC) .1.3.6.1.3.73.2.1.1.1.4 |
mtaAlternativeAgentThe name (or address) of another agent that may have message tracking information concerning this MTA.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.1.1.5 |
msgTrackNextRequestIndexThe index that may be used by a manager (requestor) on a 'set-request' PDU to create a new conceptual row in the msgTrackRequestTable table (and thereby issue a message tracking query).ro Counter32 -- Note that in SNMPv1, the syntax is simply 'Counter' .1.3.6.1.3.73.2.1.2 |
msgTrackRequestTableThe table holding all active message tracking requests. SEQUENCE OF MsgTrackRequestEntry .1.3.6.1.3.73.2.1.3 |
msgTrackRequestEntryThe entry associated with each request for message information. MsgTrackRequestEntry .1.3.6.1.3.73.2.1.3.1 |
reqEntryIndexThe integer index into the msgTrackRequestTable table.ro INTEGER .1.3.6.1.3.73.2.1.3.1.1 |
reqRowStatusThe status of the conceptual row. These are mapped to the same values as the RowStatus textual conversion in SNMPv2 and carry the same semantics with one exception: the exception is that when a manager (requestor) sets the value to destroy(6), this also has the added semantics of deleting all conceptual rows in the msgTrackResponseTable table whose respEntryIndex matches the reqEntryIndex of this conceptual row.rw Enumeration .1.3.6.1.3.73.2.1.3.1.2 |
reqResponseStatusIndicates the status of this query and its responses in the msgTrackResponseTable. Values are: unknown - The status of this query is not known. inProgress - The agent(responder) is still processing the request. failedNoMatches - The query has been processed and has produced no matches. failedInvalidQuery - The query could not be processed due to invalid or missing data in the original query. FailedError - The query could not be processed due to an error in the agent(responder). successUnderqualified - The query was successfully processed, but the query was found to be underqualified. That is, more reponses were found than were specified in reqMaxResponses. reqMaxResponses entries were returned in the msgTrackResponseTable. success - The query succeeded, returning from 1 to reqMaxResponse entries in the msgTrackResponseTable.ro Enumeration .1.3.6.1.3.73.2.1.3.1.3 |
reqMaxResponsesSpecifies the largest number of responses to be returned in the msgTrackResponseTable on an underspecified query (i.e. the maximum value of respMsgIndex in the msgTrackResponseTable conceptual row whose respEntryIndex matches the reqEntryIndex of this conceptual row).rw INTEGER .1.3.6.1.3.73.2.1.3.1.4 |
reqUniqueMsgIdSpecifies a unique message id used internally by the MTA for identification of a message. This form of the message id may or may not be identical to the inbound and/or outbound forms of the message id. If specified, this may be the only search criteria required. If the entire unique message id is not specified, prefix matching is assumed. Set to an empty (zero length) string if unknown or irrelevant to query.rw DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.3.1.5 |
reqInboundMsgIdSpecifies a unique message id as received by the MTA for identification of a message. This form of the message id may or may not be identical to the internal and/or outbound forms of the message id. If specified, this may be the only search criteria required. If the entire inbound message id is not specified, prefix matching is assumed. Set to an empty (zero length) string if unknown or irrelevant to query.rw DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.3.1.6 |
reqOutboundMsgIdSpecifies a unique message id as transmitted by the MTA for identification of a message. This form of the message id may or may not be identical to the internal and/or inbound forms of the message id. If specified, this may be the only search criteria required. If the entire outbound message id is not specified, prefix matching is assumed. Set to an empty (zero length) string if unknown or irrelevant to query.rw DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.3.1.7 |
reqInboundOriginatorIdentifies the originator of the message in its received form, expressed in string format. The style and format of this identifier varies according to a specific messaging technology. As a result of potentially disparate messaging technologies, this identifier is only guaranteed to be the name known to the end-user on the first MTA in the delivery sequence. If reqOriginatorNameForm is set to 'x.400(2)' or 'smtp(3)', the supplied attributes will be considered in the match. Any attributes not supplied will be wildcarded. If reqOriginatorNameForm is set to 'freeForm(1)', this value is assumed to be a substring of the originator name. Set to an empty (zero length) string if unknown or irrelevant to query.rw DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.3.1.8 |
reqOutboundOriginatorIdentifies the originator of the message in its transmitted form, expressed in string format. The style and format of this identifier varies according to a specific messaging technology. As a result of potentially disparate messaging technologies this identifier is only guaranteed to be the name known to the end-user on the last MTA in the delivery sequence. If reqOriginatorNameForm is set to 'x.400(2)' or 'smtp(3)', the supplied attributes will be considered in the match. Any attributes not supplied will be wildcarded. If reqOriginatorNameForm is set to 'freeForm(1)', this value is assumed to be a substring of the originator name. Set to an empty (zero length) string if unknown or irrelevant to query.rw DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.3.1.9 |
reqOriginatorNameFormIdentifies the name form of originator strings supplied in the reqInboundOriginator and/or reqOutboundOriginator values. This value is used by the agent to perform name form dependant parsing of these values. If neither of these strings are supplied, this name form value is irrelevant to the query. A value of 'any(1)' implies that no special parsing should be performed on the originator names supplied.rw NameForm .1.3.6.1.3.73.2.1.3.1.10 |
reqInboundRecipientIdentifies one of the recipients (the one to be tracked) of the message in its received form, expressed in string format. The style and format of this identifier varies according to a specific messaging technology. As a result of potentially disparate messaging technologies, this identifier is only guaranteed to be the name an end-user knows the recipient by on the first MTA in the delivery sequence. If reqRecipientNameForm is set to 'x.400(2)' or 'smtp(3)', the supplied attributes will be considered in the match. Any attributes not supplied will be wildcarded. If reqRecipientNameForm is set to 'freeForm(1)', this value is assumed to be a substring of the recipient name. Set to an empty (zero length) string if unknown or irrelevant to query.rw DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.3.1.11 |
reqOutboundRecipientIdentifies one of the recipients (the one to be tracked) of the message in its transmitted form, expressed in string format. The style and format of this identifier varies according to a specific messaging technology. As a result of potentially disparate messaging technologies, this identifier is only guaranteed to be the name an end-user knows the recipient by on the last MTA in the delivery sequence. If reqRecipientNameForm is set to 'x.400(2)' or 'smtp(3)', the supplied attributes will be considered in the match. Any attributes not supplied will be wildcarded. If reqRecipientNameForm is set to 'freeForm(1)', this value is assumed to be a substring of the recipient name. Set to an empty (zero length) string if unknown or irrelevant to query.rw DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.3.1.12 |
reqRecipientNameFormIdentifies the name form of recipient strings supplied in the reqInboundRecipient and/or reqOutboundRecipient values. This value is used by the agent to perform name form dependant parsing of these values. If neither of these strings are supplied, this name form value is irrelevant to the query. A value of 'any(1)' implies that no special parsing should be performed on the recipient names supplied.rw NameForm .1.3.6.1.3.73.2.1.3.1.13 |
reqSubjectIdentifies a substring of the text of the 'Subject' attribute of the message. Since some messaging technologies make it difficult for an MTA to preserve this data, it may not be supported by all agents. Set to an empty (zero length) string if unknown or irrelevant to query.rw DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.3.1.14 |
reqMinMsgSizeSpecifies the minimum size of a message to be tracked (content, excluding envelope), expressed in kilo-octets. Set both reqMinMsgSize and reqMaxMsgSize to zero if message size is irrelevant to the query.rw INTEGER .1.3.6.1.3.73.2.1.3.1.15 |
reqMaxMsgSizeSpecifies the maximum size of a message to be tracked (content, excluding envelope), expressed in kilo-octets. Set both reqMinMsgSize and reqMaxMsgSize to zero if message size is irrelevant to the query.rw INTEGER .1.3.6.1.3.73.2.1.3.1.16 |
reqEarliestArrivalTimeSpecifies the earliest arrival time, at this MTA, for a message to be tracked. Set to an empty (zero length) string if unknown or irrelevant to query.rw DateAndTime (SNMPv2-TC) .1.3.6.1.3.73.2.1.3.1.17 |
reqLatestArrivalTimeSpecifies the latest arrival time, at this MTA, for a message to be tracked. Set to an empty (zero length) string if unknown or irrelevant to query.rw DateAndTime (SNMPv2-TC) .1.3.6.1.3.73.2.1.3.1.18 |
reqDispositionStatusSpecifies the disposition status of the message for a particular recipient. Set to 'unknown(1)' if unknown or irrelevant to the query.rw DispositionStatus .1.3.6.1.3.73.2.1.3.1.19 |
reqMsgTypeThe type of message to be tracked. Set to 'any(1)' if message type is unknown or irrelevant to the query.rw MsgType .1.3.6.1.3.73.2.1.3.1.20 |
reqCollapseRecipientsIf a value of 'true(2)' is specified, a single msgTrackResponseEntry will be created for each matching message regardless of the number of recipients. If not specified or set to 'false(1)', a msgTrackResponseEntry will be created for each matching message and/or recipient. This variable may be used in the case of a distribution list or a message with a large number of recipients.rw Enumeration .1.3.6.1.3.73.2.1.3.1.21 |
reqFailureReasonA textual description of why a message tracking request failed. This variable may be set by an agent when the reqResponseStatus is set to either 'failedInvalidQuery(4)', or 'failedError(5)'.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.3.1.22 |
msgTrackResponseTableThe table holding the response to all active message tracking requests. SEQUENCE OF MsgTrackResponseEntry .1.3.6.1.3.73.2.1.4 |
msgTrackResponseEntryThe entry associated with each response to a request for message information. MsgTrackResponseEntry .1.3.6.1.3.73.2.1.4.1 |
respEntryIndexThe primary integer index into the msgTrackResponseTable table. It matches the value of reqEntryIndex for the original request.ro INTEGER .1.3.6.1.3.73.2.1.4.1.1 |
respMsgIndexThe secondary integer index into the msgTrackResponseTable table. For each value of respEntryIndex in the table, there may be multiple conceptual rows indexed by respMsgIndex, each denoting a possible response to the tracking query. The maximum number of entries should have an upper bound of the value of reqMaxResponses in the conceptual row of msgTrackRequestTable that represents the original query request.ro INTEGER .1.3.6.1.3.73.2.1.4.1.2 |
respDispositionStatusIndicates the disposition of this message by this MTA for this recipient.ro DispositionStatus .1.3.6.1.3.73.2.1.4.1.3 |
rspDispositionTimeTime at which this MTA disposed of this message for this recipient.ro DateAndTime (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.4 |
respNextHopMtaName of the MTA to which this message was sent. MADMAN-compliant MTA's should be addressed in the form '(<host-id>::<mtaName>)'.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.5 |
respPrevHopMtaName of the MTA from which this message was received. MADMAN- compliant MTA's should be addressed in the form '(<host-id>::<mtaName>)'.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.6 |
respNonDeliveryReasonA textual representation representing the reason for non-delivery to this recipient. No attempt is made to normalize these non-delivered reasons across systems, since this indicates a terminal condition.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.7 |
respMsgArrivalTimeRepresents the time at which this message for this recipient arrived at this MTA.ro DateAndTime (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.8 |
respMsgSizeSize of the message in kilo-octets.ro INTEGER .1.3.6.1.3.73.2.1.4.1.9 |
respMsgPriorityTextual representation of the priority of the message. No attempt is made to normalize these values across disparate messaging technologies.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.10 |
respUniqueMsgIdThe unique message identifier that the MTA assigned internally to the message.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.11 |
respInboundMsgIdThe unique message identifier that the 'previous hop' MTA assigned to the message. If the 'previous' MTA uses a different messaging technology or identifier scheme, this identifier serves to correlate the message from MTA to MTA. If the 'previous' MTA uses the same technology, this value is generally superfluous. If this is the first MTA in the delivery sequence, or if the previous message id is unknown, this variable is null- valued.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.12 |
respOutboundMsgIdThe unique message identifier that the 'next hop' MTA assigned to the message. If the 'next' MTA uses a different messaging technology or identifier scheme, this identifier serves to correlate the message from MTA to MTA. If the 'next' MTA uses the same technology, this value is generally superfluous. If this is the last MTA in the delivery sequence, or if the next hop message id is unknown, this variable is null-valued.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.13 |
respInboundOriginatorTextual representation identifying the originator of the message as it was received from the 'previous hop' MTA. The style of this variable varies according to a specific messaging technology.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.14 |
respOutboundOriginatorTextual representation identifying the originator of the message as it was (or will be) presented to the 'next hop' MTA. The style of this variable varies according to a specific messaging technology.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.15 |
respInboundRecipientTextual representation identifying the recipient of the message as it was received from the 'previous hop' MTA. The style of this variable varies according to a specific messaging technology..ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.16 |
respOutboundRecipientTextual representation identifying the recipient of the message as it was (or will be) presented to the 'next hop' MTA. The style of this variable varies according to a specific messaging technology.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.17 |
respSupplementalInformationContains information provided by the agent to the manager that may be of use in identifying or tracking this message. No formal structure for this information is specified. Knowledge of the contents of this field is by bilateral agreement.ro DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.18 |
respSubjectThe full text of the subject of the tracked messagero DisplayString (SNMPv2-TC) .1.3.6.1.3.73.2.1.4.1.19 |
respMsgTypeThe type of the tracked messagero MsgType .1.3.6.1.3.73.2.1.4.1.20 |
messageTrackingConformance OBJECT IDENTIFIER .1.3.6.1.3.73.2.1.5 |
messageTrackingGroups OBJECT IDENTIFIER .1.3.6.1.3.73.2.1.5.1 |
msgIdGroupA collection of objects for tracking messages where the messageId is known with responses containing basic message information. Unknown .1.3.6.1.3.73.2.1.5.1.1 |
basicGroupA collection of objects for tracking messages where the messageId is not known with responses containing basic message information. Unknown .1.3.6.1.3.73.2.1.5.1.2 |
enhancedGroupA collection of objects for tracking messages where the messageId is not known with responses containing enhanced message information as well as enhanced query capabilities. Unknown .1.3.6.1.3.73.2.1.5.1.3 |
gatewayGroupA collection of object for tracking messages that have passed through a gateway mta. Unknown .1.3.6.1.3.73.2.1.5.1.4 |
messageTrackingCompliances OBJECT IDENTIFIER .1.3.6.1.3.73.2.1.5.2 |
limitedComplianceThe basic levels of compliance for SNMPv2 entities that implement this MIB for message tracking requiring the knowledge of a message Id. Unknown .1.3.6.1.3.73.2.1.5.2.1 |
basicComplianceThe basic levels of compliance for SNMPv2 entities that implement this MIB for message tracking without requiring the knowledge of a message Id. Unknown .1.3.6.1.3.73.2.1.5.2.2 |
enhancedComplianceThe basic levels of compliance for SNMPv2 entities that implement this MIB for message tracking without requiring the knowledge of a message Id and allowing an enhanced level of query capabilities. Unknown .1.3.6.1.3.73.2.1.5.2.3 |
gatewayComplianceThe basic levels of compliance for SNMPv2 entities that implement this MIB for message tracking across mta's that perform a gateway function. Unknown .1.3.6.1.3.73.2.1.5.2.4 |