All MIBs › MESSAGE-TRACKING-MIB
Organization: IETF
Last Updated: 1997-04-11
Category: IETF Standards, Network Management
Description: Tracks IETF message delivery status and routing events across mail transfer agents.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is MESSAGE-TRACKING-MIB?
MESSAGE-TRACKING-MIB is a standard IETF MIB for tracking the progress of a message (e.g., email/fax) through an MTA (Message Transfer Agent) or messaging gateway. Its MTA-information table, keyed by index, records name, messaging type, start time for recorded information, and an alternative agent, while a message-tracking request table (indexed, next-request-index counter) records row/response status, max responses, unique/inbound/outbound message IDs, inbound/outbound originator and their name form, inbound/outbound recipient and name form, subject, and minimum message size. As a status MIB it lets an administrator trace a specific message's path and delivery status across MTA hops. It is deployed on messaging gateways/MTAs implementing IETF message tracking. Engineers implementing or auditing this functionality typically reference the MESSAGE-TRACKING-MIB RFC/standard documentation for the authoritative specification.
IPNetwork Monitor allows you to monitor SNMP objects defined in MESSAGE-TRACKING-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Messaging gateways/MTAs implementing IETF message tracking
Monitoring Examples
An administrator queries msgTrackRequestTable with a specific reqUniqueMsgId to trace a message's delivery path across MTA hops.
What Can Be Monitored
- message tracking request status and delivery path
This MIB depends on
Related MIBs
Imported Objects
From RFC1155-SMI
| experimental |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| DateAndTime | |
| DisplayString | |
| TimeInterval |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| msgTracking | 1.3.6.1.3.73.2 | |||
| mta_message_track | 1.3.6.1.3.73.2.1 | The MIB module describing message tracking | ||
| mtaInformationTable | 1.3.6.1.3.73.2.1.1 | not-accessible | The table holding information about the MTA being queried. A table is used because there may be multiple MTAs at a single host. | |
| mtaInformationEntry | 1.3.6.1.3.73.2.1.1.1 | not-accessible | One entry in the table holding information about the MTA being queried | |
| INT mtaIndex | 1.3.6.1.3.73.2.1.1.1.1 | INTEGER | read-only | The integer index into this table. |
| STR mtaName | 1.3.6.1.3.73.2.1.1.1.2 | DisplayString | read-only | The name of the MTA described in this row of the table. |
| STR mtaMessagingType | 1.3.6.1.3.73.2.1.1.1.3 | DisplayString | read-only | Common name of the messaging system of this MTA (e.g. X.400, SMTP). |
| DAT mtaStartTimeforRecordedInformation | 1.3.6.1.3.73.2.1.1.1.4 | DateAndTime | read-only | The date/time of the oldest message tracking information available from this MTA. |
| STR mtaAlternativeAgent | 1.3.6.1.3.73.2.1.1.1.5 | DisplayString | read-only | The name (or address) of another agent that may have message tracking information concerning this MTA. |
| C32 msgTrackNextRequestIndex | 1.3.6.1.3.73.2.1.2 | Counter32 | read-only | The 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). |
| msgTrackRequestTable | 1.3.6.1.3.73.2.1.3 | not-accessible | The table holding all active message tracking requests. | |
| msgTrackRequestEntry | 1.3.6.1.3.73.2.1.3.1 | not-accessible | The entry associated with each request for message information. | |
| INT reqEntryIndex | 1.3.6.1.3.73.2.1.3.1.1 | INTEGER | read-only | The integer index into the msgTrackRequestTable table. |
| INT reqRowStatus | 1.3.6.1.3.73.2.1.3.1.2 | INTEGER | read-write | The 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. |
| INT reqResponseStatus | 1.3.6.1.3.73.2.1.3.1.3 | INTEGER | read-only | Indicates 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. |
| INT reqMaxResponses | 1.3.6.1.3.73.2.1.3.1.4 | INTEGER | read-write | Specifies 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). |
| STR reqUniqueMsgId | 1.3.6.1.3.73.2.1.3.1.5 | DisplayString | read-write | Specifies 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. |
| STR reqInboundMsgId | 1.3.6.1.3.73.2.1.3.1.6 | DisplayString | read-write | Specifies 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. |
| STR reqOutboundMsgId | 1.3.6.1.3.73.2.1.3.1.7 | DisplayString | read-write | Specifies 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. |
| STR reqInboundOriginator | 1.3.6.1.3.73.2.1.3.1.8 | DisplayString | read-write | Identifies 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. |
| STR reqOutboundOriginator | 1.3.6.1.3.73.2.1.3.1.9 | DisplayString | read-write | Identifies 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. |
| NAM reqOriginatorNameForm | 1.3.6.1.3.73.2.1.3.1.10 | NameForm | read-write | Identifies 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. |
| STR reqInboundRecipient | 1.3.6.1.3.73.2.1.3.1.11 | DisplayString | read-write | Identifies 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. |
| STR reqOutboundRecipient | 1.3.6.1.3.73.2.1.3.1.12 | DisplayString | read-write | Identifies 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. |
| NAM reqRecipientNameForm | 1.3.6.1.3.73.2.1.3.1.13 | NameForm | read-write | Identifies 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. |
| STR reqSubject | 1.3.6.1.3.73.2.1.3.1.14 | DisplayString | read-write | Identifies 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. |
| INT reqMinMsgSize | 1.3.6.1.3.73.2.1.3.1.15 | INTEGER | read-write | Specifies 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. |
| INT reqMaxMsgSize | 1.3.6.1.3.73.2.1.3.1.16 | INTEGER | read-write | Specifies 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. |
| DAT reqEarliestArrivalTime | 1.3.6.1.3.73.2.1.3.1.17 | DateAndTime | read-write | Specifies 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. |
| DAT reqLatestArrivalTime | 1.3.6.1.3.73.2.1.3.1.18 | DateAndTime | read-write | Specifies 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. |
| DIS reqDispositionStatus | 1.3.6.1.3.73.2.1.3.1.19 | DispositionStatus | read-write | Specifies the disposition status of the message for a particular recipient. Set to 'unknown(1)' if unknown or irrelevant to the query. |
| MSG reqMsgType | 1.3.6.1.3.73.2.1.3.1.20 | MsgType | read-write | The type of message to be tracked. Set to 'any(1)' if message type is unknown or irrelevant to the query. |
| INT reqCollapseRecipients | 1.3.6.1.3.73.2.1.3.1.21 | INTEGER | read-write | If 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. |
| STR reqFailureReason | 1.3.6.1.3.73.2.1.3.1.22 | DisplayString | read-only | A 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)'. |
| msgTrackResponseTable | 1.3.6.1.3.73.2.1.4 | not-accessible | The table holding the response to all active message tracking requests. | |
| msgTrackResponseEntry | 1.3.6.1.3.73.2.1.4.1 | not-accessible | The entry associated with each response to a request for message information. | |
| INT respEntryIndex | 1.3.6.1.3.73.2.1.4.1.1 | INTEGER | read-only | The primary integer index into the msgTrackResponseTable table. It matches the value of reqEntryIndex for the original request. |
| INT respMsgIndex | 1.3.6.1.3.73.2.1.4.1.2 | INTEGER | read-only | The 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. |
| DIS respDispositionStatus | 1.3.6.1.3.73.2.1.4.1.3 | DispositionStatus | read-only | Indicates the disposition of this message by this MTA for this recipient. |
| DAT rspDispositionTime | 1.3.6.1.3.73.2.1.4.1.4 | DateAndTime | read-only | Time at which this MTA disposed of this message for this recipient. |
| STR respNextHopMta | 1.3.6.1.3.73.2.1.4.1.5 | DisplayString | read-only | Name of the MTA to which this message was sent. MADMAN-compliant MTA's should be addressed in the form '(::)'. |
| STR respPrevHopMta | 1.3.6.1.3.73.2.1.4.1.6 | DisplayString | read-only | Name of the MTA from which this message was received. MADMAN- compliant MTA's should be addressed in the form '(::)'. |
| STR respNonDeliveryReason | 1.3.6.1.3.73.2.1.4.1.7 | DisplayString | read-only | A 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. |
| DAT respMsgArrivalTime | 1.3.6.1.3.73.2.1.4.1.8 | DateAndTime | read-only | Represents the time at which this message for this recipient arrived at this MTA. |
| INT respMsgSize | 1.3.6.1.3.73.2.1.4.1.9 | INTEGER | read-only | Size of the message in kilo-octets. |
| STR respMsgPriority | 1.3.6.1.3.73.2.1.4.1.10 | DisplayString | read-only | Textual representation of the priority of the message. No attempt is made to normalize these values across disparate messaging technologies. |
| STR respUniqueMsgId | 1.3.6.1.3.73.2.1.4.1.11 | DisplayString | read-only | The unique message identifier that the MTA assigned internally to the message. |
| STR respInboundMsgId | 1.3.6.1.3.73.2.1.4.1.12 | DisplayString | read-only | The 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. |
| STR respOutboundMsgId | 1.3.6.1.3.73.2.1.4.1.13 | DisplayString | read-only | The 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. |
| STR respInboundOriginator | 1.3.6.1.3.73.2.1.4.1.14 | DisplayString | read-only | Textual 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. |
| STR respOutboundOriginator | 1.3.6.1.3.73.2.1.4.1.15 | DisplayString | read-only | Textual 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. |
| STR respInboundRecipient | 1.3.6.1.3.73.2.1.4.1.16 | DisplayString | read-only | Textual 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.. |
| STR respOutboundRecipient | 1.3.6.1.3.73.2.1.4.1.17 | DisplayString | read-only | Textual 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. |
| STR respSupplementalInformation | 1.3.6.1.3.73.2.1.4.1.18 | DisplayString | read-only | Contains 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. |
| STR respSubject | 1.3.6.1.3.73.2.1.4.1.19 | DisplayString | read-only | The full text of the subject of the tracked message |
| MSG respMsgType | 1.3.6.1.3.73.2.1.4.1.20 | MsgType | read-only | The type of the tracked message |
| messageTrackingConformance | 1.3.6.1.3.73.2.1.5 | |||
| messageTrackingGroups | 1.3.6.1.3.73.2.1.5.1 | |||
| msgIdGroup | 1.3.6.1.3.73.2.1.5.1.1 | A collection of objects for tracking messages where the messageId is known with responses containing basic message information. | ||
| basicGroup | 1.3.6.1.3.73.2.1.5.1.2 | A collection of objects for tracking messages where the messageId is not known with responses containing basic message information. | ||
| enhancedGroup | 1.3.6.1.3.73.2.1.5.1.3 | A collection of objects for tracking messages where the messageId is not known with responses containing enhanced message information as well as enhanced query capabilities. | ||
| gatewayGroup | 1.3.6.1.3.73.2.1.5.1.4 | A collection of object for tracking messages that have passed through a gateway mta. | ||
| messageTrackingCompliances | 1.3.6.1.3.73.2.1.5.2 | |||
| limitedCompliance | 1.3.6.1.3.73.2.1.5.2.1 | The basic levels of compliance for SNMPv2 entities that implement this MIB for message tracking requiring the knowledge of a message Id. | ||
| basicCompliance | 1.3.6.1.3.73.2.1.5.2.2 | The basic levels of compliance for SNMPv2 entities that implement this MIB for message tracking without requiring the knowledge of a message Id. | ||
| enhancedCompliance | 1.3.6.1.3.73.2.1.5.2.3 | The 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. | ||
| gatewayCompliance | 1.3.6.1.3.73.2.1.5.2.4 | The basic levels of compliance for SNMPv2 entities that implement this MIB for message tracking across mta's that perform a gateway function. |
RFC description
Tracks message delivery status through MTA (Message Transfer Agents) supporting disposition tracking and recipient tracking.
Start monitoring Vendor-neutral IETF standard (messaging gateway/MTA, message tracking) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.