MTA-MIB
AI MIB Summary
The MTA-MIB provides standardized SNMP objects to monitor the operational status, queue depths, and message transfer statistics of Message Transfer Agents (MTAs) within email infrastructure. It enables administrators to track delivery success rates, queue backlogs, and connection states for SMTP/ESMTP services to ensure mail system reliability.
The MIB module describing Message Transfer Agents (MTAs)
Main OID:
mta.1.3.6.1.2.1.28
81
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
81 total| Object Name |
|---|
mtaThe MIB module describing Message Transfer Agents (MTAs) MODULE-IDENTITY .1.3.6.1.2.1.28 |
mtaTableThe table holding information specific to an MTA. SEQUENCE OF MtaEntry .1.3.6.1.2.1.28.1 |
mtaEntryThe entry associated with each MTA. MtaEntry .1.3.6.1.2.1.28.1.1 |
mtaReceivedMessagesThe 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.ro Counter32 .1.3.6.1.2.1.28.1.1.1 |
mtaStoredMessagesThe 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.ro Gauge32 .1.3.6.1.2.1.28.1.1.2 |
mtaTransmittedMessagesThe 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.ro Counter32 .1.3.6.1.2.1.28.1.1.3 |
mtaReceivedVolumeThe 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.ro Counter32 UNITS "K-octets" .1.3.6.1.2.1.28.1.1.4 |
mtaStoredVolumeThe 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.ro Gauge32 UNITS "K-octets" .1.3.6.1.2.1.28.1.1.5 |
mtaTransmittedVolumeThe 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.ro Counter32 UNITS "K-octets" .1.3.6.1.2.1.28.1.1.6 |
mtaReceivedRecipientsThe 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.ro Counter32 .1.3.6.1.2.1.28.1.1.7 |
mtaStoredRecipientsThe 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.ro Gauge32 .1.3.6.1.2.1.28.1.1.8 |
mtaTransmittedRecipientsThe 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.ro Counter32 .1.3.6.1.2.1.28.1.1.9 |
mtaSuccessfulConvertedMessagesThe number of messages that have been successfully converted from one form to another since MTA initialization.ro Counter32 .1.3.6.1.2.1.28.1.1.10 |
mtaFailedConvertedMessagesThe number of messages for which an unsuccessful attempt was made to convert them from one form to another since MTA initialization.ro Counter32 .1.3.6.1.2.1.28.1.1.11 |
mtaLoopsDetectedA 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.ro Counter32 .1.3.6.1.2.1.28.1.1.12 |
mtaGroupTableThe table holding information specific to each MTA group. SEQUENCE OF MtaGroupEntry .1.3.6.1.2.1.28.2 |
mtaGroupEntryThe entry associated with each MTA group. MtaGroupEntry .1.3.6.1.2.1.28.2.1 |
mtaGroupIndexThe index associated with a group for a given MTA. INTEGER .1.3.6.1.2.1.28.2.1.1 |
mtaGroupReceivedMessagesThe number of messages received to this group since group creation.ro Counter32 .1.3.6.1.2.1.28.2.1.2 |
mtaGroupRejectedMessagesThe number of messages rejected by this group since group creation.ro Counter32 .1.3.6.1.2.1.28.2.1.3 |
mtaGroupStoredMessagesThe total number of messages currently stored in this group's queue.ro Gauge32 .1.3.6.1.2.1.28.2.1.4 |
mtaGroupTransmittedMessagesThe number of messages transmitted by this group since group creation.ro Counter32 .1.3.6.1.2.1.28.2.1.5 |
mtaGroupReceivedVolumeThe 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.ro Counter32 UNITS "K-octets" .1.3.6.1.2.1.28.2.1.6 |
mtaGroupStoredVolumeThe 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.ro Gauge32 UNITS "K-octets" .1.3.6.1.2.1.28.2.1.7 |
mtaGroupTransmittedVolumeThe 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.ro Counter32 UNITS "K-octets" .1.3.6.1.2.1.28.2.1.8 |
mtaGroupReceivedRecipientsThe 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.ro Counter32 .1.3.6.1.2.1.28.2.1.9 |
mtaGroupStoredRecipientsThe 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.ro Gauge32 .1.3.6.1.2.1.28.2.1.10 |
mtaGroupTransmittedRecipientsThe 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.ro Counter32 .1.3.6.1.2.1.28.2.1.11 |
mtaGroupOldestMessageStoredTime since the oldest message in this group's queue was placed in the queue.ro TimeInterval (SNMPv2-TC) .1.3.6.1.2.1.28.2.1.12 |
mtaGroupInboundAssociationsThe number of current associations to the group, where the group is the responder.ro Gauge32 .1.3.6.1.2.1.28.2.1.13 |
mtaGroupOutboundAssociationsThe number of current associations to the group, where the group is the initiator.ro Gauge32 .1.3.6.1.2.1.28.2.1.14 |
mtaGroupAccumulatedInboundAssociationsThe total number of associations to the group since group creation, where the MTA was the responder.ro Counter32 .1.3.6.1.2.1.28.2.1.15 |
mtaGroupAccumulatedOutboundAssociationsThe total number of associations from the group since group creation, where the MTA was the initiator.ro Counter32 .1.3.6.1.2.1.28.2.1.16 |
mtaGroupLastInboundActivityTime since the last time that this group had an active inbound association for purposes of message reception.ro TimeInterval (SNMPv2-TC) .1.3.6.1.2.1.28.2.1.17 |
mtaGroupLastOutboundActivityTime since the last time that this group had a successful outbound association for purposes of message delivery.ro TimeInterval (SNMPv2-TC) .1.3.6.1.2.1.28.2.1.18 |
mtaGroupRejectedInboundAssociationsThe total number of inbound associations the group has rejected, since group creation. Rejected associations are not counted in the accumulated association totals.ro Counter32 .1.3.6.1.2.1.28.2.1.19 |
mtaGroupFailedOutboundAssociationsThe 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.ro Counter32 .1.3.6.1.2.1.28.2.1.20 |
mtaGroupInboundRejectionReasonThe 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'.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.28.2.1.21 |
mtaGroupOutboundConnectFailureReasonThe 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'.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.28.2.1.22 |
mtaGroupScheduledRetryThe amount of time until this group is next scheduled to attempt to make an association.ro TimeInterval (SNMPv2-TC) .1.3.6.1.2.1.28.2.1.23 |
mtaGroupMailProtocolAn 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.ro OBJECT IDENTIFIER .1.3.6.1.2.1.28.2.1.24 |
mtaGroupNameA 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.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.28.2.1.25 |
mtaGroupSuccessfulConvertedMessagesThe number of messages that have been successfully converted from one form to another in this group since group creation.ro Counter32 .1.3.6.1.2.1.28.2.1.26 |
mtaGroupFailedConvertedMessagesThe number of messages for which an unsuccessful attempt was made to convert them from one form to another in this group since group creation.ro Counter32 .1.3.6.1.2.1.28.2.1.27 |
mtaGroupDescriptionA description of the group's purpose. This information is intended to identify the group in a status display.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.28.2.1.28 |
mtaGroupURLA URL pointing to a description of the group. This information is intended to identify and briefly describe the group in a status display.ro URLString (NETWORK-SERVICES-MIB) .1.3.6.1.2.1.28.2.1.29 |
mtaGroupCreationTimeTime since this group was first created.ro TimeInterval (SNMPv2-TC) .1.3.6.1.2.1.28.2.1.30 |
mtaGroupHierarchyDescribes 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.ro INTEGER (-2147483648..2147483647) .1.3.6.1.2.1.28.2.1.31 |
mtaGroupOldestMessageIdMessage 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.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.28.2.1.32 |
mtaGroupLoopsDetectedA 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.ro Counter32 .1.3.6.1.2.1.28.2.1.33 |
mtaGroupLastOutboundAssociationAttemptTime since the last time that this group attempted to make an outbound association for purposes of message delivery.ro TimeInterval (SNMPv2-TC) .1.3.6.1.2.1.28.2.1.34 |
mtaGroupAssociationTableThe table holding information regarding the associations for each MTA group. SEQUENCE OF MtaGroupAssociationEntry .1.3.6.1.2.1.28.3 |
mtaGroupAssociationEntryThe entry holding information regarding the associations for each MTA group. MtaGroupAssociationEntry .1.3.6.1.2.1.28.3.1 |
mtaGroupAssociationIndexReference into association table to allow correlation of this group's active associations with the association table.ro INTEGER .1.3.6.1.2.1.28.3.1.1 |
mtaConformance OBJECT IDENTIFIER .1.3.6.1.2.1.28.4 |
mtaGroups OBJECT IDENTIFIER .1.3.6.1.2.1.28.4.1 |
mtaRFC2249GroupA collection of objects providing basic monitoring of MTAs. This group was originally defined in RFC 2249. Unknown .1.3.6.1.2.1.28.4.1.4 |
mtaRFC2249AssocGroupA collection of objects providing monitoring of MTA associations. This group was originally defined in RFC 2249. Unknown .1.3.6.1.2.1.28.4.1.5 |
mtaRFC2249ErrorGroupA collection of objects providing monitoring of detailed MTA errors. This group was originally defined in RFC 2249. Unknown .1.3.6.1.2.1.28.4.1.6 |
mtaRFC2789GroupA collection of objects providing basic monitoring of MTAs. This is the appropriate group for RFC 2789. Unknown .1.3.6.1.2.1.28.4.1.7 |
mtaRFC2789AssocGroupA collection of objects providing monitoring of MTA associations. This is the appropriate group for RFC 2789 association monitoring. Unknown .1.3.6.1.2.1.28.4.1.8 |
mtaRFC2789ErrorGroupA collection of objects providing monitoring of detailed MTA errors. This is the appropriate group for RFC 2789 error monitoring. Unknown .1.3.6.1.2.1.28.4.1.9 |
mtaRFC1566GroupA collection of objects providing basic monitoring of MTAs. This is the original set of such objects defined in RFC 1566. Unknown .1.3.6.1.2.1.28.4.1.10 |
mtaRFC1566AssocGroupA collection of objects providing monitoring of MTA associations. This is the original set of such objects defined in RFC 1566. Unknown .1.3.6.1.2.1.28.4.1.11 |
mtaCompliances OBJECT IDENTIFIER .1.3.6.1.2.1.28.4.2 |
mtaComplianceThe compliance statement for RFC 1566 implementations which support the Mail Monitoring MIB for basic monitoring of MTAs. Unknown .1.3.6.1.2.1.28.4.2.1 |
mtaAssocComplianceThe compliance statement for RFC 1566 implementations which support the Mail Monitoring MIB for monitoring of MTAs and their associations. Unknown .1.3.6.1.2.1.28.4.2.2 |
mtaRFC2249ComplianceThe compliance statement for RFC 2249 implementations which support the Mail Monitoring MIB for basic monitoring of MTAs. Unknown .1.3.6.1.2.1.28.4.2.5 |
mtaRFC2249AssocComplianceThe compliance statement for RFC 2249 implementations which support the Mail Monitoring MIB for monitoring of MTAs and their associations. Unknown .1.3.6.1.2.1.28.4.2.6 |
mtaRFC2249ErrorComplianceThe compliance statement for RFC 2249 implementations which support the Mail Monitoring MIB for monitoring of MTAs and detailed errors. Unknown .1.3.6.1.2.1.28.4.2.7 |
mtaRFC2249FullComplianceThe compliance statement for RFC 2249 implementations which support the full Mail Monitoring MIB for monitoring of MTAs, associations, and detailed errors. Unknown .1.3.6.1.2.1.28.4.2.8 |
mtaRFC2789ComplianceThe compliance statement for RFC 2789 implementations which support the Mail Monitoring MIB for basic monitoring of MTAs. Unknown .1.3.6.1.2.1.28.4.2.9 |
mtaRFC2789AssocComplianceThe compliance statement for RFC 2789 implementations which support the Mail Monitoring MIB for monitoring of MTAs and their associations. Unknown .1.3.6.1.2.1.28.4.2.10 |
mtaRFC2789ErrorComplianceThe compliance statement for RFC 2789 implementations which support the Mail Monitoring MIB for monitoring of MTAs and detailed errors. Unknown .1.3.6.1.2.1.28.4.2.11 |
mtaRFC2789FullComplianceThe compliance statement for RFC 2789 implementations which support the full Mail Monitoring MIB for monitoring of MTAs, associations, and detailed errors. Unknown .1.3.6.1.2.1.28.4.2.12 |
mtaGroupErrorTableThe table holding information regarding accumulated errors for each MTA group. SEQUENCE OF MtaGroupErrorEntry .1.3.6.1.2.1.28.5 |
mtaGroupErrorEntryThe entry holding information regarding accumulated errors for each MTA group. MtaGroupErrorEntry .1.3.6.1.2.1.28.5.1 |
mtaGroupInboundErrorCountCount 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.ro Counter32 .1.3.6.1.2.1.28.5.1.1 |
mtaGroupInternalErrorCountCount of the number of errors of a given type that have been accumulated in association with a particular group during internal MTA processing.ro Counter32 .1.3.6.1.2.1.28.5.1.2 |
mtaGroupOutboundErrorCountCount 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.ro Counter32 .1.3.6.1.2.1.28.5.1.3 |
mtaStatusCodeAn 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. INTEGER .1.3.6.1.2.1.28.5.1.4 |