MTA-MIB

File: MTA-MIB.mib (43601 bytes)

Imported modules

SNMPv2-SMI	SNMPv2-TC	SNMPv2-CONF
SNMP-FRAMEWORK-MIB	NETWORK-SERVICES-MIB

Imported symbols

OBJECT-TYPE	Counter32	Gauge32
MODULE-IDENTITY	mib-2	TimeInterval
MODULE-COMPLIANCE	OBJECT-GROUP	SnmpAdminString
applIndex	URLString

Defined Types

MtaEntry
SEQUENCE
	mtaReceivedMessages	Counter32
	mtaStoredMessages	Gauge32
	mtaTransmittedMessages	Counter32
	mtaReceivedVolume	Counter32
	mtaStoredVolume	Gauge32
	mtaTransmittedVolume	Counter32
	mtaReceivedRecipients	Counter32
	mtaStoredRecipients	Gauge32
	mtaTransmittedRecipients	Counter32
	mtaSuccessfulConvertedMessages	Counter32
	mtaFailedConvertedMessages	Counter32
	mtaLoopsDetected	Counter32

MtaGroupEntry
SEQUENCE
	mtaGroupIndex	INTEGER
	mtaGroupReceivedMessages	Counter32
	mtaGroupRejectedMessages	Counter32
	mtaGroupStoredMessages	Gauge32
	mtaGroupTransmittedMessages	Counter32
	mtaGroupReceivedVolume	Counter32
	mtaGroupStoredVolume	Gauge32
	mtaGroupTransmittedVolume	Counter32
	mtaGroupReceivedRecipients	Counter32
	mtaGroupStoredRecipients	Gauge32
	mtaGroupTransmittedRecipients	Counter32
	mtaGroupOldestMessageStored	TimeInterval
	mtaGroupInboundAssociations	Gauge32
	mtaGroupOutboundAssociations	Gauge32
	mtaGroupAccumulatedInboundAssociations	Counter32
	mtaGroupAccumulatedOutboundAssociations	Counter32
	mtaGroupLastInboundActivity	TimeInterval
	mtaGroupLastOutboundActivity	TimeInterval
	mtaGroupLastOutboundAssociationAttempt	TimeInterval
	mtaGroupRejectedInboundAssociations	Counter32
	mtaGroupFailedOutboundAssociations	Counter32
	mtaGroupInboundRejectionReason	SnmpAdminString
	mtaGroupOutboundConnectFailureReason	SnmpAdminString
	mtaGroupScheduledRetry	TimeInterval
	mtaGroupMailProtocol	OBJECT IDENTIFIER
	mtaGroupName	SnmpAdminString
	mtaGroupSuccessfulConvertedMessages	Counter32
	mtaGroupFailedConvertedMessages	Counter32
	mtaGroupDescription	SnmpAdminString
	mtaGroupURL	URLString
	mtaGroupCreationTime	TimeInterval
	mtaGroupHierarchy	INTEGER
	mtaGroupOldestMessageId	SnmpAdminString
	mtaGroupLoopsDetected	Counter32

MtaGroupAssociationEntry
SEQUENCE
	mtaGroupAssociationIndex	INTEGER

MtaGroupErrorEntry
SEQUENCE
	mtaStatusCode	INTEGER	4000000..5999999
	mtaGroupInboundErrorCount	Counter32
	mtaGroupInternalErrorCount	Counter32
	mtaGroupOutboundErrorCount	Counter32

Defined Values

mta		1.3.6.1.2.1.28
The MIB module describing Message Transfer Agents (MTAs)
MODULE-IDENTITY

mtaTable		1.3.6.1.2.1.28.1
The table holding information specific to an MTA.
Status: current	Access: not-accessible
OBJECT-TYPE
	SEQUENCE OF
		MtaEntry

mtaEntry		1.3.6.1.2.1.28.1.1
The entry associated with each MTA.
Status: current	Access: not-accessible
OBJECT-TYPE
	MtaEntry

mtaReceivedMessages		1.3.6.1.2.1.28.1.1.1
The number of messages received since MTA initialization. This includes messages transmitted to this MTA from other MTAs as well as messages that have been submitted to the MTA directly by end-users or applications.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaStoredMessages		1.3.6.1.2.1.28.1.1.2
The total number of messages currently stored in the MTA. This includes messages that are awaiting transmission to some other MTA or are waiting for delivery to an end-user or application.
Status: current	Access: read-only
OBJECT-TYPE
	Gauge32

mtaTransmittedMessages		1.3.6.1.2.1.28.1.1.3
The number of messages transmitted since MTA initialization. This includes messages that were transmitted to some other MTA or are waiting for delivery to an end-user or application.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaReceivedVolume		1.3.6.1.2.1.28.1.1.4
The total volume of messages received since MTA initialization, measured in kilo-octets. This volume should include all transferred data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA should use the number of kilo-octets of P2 data. This includes messages transmitted to this MTA from other MTAs as well as messages that have been submitted to the MTA directly by end-users or applications.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaStoredVolume		1.3.6.1.2.1.28.1.1.5
The total volume of messages currently stored in the MTA, measured in kilo-octets. This volume should include all stored data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA would use the number of kilo-octets of P2 data. This includes messages that are awaiting transmission to some other MTA or are waiting for delivery to an end-user or application.
Status: current	Access: read-only
OBJECT-TYPE
	Gauge32

mtaTransmittedVolume		1.3.6.1.2.1.28.1.1.6
The total volume of messages transmitted since MTA initialization, measured in kilo-octets. This volume should include all transferred data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA should use the number of kilo-octets of P2 data. This includes messages that were transmitted to some other MTA or are waiting for delivery to an end-user or application.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaReceivedRecipients		1.3.6.1.2.1.28.1.1.7
The total number of recipients specified in all messages received since MTA initialization. Recipients this MTA has no responsibility for, i.e. inactive envelope recipients or ones referred to in message headers, should not be counted even if information about such recipients is available. This includes messages transmitted to this MTA from other MTAs as well as messages that have been submitted to the MTA directly by end-users or applications.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaStoredRecipients		1.3.6.1.2.1.28.1.1.8
The total number of recipients specified in all messages currently stored in the MTA. Recipients this MTA has no responsibility for, i.e. inactive envelope recipients or ones referred to in message headers, should not be counted. This includes messages that are awaiting transmission to some other MTA or are waiting for delivery to an end-user or application.
Status: current	Access: read-only
OBJECT-TYPE
	Gauge32

mtaTransmittedRecipients		1.3.6.1.2.1.28.1.1.9
The total number of recipients specified in all messages transmitted since MTA initialization. Recipients this MTA had no responsibility for, i.e. inactive envelope recipients or ones referred to in message headers, should not be counted. This includes messages that were transmitted to some other MTA or are waiting for delivery to an end-user or application.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaSuccessfulConvertedMessages		1.3.6.1.2.1.28.1.1.10
The number of messages that have been successfully converted from one form to another since MTA initialization.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaFailedConvertedMessages		1.3.6.1.2.1.28.1.1.11
The number of messages for which an unsuccessful attempt was made to convert them from one form to another since MTA initialization.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaLoopsDetected		1.3.6.1.2.1.28.1.1.12
A message loop is defined as a situation where the MTA decides that a given message will never be delivered to one or more recipients and instead will continue to loop endlessly through one or more MTAs. This variable counts the number of times the MTA has detected such a situation since MTA initialization. Note that the mechanism MTAs use to detect loops (e.g., trace field counting, count of references to this MTA in a trace field, examination of DNS or other directory information, etc.), the level at which loops are detected (e.g., per message, per recipient, per directory entry, etc.), and the handling of a loop once it is detected (e.g., looping messages are held, looping messages are bounced or sent to the postmaster, messages that the MTA knows will loop won't be accepted, etc.) vary widely from one MTA to the next and cannot be inferred from this variable.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupTable		1.3.6.1.2.1.28.2
The table holding information specific to each MTA group.
Status: current	Access: not-accessible
OBJECT-TYPE
	SEQUENCE OF
		MtaGroupEntry

mtaGroupEntry		1.3.6.1.2.1.28.2.1
The entry associated with each MTA group.
Status: current	Access: not-accessible
OBJECT-TYPE
	MtaGroupEntry

mtaGroupIndex		1.3.6.1.2.1.28.2.1.1
The index associated with a group for a given MTA.
Status: current	Access: not-accessible
OBJECT-TYPE
	INTEGER	1..2147483647

mtaGroupReceivedMessages		1.3.6.1.2.1.28.2.1.2
The number of messages received to this group since group creation.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupRejectedMessages		1.3.6.1.2.1.28.2.1.3
The number of messages rejected by this group since group creation.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupStoredMessages		1.3.6.1.2.1.28.2.1.4
The total number of messages currently stored in this group's queue.
Status: current	Access: read-only
OBJECT-TYPE
	Gauge32

mtaGroupTransmittedMessages		1.3.6.1.2.1.28.2.1.5
The number of messages transmitted by this group since group creation.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupReceivedVolume		1.3.6.1.2.1.28.2.1.6
The total volume of messages received to this group since group creation, measured in kilo-octets. This volume should include all transferred data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA should use the number of kilo-octets of P2 data.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupStoredVolume		1.3.6.1.2.1.28.2.1.7
The total volume of messages currently stored in this group's queue, measured in kilo-octets. This volume should include all stored data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA would use the number of kilo-octets of P2 data.
Status: current	Access: read-only
OBJECT-TYPE
	Gauge32

mtaGroupTransmittedVolume		1.3.6.1.2.1.28.2.1.8
The total volume of messages transmitted by this group since group creation, measured in kilo-octets. This volume should include all transferred data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA should use the number of kilo-octets of P2 data.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupReceivedRecipients		1.3.6.1.2.1.28.2.1.9
The total number of recipients specified in all messages received to this group since group creation. Recipients this MTA has no responsibility for should not be counted.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupStoredRecipients		1.3.6.1.2.1.28.2.1.10
The total number of recipients specified in all messages currently stored in this group's queue. Recipients this MTA has no responsibility for should not be counted.
Status: current	Access: read-only
OBJECT-TYPE
	Gauge32

mtaGroupTransmittedRecipients		1.3.6.1.2.1.28.2.1.11
The total number of recipients specified in all messages transmitted by this group since group creation. Recipients this MTA had no responsibility for should not be counted.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupOldestMessageStored		1.3.6.1.2.1.28.2.1.12
Time since the oldest message in this group's queue was placed in the queue.
Status: current	Access: read-only
OBJECT-TYPE
	TimeInterval

mtaGroupInboundAssociations		1.3.6.1.2.1.28.2.1.13
The number of current associations to the group, where the group is the responder.
Status: current	Access: read-only
OBJECT-TYPE
	Gauge32

mtaGroupOutboundAssociations		1.3.6.1.2.1.28.2.1.14
The number of current associations to the group, where the group is the initiator.
Status: current	Access: read-only
OBJECT-TYPE
	Gauge32

mtaGroupAccumulatedInboundAssociations		1.3.6.1.2.1.28.2.1.15
The total number of associations to the group since group creation, where the MTA was the responder.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupAccumulatedOutboundAssociations		1.3.6.1.2.1.28.2.1.16
The total number of associations from the group since group creation, where the MTA was the initiator.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupLastInboundActivity		1.3.6.1.2.1.28.2.1.17
Time since the last time that this group had an active inbound association for purposes of message reception.
Status: current	Access: read-only
OBJECT-TYPE
	TimeInterval

mtaGroupLastOutboundActivity		1.3.6.1.2.1.28.2.1.18
Time since the last time that this group had a successful outbound association for purposes of message delivery.
Status: current	Access: read-only
OBJECT-TYPE
	TimeInterval

mtaGroupLastOutboundAssociationAttempt		1.3.6.1.2.1.28.2.1.34
Time since the last time that this group attempted to make an outbound association for purposes of message delivery.
Status: current	Access: read-only
OBJECT-TYPE
	TimeInterval

mtaGroupRejectedInboundAssociations		1.3.6.1.2.1.28.2.1.19
The total number of inbound associations the group has rejected, since group creation. Rejected associations are not counted in the accumulated association totals.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupFailedOutboundAssociations		1.3.6.1.2.1.28.2.1.20
The total number associations where the group was the initiator and association establishment has failed, since group creation. Failed associations are not counted in the accumulated association totals.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupInboundRejectionReason		1.3.6.1.2.1.28.2.1.21
The failure reason, if any, for the last association this group refused to respond to. If no association attempt has been made since the MTA was initialized the value should be 'never'.
Status: current	Access: read-only
OBJECT-TYPE
	SnmpAdminString

mtaGroupOutboundConnectFailureReason		1.3.6.1.2.1.28.2.1.22
The failure reason, if any, for the last association attempt this group initiated. If no association attempt has been made since the MTA was initialized the value should be 'never'.
Status: current	Access: read-only
OBJECT-TYPE
	SnmpAdminString

mtaGroupScheduledRetry		1.3.6.1.2.1.28.2.1.23
The amount of time until this group is next scheduled to attempt to make an association.
Status: current	Access: read-only
OBJECT-TYPE
	TimeInterval

mtaGroupMailProtocol		1.3.6.1.2.1.28.2.1.24
An identification of the protocol being used by this group. For an group employing OSI protocols, this will be the Application Context. For Internet applications, OID values of the form {applTCPProtoID port} or {applUDPProtoID port} are used for TCP-based and UDP-based protocols, respectively. In either case 'port' corresponds to the primary port number being used by the protocol. The usual IANA procedures may be used to register ports for new protocols. applTCPProtoID and applUDPProtoID are defined in the NETWORK-SERVICES-MIB, RFC 2788.
Status: current	Access: read-only
OBJECT-TYPE
	OBJECT IDENTIFIER

mtaGroupName		1.3.6.1.2.1.28.2.1.25
A descriptive name for the group. If this group connects to a single remote MTA this should be the name of that MTA. If this in turn is an Internet MTA this should be the domain name. For an OSI MTA it should be the string encoded distinguished name of the managed object using the format defined in RFC 2253. For X.400(1984) MTAs which do not have a Distinguished Name, the RFC 2156 syntax 'mta in globalid' used in X400-Received: fields can be used.
Status: current	Access: read-only
OBJECT-TYPE
	SnmpAdminString

mtaGroupSuccessfulConvertedMessages		1.3.6.1.2.1.28.2.1.26
The number of messages that have been successfully converted from one form to another in this group since group creation.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupFailedConvertedMessages		1.3.6.1.2.1.28.2.1.27
The number of messages for which an unsuccessful attempt was made to convert them from one form to another in this group since group creation.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupDescription		1.3.6.1.2.1.28.2.1.28
A description of the group's purpose. This information is intended to identify the group in a status display.
Status: current	Access: read-only
OBJECT-TYPE
	SnmpAdminString

mtaGroupURL		1.3.6.1.2.1.28.2.1.29
A URL pointing to a description of the group. This information is intended to identify and briefly describe the group in a status display.
Status: current	Access: read-only
OBJECT-TYPE
	URLString

mtaGroupCreationTime		1.3.6.1.2.1.28.2.1.30
Time since this group was first created.
Status: current	Access: read-only
OBJECT-TYPE
	TimeInterval

mtaGroupHierarchy		1.3.6.1.2.1.28.2.1.31
Describes how this group fits into the hierarchy. A positive value is interpreted as an mtaGroupIndex value for some other group whose variables include those of this group (and usually others). A negative value is interpreted as a group collection code: Groups with common negative hierarchy values comprise one particular breakdown of MTA activity as a whole. A zero value means that this MIB implementation doesn't implement hierarchy indicators and thus the overall group hierarchy cannot be determined.
Status: current	Access: read-only
OBJECT-TYPE
	INTEGER	-2147483648..2147483647

mtaGroupOldestMessageId		1.3.6.1.2.1.28.2.1.32
Message ID of the oldest message in the group's queue. Whenever possible this should be in the form of an RFC 822 msg-id; X.400 may convert X.400 message identifiers to this form by following the rules laid out in RFC2156.
Status: current	Access: read-only
OBJECT-TYPE
	SnmpAdminString

mtaGroupLoopsDetected		1.3.6.1.2.1.28.2.1.33
A message loop is defined as a situation where the MTA decides that a given message will never be delivered to one or more recipients and instead will continue to loop endlessly through one or more MTAs. This variable counts the number of times the MTA has detected such a situation in conjunction with something associated with this group since group creation. Note that the mechanism MTAs use to detect loops (e.g., trace field counting, count of references to this MTA in a trace field, examination of DNS or other directory information, etc.), the level at which loops are detected (e.g., per message, per recipient, per directory entry, etc.), and the handling of a loop once it is detected (e.g., looping messages are held, looping messages are bounced or sent to the postmaster, messages that the MTA knows will loop won't be accepted, etc.) vary widely from one MTA to the next and cannot be inferred from this variable.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupAssociationTable		1.3.6.1.2.1.28.3
The table holding information regarding the associations for each MTA group.
Status: current	Access: not-accessible
OBJECT-TYPE
	SEQUENCE OF
		MtaGroupAssociationEntry

mtaGroupAssociationEntry		1.3.6.1.2.1.28.3.1
The entry holding information regarding the associations for each MTA group.
Status: current	Access: not-accessible
OBJECT-TYPE
	MtaGroupAssociationEntry

mtaGroupAssociationIndex		1.3.6.1.2.1.28.3.1.1
Reference into association table to allow correlation of this group's active associations with the association table.
Status: current	Access: read-only
OBJECT-TYPE
	INTEGER	1..2147483647

mtaGroupErrorTable		1.3.6.1.2.1.28.5
The table holding information regarding accumulated errors for each MTA group.
Status: current	Access: not-accessible
OBJECT-TYPE
	SEQUENCE OF
		MtaGroupErrorEntry

mtaGroupErrorEntry		1.3.6.1.2.1.28.5.1
The entry holding information regarding accumulated errors for each MTA group.
Status: current	Access: not-accessible
OBJECT-TYPE
	MtaGroupErrorEntry

mtaGroupInboundErrorCount		1.3.6.1.2.1.28.5.1.1
Count of the number of errors of a given type that have been accumulated in association with a particular group while processing incoming messages. In the case of SMTP these will typically be errors reporting by an SMTP server to the remote client; in the case of X.400 these will typically be errors encountered while processing an incoming message.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupInternalErrorCount		1.3.6.1.2.1.28.5.1.2
Count of the number of errors of a given type that have been accumulated in association with a particular group during internal MTA processing.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaGroupOutboundErrorCount		1.3.6.1.2.1.28.5.1.3
Count of the number of errors of a given type that have been accumulated in association with a particular group's outbound connection activities. In the case of an SMTP client these will typically be errors reported while attempting to contact or while communicating with the remote SMTP server. In the case of X.400 these will typically be errors encountered while constructing or attempting to deliver an outgoing message.
Status: current	Access: read-only
OBJECT-TYPE
	Counter32

mtaStatusCode		1.3.6.1.2.1.28.5.1.4
An index capable of representing an Enhanced Mail System Status Code. Enhanced Mail System Status Codes are defined in RFC 1893. These codes have the form class.subject.detail Here 'class' is either 2, 4, or 5 and both 'subject' and 'detail' are integers in the range 0..999. Given a status code the corresponding index value is defined to be ((class * 1000) + subject) * 1000 + detail. Both SMTP error response codes and X.400 reason and diagnostic codes can be mapped into these codes, resulting in a namespace capable of describing most error conditions a mail system encounters in a generic yet detailed way.
Status: current	Access: not-accessible
OBJECT-TYPE
	INTEGER	4000000..5999999

mtaConformance		1.3.6.1.2.1.28.4
OBJECT IDENTIFIER

mtaGroups		1.3.6.1.2.1.28.4.1
OBJECT IDENTIFIER

mtaCompliances		1.3.6.1.2.1.28.4.2
OBJECT IDENTIFIER

mtaCompliance		1.3.6.1.2.1.28.4.2.1
The compliance statement for RFC 1566 implementations which support the Mail Monitoring MIB for basic monitoring of MTAs.
Status: current	Access: not-accessible
MODULE-COMPLIANCE

mtaAssocCompliance		1.3.6.1.2.1.28.4.2.2
The compliance statement for RFC 1566 implementations which support the Mail Monitoring MIB for monitoring of MTAs and their associations.
Status: current	Access: not-accessible
MODULE-COMPLIANCE

mtaRFC2249Compliance		1.3.6.1.2.1.28.4.2.5
The compliance statement for RFC 2249 implementations which support the Mail Monitoring MIB for basic monitoring of MTAs.
Status: current	Access: not-accessible
MODULE-COMPLIANCE

mtaRFC2249AssocCompliance		1.3.6.1.2.1.28.4.2.6
The compliance statement for RFC 2249 implementations which support the Mail Monitoring MIB for monitoring of MTAs and their associations.
Status: current	Access: not-accessible
MODULE-COMPLIANCE

mtaRFC2249ErrorCompliance		1.3.6.1.2.1.28.4.2.7
The compliance statement for RFC 2249 implementations which support the Mail Monitoring MIB for monitoring of MTAs and detailed errors.
Status: current	Access: not-accessible
MODULE-COMPLIANCE

mtaRFC2249FullCompliance		1.3.6.1.2.1.28.4.2.8
The compliance statement for RFC 2249 implementations which support the full Mail Monitoring MIB for monitoring of MTAs, associations, and detailed errors.
Status: current	Access: not-accessible
MODULE-COMPLIANCE

mtaRFC2789Compliance		1.3.6.1.2.1.28.4.2.9
The compliance statement for RFC 2789 implementations which support the Mail Monitoring MIB for basic monitoring of MTAs.
Status: current	Access: not-accessible
MODULE-COMPLIANCE

mtaRFC2789AssocCompliance		1.3.6.1.2.1.28.4.2.10
The compliance statement for RFC 2789 implementations which support the Mail Monitoring MIB for monitoring of MTAs and their associations.
Status: current	Access: not-accessible
MODULE-COMPLIANCE

mtaRFC2789ErrorCompliance		1.3.6.1.2.1.28.4.2.11
The compliance statement for RFC 2789 implementations which support the Mail Monitoring MIB for monitoring of MTAs and detailed errors.
Status: current	Access: not-accessible
MODULE-COMPLIANCE

mtaRFC2789FullCompliance		1.3.6.1.2.1.28.4.2.12
The compliance statement for RFC 2789 implementations which support the full Mail Monitoring MIB for monitoring of MTAs, associations, and detailed errors.
Status: current	Access: not-accessible
MODULE-COMPLIANCE

mtaRFC1566Group		1.3.6.1.2.1.28.4.1.10
A collection of objects providing basic monitoring of MTAs. This is the original set of such objects defined in RFC 1566.
Status: current	Access: not-accessible
OBJECT-GROUP

mtaRFC1566AssocGroup		1.3.6.1.2.1.28.4.1.11
A collection of objects providing monitoring of MTA associations. This is the original set of such objects defined in RFC 1566.
Status: current	Access: not-accessible
OBJECT-GROUP

mtaRFC2249Group		1.3.6.1.2.1.28.4.1.4
A collection of objects providing basic monitoring of MTAs. This group was originally defined in RFC 2249.
Status: current	Access: not-accessible
OBJECT-GROUP

mtaRFC2249AssocGroup		1.3.6.1.2.1.28.4.1.5
A collection of objects providing monitoring of MTA associations. This group was originally defined in RFC 2249.
Status: current	Access: not-accessible
OBJECT-GROUP

mtaRFC2249ErrorGroup		1.3.6.1.2.1.28.4.1.6
A collection of objects providing monitoring of detailed MTA errors. This group was originally defined in RFC 2249.
Status: current	Access: not-accessible
OBJECT-GROUP

mtaRFC2789Group		1.3.6.1.2.1.28.4.1.7
A collection of objects providing basic monitoring of MTAs. This is the appropriate group for RFC 2789.
Status: current	Access: not-accessible
OBJECT-GROUP

mtaRFC2789AssocGroup		1.3.6.1.2.1.28.4.1.8
A collection of objects providing monitoring of MTA associations. This is the appropriate group for RFC 2789 association monitoring.
Status: current	Access: not-accessible
OBJECT-GROUP

mtaRFC2789ErrorGroup		1.3.6.1.2.1.28.4.1.9
A collection of objects providing monitoring of detailed MTA errors. This is the appropriate group for RFC 2789 error monitoring.
Status: current	Access: not-accessible
OBJECT-GROUP