MESSAGE-TRACKING-MIB

File: MESSAGE-TRACKING-MIB.mib (35130 bytes)

Imported modules

RFC1155-SMI	SNMPv2-SMI	SNMPv2-TC
SNMPv2-CONF

Imported symbols

experimental	OBJECT-TYPE	MODULE-IDENTITY
Counter32	DisplayString	TimeInterval
DateAndTime	OBJECT-GROUP	MODULE-COMPLIANCE

Defined Types

NameForm
INTEGER	freeForm(1), x400(2), smtp(3)

DispositionStatus
INTEGER	unknown(1), transferred(2), delivered(3), non-delivered(4), redirected(5), dlist-expanded(6), in-queue(7)

MsgType
INTEGER	any(1), data(2), status(3), probe(4)

MtaInformationEntry
SEQUENCE
	mtaIndex	INTEGER
	mtaName	DisplayString
	mtaMessagingType	DisplayString
	startTimeforRecordedInformation	DateAndTime
	alternativeAgent	DisplayString

MsgTrackRequestEntry
SEQUENCE
	reqEntryIndex	INTEGER
	reqRowStatus	INTEGER
	reqResponseStatus	INTEGER
	reqMaxResponses	INTEGER
	reqUniqueMsgId	DisplayString
	reqInboundMsgId	DisplayString
	reqOutboundMsgId	DisplayString
	reqInboundOriginator	DisplayString
	reqOutboundOriginator	DisplayString
	reqOriginatorNameForm	NameForm
	reqInboundRecipient	DisplayString
	reqOutboundRecipient	DisplayString
	reqRecipientNameForm	NameForm
	reqSubject	DisplayString
	reqMinMsgSize	INTEGER
	reqMaxMsgSize	INTEGER
	reqEarliestArrivalTime	DateAndTime
	reqLatestArrivalTime	DateAndTime
	reqDispositionStatus	DispositionStatus
	reqFailureReason	DisplayString
	reqMsgType	MsgType
	reqCollapseRecipients	INTEGER

MsgTrackResponseEntry
SEQUENCE
	respEntryIndex	INTEGER
	respMsgIndex	INTEGER
	respDispositionStatus	DispositionStatus
	respDispositionTime	INTEGER
	respNextHopMta	DisplayString
	respPrevHopMta	DisplayString
	respNonDeliveryReason	DisplayString
	respMsgArrivalTime	DateAndTime
	respMsgSize	INTEGER
	respMsgPriority	DisplayString
	respUniqueMsgId	DisplayString
	respInboundMsgId	DisplayString
	respOutboundMsgId	DisplayString
	respInboundOriginator	DisplayString
	respOutboundOriginator	DisplayString
	respInboundRecipient	DisplayString
	respOutboundRecipient	DisplayString
	respSupplementalInformation	DisplayString
	respSubject	DisplayString
	respMsgType	MsgType

Defined Values

msgTracking		1.3.6.1.3.73.2
OBJECT IDENTIFIER

mta-message-track		1.3.6.1.3.73.2.1
The MIB module describing message tracking
MODULE-IDENTITY

mtaInformationTable		1.3.6.1.3.73.2.1.1
The table holding information about the MTA being queried. A table is used because there may be multiple MTAs at a single host.
Status: current	Access: not-accessible
OBJECT-TYPE
	SEQUENCE OF
		MtaInformationEntry

mtaInformationEntry		1.3.6.1.3.73.2.1.1.1
One entry in the table holding information about the MTA being queried
Status: current	Access: not-accessible
OBJECT-TYPE
	MtaInformationEntry

mtaIndex		1.3.6.1.3.73.2.1.1.1.1
The integer index into this table.
Status: current	Access: read-only
OBJECT-TYPE
	INTEGER	1..2147483647

mtaName		1.3.6.1.3.73.2.1.1.1.2
The name of the MTA described in this row of the table.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

mtaMessagingType		1.3.6.1.3.73.2.1.1.1.3
Common name of the messaging system of this MTA (e.g. X.400, SMTP).
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

mtaStartTimeforRecordedInformation		1.3.6.1.3.73.2.1.1.1.4
The date/time of the oldest message tracking information available from this MTA.
Status: current	Access: read-only
OBJECT-TYPE
	DateAndTime

mtaAlternativeAgent		1.3.6.1.3.73.2.1.1.1.5
The name (or address) of another agent that may have message tracking information concerning this MTA.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

msgTrackNextRequestIndex		1.3.6.1.3.73.2.1.2
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).
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

msgTrackRequestTable		1.3.6.1.3.73.2.1.3
The table holding all active message tracking requests.
Status: current	Access: not-accessible
OBJECT-TYPE
	SEQUENCE OF
		MsgTrackRequestEntry

msgTrackRequestEntry		1.3.6.1.3.73.2.1.3.1
The entry associated with each request for message information.
Status: current	Access: not-accessible
OBJECT-TYPE
	MsgTrackRequestEntry

reqEntryIndex		1.3.6.1.3.73.2.1.3.1.1
The integer index into the msgTrackRequestTable table.
Status: current	Access: read-only
OBJECT-TYPE
	INTEGER	1..2147483647

reqRowStatus		1.3.6.1.3.73.2.1.3.1.2
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.
Status: current	Access: read-write
OBJECT-TYPE
	INTEGER	active(1), notInService(2), notReady(3), createAndGo(4), createAndWait(5), destroy(6)

reqResponseStatus		1.3.6.1.3.73.2.1.3.1.3
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.
Status: current	Access: read-only
OBJECT-TYPE
	INTEGER	unknown(1), inProgress(2), failedNoMatches(3), failedInvalidQuery(4), failedError(5), successUnderqualified(6), success(7)

reqMaxResponses		1.3.6.1.3.73.2.1.3.1.4
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).
Status: current	Access: read-write
OBJECT-TYPE
	INTEGER	1..100

reqUniqueMsgId		1.3.6.1.3.73.2.1.3.1.5
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.
Status: current	Access: read-write
OBJECT-TYPE
	DisplayString

reqInboundMsgId		1.3.6.1.3.73.2.1.3.1.6
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.
Status: current	Access: read-write
OBJECT-TYPE
	DisplayString

reqOutboundMsgId		1.3.6.1.3.73.2.1.3.1.7
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.
Status: current	Access: read-write
OBJECT-TYPE
	DisplayString

reqInboundOriginator		1.3.6.1.3.73.2.1.3.1.8
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.
Status: current	Access: read-write
OBJECT-TYPE
	DisplayString

reqOutboundOriginator		1.3.6.1.3.73.2.1.3.1.9
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.
Status: current	Access: read-write
OBJECT-TYPE
	DisplayString

reqOriginatorNameForm		1.3.6.1.3.73.2.1.3.1.10
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.
Status: current	Access: read-write
OBJECT-TYPE
	NameForm

reqInboundRecipient		1.3.6.1.3.73.2.1.3.1.11
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.
Status: current	Access: read-write
OBJECT-TYPE
	DisplayString

reqOutboundRecipient		1.3.6.1.3.73.2.1.3.1.12
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.
Status: current	Access: read-write
OBJECT-TYPE
	DisplayString

reqRecipientNameForm		1.3.6.1.3.73.2.1.3.1.13
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.
Status: current	Access: read-write
OBJECT-TYPE
	NameForm

reqSubject		1.3.6.1.3.73.2.1.3.1.14
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.
Status: current	Access: read-write
OBJECT-TYPE
	DisplayString

reqMinMsgSize		1.3.6.1.3.73.2.1.3.1.15
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.
Status: current	Access: read-write
OBJECT-TYPE
	INTEGER	1..2147483647

reqMaxMsgSize		1.3.6.1.3.73.2.1.3.1.16
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.
Status: current	Access: read-write
OBJECT-TYPE
	INTEGER	1..2147483647

reqEarliestArrivalTime		1.3.6.1.3.73.2.1.3.1.17
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.
Status: current	Access: read-write
OBJECT-TYPE
	DateAndTime

reqLatestArrivalTime		1.3.6.1.3.73.2.1.3.1.18
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.
Status: current	Access: read-write
OBJECT-TYPE
	DateAndTime

reqDispositionStatus		1.3.6.1.3.73.2.1.3.1.19
Specifies the disposition status of the message for a particular recipient. Set to 'unknown(1)' if unknown or irrelevant to the query.
Status: current	Access: read-write
OBJECT-TYPE
	DispositionStatus

reqMsgType		1.3.6.1.3.73.2.1.3.1.20
The type of message to be tracked. Set to 'any(1)' if message type is unknown or irrelevant to the query.
Status: current	Access: read-write
OBJECT-TYPE
	MsgType

reqCollapseRecipients		1.3.6.1.3.73.2.1.3.1.21
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.
Status: current	Access: read-write
OBJECT-TYPE
	INTEGER	false(1), true(2)

reqFailureReason		1.3.6.1.3.73.2.1.3.1.22
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)'.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

msgTrackResponseTable		1.3.6.1.3.73.2.1.4
The table holding the response to all active message tracking requests.
Status: current	Access: not-accessible
OBJECT-TYPE
	SEQUENCE OF
		MsgTrackResponseEntry

msgTrackResponseEntry		1.3.6.1.3.73.2.1.4.1
The entry associated with each response to a request for message information.
Status: current	Access: not-accessible
OBJECT-TYPE
	MsgTrackResponseEntry

respEntryIndex		1.3.6.1.3.73.2.1.4.1.1
The primary integer index into the msgTrackResponseTable table. It matches the value of reqEntryIndex for the original request.
Status: current	Access: read-only
OBJECT-TYPE
	INTEGER	1..2147483647

respMsgIndex		1.3.6.1.3.73.2.1.4.1.2
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.
Status: current	Access: read-only
OBJECT-TYPE
	INTEGER	1..2147483647

respDispositionStatus		1.3.6.1.3.73.2.1.4.1.3
Indicates the disposition of this message by this MTA for this recipient.
Status: current	Access: read-only
OBJECT-TYPE
	DispositionStatus

rspDispositionTime		1.3.6.1.3.73.2.1.4.1.4
Time at which this MTA disposed of this message for this recipient.
Status: current	Access: read-only
OBJECT-TYPE
	DateAndTime

respNextHopMta		1.3.6.1.3.73.2.1.4.1.5
Name of the MTA to which this message was sent. MADMAN-compliant MTA's should be addressed in the form '(::)'.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respPrevHopMta		1.3.6.1.3.73.2.1.4.1.6
Name of the MTA from which this message was received. MADMAN- compliant MTA's should be addressed in the form '(::)'.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respNonDeliveryReason		1.3.6.1.3.73.2.1.4.1.7
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.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respMsgArrivalTime		1.3.6.1.3.73.2.1.4.1.8
Represents the time at which this message for this recipient arrived at this MTA.
Status: current	Access: read-only
OBJECT-TYPE
	DateAndTime

respMsgSize		1.3.6.1.3.73.2.1.4.1.9
Size of the message in kilo-octets.
Status: current	Access: read-only
OBJECT-TYPE
	INTEGER	1..2147483647

respMsgPriority		1.3.6.1.3.73.2.1.4.1.10
Textual representation of the priority of the message. No attempt is made to normalize these values across disparate messaging technologies.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respUniqueMsgId		1.3.6.1.3.73.2.1.4.1.11
The unique message identifier that the MTA assigned internally to the message.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respInboundMsgId		1.3.6.1.3.73.2.1.4.1.12
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.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respOutboundMsgId		1.3.6.1.3.73.2.1.4.1.13
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.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respInboundOriginator		1.3.6.1.3.73.2.1.4.1.14
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.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respOutboundOriginator		1.3.6.1.3.73.2.1.4.1.15
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.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respInboundRecipient		1.3.6.1.3.73.2.1.4.1.16
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..
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respOutboundRecipient		1.3.6.1.3.73.2.1.4.1.17
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.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respSupplementalInformation		1.3.6.1.3.73.2.1.4.1.18
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.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respSubject		1.3.6.1.3.73.2.1.4.1.19
The full text of the subject of the tracked message
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString

respMsgType		1.3.6.1.3.73.2.1.4.1.20
The type of the tracked message
Status: current	Access: read-only
OBJECT-TYPE
	MsgType

messageTrackingConformance		1.3.6.1.3.73.2.1.5
OBJECT IDENTIFIER

messageTrackingGroups		1.3.6.1.3.73.2.1.5.1
OBJECT IDENTIFIER

messageTrackingCompliances		1.3.6.1.3.73.2.1.5.2
OBJECT IDENTIFIER

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.
Status: current	Access: read-only
MODULE-COMPLIANCE

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.
Status: current	Access: read-only
MODULE-COMPLIANCE

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.
Status: current	Access: read-only
MODULE-COMPLIANCE

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.
Status: current	Access: read-only
MODULE-COMPLIANCE

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.
Status: current	Access: read-only
OBJECT-GROUP

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.
Status: current	Access: read-only
OBJECT-GROUP

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.
Status: current	Access: read-only
OBJECT-GROUP

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.
Status: current	Access: read-only
OBJECT-GROUP