-- Network Working Group N. Freed
-- Request for Comments: 2249 Innosoft
-- Obsoletes: 1566 S. Kille
-- Category: Standards Track ISODE Consortium
-- January 1998-- Mail Monitoring MIBMTA-MIB DEFINITIONS::=BEGINIMPORTSOBJECT-TYPE,Counter32,Gauge32,MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI
DisplayString,TimeIntervalFROM SNMPv2-TC
MODULE-COMPLIANCE,OBJECT-GROUPFROM SNMPv2-CONF
applIndex,URLString
FROM NETWORK-SERVICES-MIB;mta MODULE-IDENTITYLAST-UPDATED"9708170000Z"ORGANIZATION"IETF Mail and Directory Management Working Group"CONTACT-INFO" Ned Freed
Postal: Innosoft International, Inc.
1050 Lakes Drive
West Covina, CA 91790
US
Tel: +1 626 919 3600
Fax: +1 626 919 3614
E-Mail: ned.freed@innosoft.com"DESCRIPTION"The MIB module describing Message Transfer Agents (MTAs)"REVISION"9311280000Z"DESCRIPTION"The original version of this MIB was published in RFC 1566"::={mib-2 28}mtaTable OBJECT-TYPESYNTAXSEQUENCEOF MtaEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The table holding information specific to an MTA."::={mta 1}mtaStatusCode OBJECT-TYPESYNTAXINTEGER(4000000..5999999)
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An index capable of representing an Enhanced Mail System
Status Code. Enhanced Mail System Status Codes are
defined in RFC 1893 [14]. 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."::={mta 6}mtaEntry OBJECT-TYPESYNTAX MtaEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The entry associated with each MTA."INDEX{applIndex}::={mtaTable 1}
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}mtaReceivedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaEntry 1}mtaStoredMessages OBJECT-TYPESYNTAXGauge32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaEntry 2}mtaTransmittedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaEntry 3}mtaReceivedVolume OBJECT-TYPESYNTAXCounter32UNITS"K-octets"
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaEntry 4}mtaStoredVolume OBJECT-TYPESYNTAXGauge32UNITS"K-octets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaEntry 5}mtaTransmittedVolume OBJECT-TYPESYNTAXCounter32UNITS"K-octets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaEntry 6}mtaReceivedRecipients OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaEntry 7}mtaStoredRecipients OBJECT-TYPESYNTAXGauge32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaEntry 8}mtaTransmittedRecipients OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-only
STATUScurrentDESCRIPTION"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."::={mtaEntry 9}mtaSuccessfulConvertedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of messages that have been successfully
converted from one form to another since MTA
initialization."::={mtaEntry 10}mtaFailedConvertedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of messages for which an unsuccessful
attempt was made to convert them from one form to
another since MTA initialization."::={mtaEntry 11}mtaLoopsDetected OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaEntry 12}-- MTAs typically group inbound reception, queue storage, and
-- outbound transmission in some way, rather than accounting for
-- such operations only across the MTA as a whole. In the most
-- extreme case separate information will be maintained for each
-- different entity that receives messages and for each entity
-- the MTA stores messages for and delivers messages to. Other
-- MTAs may elect to treat all reception equally, all queue
-- storage equally, all deliveries equally, or some combination
-- of this. Overlapped groupings are also possible, where an MTA
-- decomposes its traffic in different ways for different
-- purposes.-- In any case, a grouping abstraction is an extremely useful for
-- breaking down the activities of an MTA. For purposes of
-- labelling this will be called a "group" in this MIB.-- Each group contains all the variables needed to monitor all
-- aspects of an MTA's operation. However, the fact that all
-- groups contain all possible variables does not imply that all
-- groups must use all possible variables. For example, a single
-- group might be used to monitor only one kind of event (inbound
-- processing, outbound processing, or storage). In this sort of
-- configuration all unused counters would be inaccessible; e.g.,
-- returning either a noSuchName error (for an SNMPv1 get), or a
-- noSuchInstance exception (for an SNMPv2 get).-- Groups can be created at any time after MTA initialization. Once
-- a group is created it should not be deleted or its mtaGroupIndex
-- changed unless the MTA is reinitialized.-- Groups are not necessarily mutually exclusive. A given event may
-- be recorded by more than one group, a message may be seen as
-- stored by more than one group, and so on. Groups should be all
-- inclusive, however: if groups are implemented all aspects of an
-- MTA's operation should be registered in at least one group. This
-- freedom lets implementors use different sets of groups to
-- provide differents "views" of an MTA.-- The possibility of overlap between groups means that summing
-- variables across groups may not produce values equal to those in
-- the mtaTable. mtaTable should always provide accurate information
-- about the MTA as a whole.-- The term "channel" is often used in MTA implementations; channels
-- are usually, but not always, equivalent to a group. However,
-- this MIB does not use the term "channel" because there is no
-- requirement that an MTA supporting this MIB has to map its
-- "channel" abstraction one-to-one onto the MIB's group abstration.-- An MTA may create a group or group of groups at any time. Once
-- created, however, an MTA cannot delete an entry for a group from
-- the group table. Deletation is only allowed when the MTA is
-- reinitialized, and is not required even then. This restriction
-- is imposed so that monitoring agents can rely on group
-- assignments being consistent across multiple query operations.-- Groups may be laid out so as to form a hierarchical arrangement,
-- with some groups acting as subgroups for other groups.
-- Alternately, disjoint groups of groups may be used to provide
-- different sorts of "snapshots" of MTA operation. The
-- mtaGroupHierarchy variable provides an indication of how each
-- group fits into the overall arrangement being used.mtaGroupTable OBJECT-TYPE
SYNTAXSEQUENCEOF MtaGroupEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The table holding information specific to each MTA group."::={mta 2}mtaGroupEntry OBJECT-TYPESYNTAX MtaGroupEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The entry associated with each MTA group."INDEX{applIndex, mtaGroupIndex}::={mtaGroupTable 1}
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
DisplayString,
mtaGroupOutboundConnectFailureReason
DisplayString,
mtaGroupScheduledRetry
TimeInterval,
mtaGroupMailProtocol
OBJECTIDENTIFIER,
mtaGroupName
DisplayString,
mtaGroupSuccessfulConvertedMessages
Counter32,
mtaGroupFailedConvertedMessages
Counter32,
mtaGroupDescription
DisplayString,
mtaGroupURL
URLString,
mtaGroupCreationTime
TimeInterval,
mtaGroupHierarchy
INTEGER,
mtaGroupOldestMessageId
DisplayString,
mtaGroupLoopsDetected
Counter32}mtaGroupIndex OBJECT-TYPESYNTAXINTEGER(1..2147483647)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The index associated with a group for a given MTA."::={mtaGroupEntry 1}
mtaGroupReceivedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of messages received to this group since
group creation."::={mtaGroupEntry 2}mtaGroupRejectedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of messages rejected by this group since
group creation."::={mtaGroupEntry 3}mtaGroupStoredMessages OBJECT-TYPESYNTAXGauge32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of messages currently stored in this
group's queue."::={mtaGroupEntry 4}
mtaGroupTransmittedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of messages transmitted by this group since
group creation."::={mtaGroupEntry 5}mtaGroupReceivedVolume OBJECT-TYPESYNTAXCounter32UNITS"K-octets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaGroupEntry 6}mtaGroupStoredVolume OBJECT-TYPESYNTAXGauge32UNITS"K-octets"
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaGroupEntry 7}mtaGroupTransmittedVolume OBJECT-TYPESYNTAXCounter32UNITS"K-octets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaGroupEntry 8}
mtaGroupReceivedRecipients OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaGroupEntry 9}mtaGroupStoredRecipients OBJECT-TYPESYNTAXGauge32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaGroupEntry 10}mtaGroupTransmittedRecipients OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaGroupEntry 11}mtaGroupOldestMessageStored OBJECT-TYPESYNTAXTimeIntervalMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Time since the oldest message in this group's queue was
placed in the queue."::={mtaGroupEntry 12}mtaGroupInboundAssociations OBJECT-TYPESYNTAXGauge32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of current associations to the group, where the
group is the responder."::={mtaGroupEntry 13}mtaGroupOutboundAssociations OBJECT-TYPESYNTAXGauge32MAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"The number of current associations to the group, where the
group is the initiator."::={mtaGroupEntry 14}mtaGroupAccumulatedInboundAssociations OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of associations to the group since
group creation, where the MTA was the responder."::={mtaGroupEntry 15}mtaGroupAccumulatedOutboundAssociations OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of associations from the group since
group creation, where the MTA was the initiator."::={mtaGroupEntry 16}mtaGroupLastInboundActivity OBJECT-TYPESYNTAXTimeIntervalMAX-ACCESSread-only
STATUScurrentDESCRIPTION"Time since the last time that this group had an active
inbound association for purposes of message reception."::={mtaGroupEntry 17}mtaGroupLastOutboundActivity OBJECT-TYPESYNTAXTimeIntervalMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Time since the last time that this group had a
successful outbound association for purposes of
message delivery."::={mtaGroupEntry 18}mtaGroupLastOutboundAssociationAttempt OBJECT-TYPESYNTAXTimeIntervalMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Time since the last time that this group attempted
to make an outbound association for purposes of
message delivery."::={mtaGroupEntry 34}mtaGroupRejectedInboundAssociations OBJECT-TYPE
SYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of inbound associations the group has
rejected, since group creation. Rejected associations
are not counted in the accumulated association totals."::={mtaGroupEntry 19}mtaGroupFailedOutboundAssociations OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaGroupEntry 20}mtaGroupInboundRejectionReason OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The failure reason, if any, for the last association this
group refused to respond to. An empty string indicates that
the last attempt was successful. If no association attempt
has been made since the MTA was initialized the value
should be 'never'."::={mtaGroupEntry 21}mtaGroupOutboundConnectFailureReason OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The failure reason, if any, for the last association attempt
this group initiated. An empty string indicates that the last
attempt was successful. If no association attempt has been
made since the MTA was initialized the value should be
'never'."::={mtaGroupEntry 22}mtaGroupScheduledRetry OBJECT-TYPESYNTAXTimeIntervalMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The time when this group is scheduled to next attempt to
make an association."::={mtaGroupEntry 23}mtaGroupMailProtocol OBJECT-TYPE
SYNTAXOBJECTIDENTIFIERMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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, the IANA
maintains a registry of the OIDs which correspond to well-known
message transfer protocols. If the application protocol is
not listed in the registry, an OID value of the form
{applTCPProtoID port} or {applUDProtoID 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 group. applTCPProtoID and applUDPProtoID are
defined in [8]."::={mtaGroupEntry 24}mtaGroupName OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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 1779 [9]. For X.400(1984) MTAs which do not
have a Distinguished Name, the RFC 1327 [12] syntax
'mta in globalid' should be used."::={mtaGroupEntry 25}mtaGroupSuccessfulConvertedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of messages that have been successfully
converted from one form to another in this group
since group creation."::={mtaGroupEntry 26}mtaGroupFailedConvertedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaGroupEntry 27}mtaGroupDescription OBJECT-TYPE
SYNTAXDisplayStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A description of the group's purpose. This information is
intended to identify the group in a status display."::={mtaGroupEntry 28}mtaGroupURL OBJECT-TYPESYNTAXURLStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A URL pointing to a description of the group. This
information is intended to identify and briefly describe
the group in a status display."::={mtaGroupEntry 29}mtaGroupCreationTime OBJECT-TYPESYNTAXTimeIntervalMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Time since this group was first created."::={mtaGroupEntry 30}mtaGroupHierarchy OBJECT-TYPE
SYNTAXINTEGER(-2147483648..2147483647)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaGroupEntry 31}mtaGroupOldestMessageId OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Message ID of the oldest message in the group's queue.
Whenever possible this should be in the form of an
RFC 822 [13] msg-id; X.400 may convert X.400 message
identifiers to this form by following the rules laid
out in RFC1327 [12]."::={mtaGroupEntry 32}mtaGroupLoopsDetected OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"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."::={mtaGroupEntry 33}-- The mtaGroupAssociationTable provides a means of correlating
-- entries in the network services association table with the
-- MTA group responsible for the association.mtaGroupAssociationTable OBJECT-TYPESYNTAXSEQUENCEOF MtaGroupAssociationEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The table holding information regarding the associations
for each MTA group."::={mta 3}mtaGroupAssociationEntry OBJECT-TYPESYNTAX MtaGroupAssociationEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The entry holding information regarding the associations
for each MTA group."INDEX{applIndex, mtaGroupIndex, mtaGroupAssociationIndex}::={mtaGroupAssociationTable 1}
MtaGroupAssociationEntry ::=SEQUENCE{
mtaGroupAssociationIndex
INTEGER
}mtaGroupAssociationIndex OBJECT-TYPESYNTAXINTEGER(1..2147483647)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Reference into association table to allow correlation of
this group's active associations with the association table."::={mtaGroupAssociationEntry 1}-- The mtaGroupErrorTable gives each group a way of tallying
-- the specific errors it has encountered. The mechanism
-- defined here uses RFC 1893 [14] status codes to identify
-- various specific errors. There are also classes for generic
-- errors of various sorts, and the entire mechanism is also
-- extensible, in that new error codes can be defined at any
-- time.mtaGroupErrorTable OBJECT-TYPESYNTAXSEQUENCEOF MtaGroupErrorEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The table holding information regarding accumulated errors
for each MTA group."::={mta 5}
mtaGroupErrorEntry OBJECT-TYPESYNTAX MtaGroupErrorEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The entry holding information regarding accumulated
errors for each MTA group."INDEX{applIndex, mtaGroupIndex, mtaStatusCode}::={mtaGroupErrorTable 1}
MtaGroupErrorEntry ::=SEQUENCE{
mtaGroupInboundErrorCount
Counter32,
mtaGroupInternalErrorCount
Counter32,
mtaGroupOutboundErrorCount
Counter32}mtaGroupInboundErrorCount OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Count of the number of errors of a given type that have
been accumulated in assocation 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."::={mtaGroupErrorEntry 1}mtaGroupInternalErrorCount OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Count of the number of errors of a given type that have
been accumulated in assocation with a particular group
during internal MTA processing."::={mtaGroupErrorEntry 2}mtaGroupOutboundErrorCount OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Count of the number of errors of a given type that have
been accumulated in assocation 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."::={mtaGroupErrorEntry 3}-- Conformance informationmtaConformance OBJECTIDENTIFIER::={mta 4}mtaGroups OBJECTIDENTIFIER::={mtaConformance 1}mtaCompliances OBJECTIDENTIFIER::={mtaConformance 2}-- Compliance statementsmtaCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SNMPv2 entities which
implement the Mail Monitoring MIB for basic
monitoring of MTAs."MODULE-- this moduleMANDATORY-GROUPS{mtaGroup}::={mtaCompliances 1}mtaAssocCompliance MODULE-COMPLIANCE
STATUScurrentDESCRIPTION"The compliance statement for SNMPv2 entities which
implement the Mail Monitoring MIB for monitoring of
MTAs and their associations."MODULE-- this moduleMANDATORY-GROUPS{mtaGroup, mtaAssocGroup}::={mtaCompliances 2}mtaErrorCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SNMPv2 entities which
implement the Mail Monitoring MIB for monitoring of
MTAs and detailed errors."MODULE-- this moduleMANDATORY-GROUPS{mtaGroup, mtaErrorGroup}::={mtaCompliances 3}mtaFullCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SNMPv2 entities which
implement the full Mail Monitoring MIB for monitoring
of MTAs, associations, and detailed errors."MODULE-- this module
MANDATORY-GROUPS{mtaGroup, mtaAssocGroup, mtaErrorGroup}::={mtaCompliances 4}-- Units of conformancemtaGroup OBJECT-GROUPOBJECTS{
mtaReceivedMessages, mtaStoredMessages,
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
mtaTransmittedVolume, mtaReceivedRecipients,
mtaStoredRecipients, mtaTransmittedRecipients,
mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
mtaGroupReceivedMessages, mtaGroupRejectedMessages,
mtaGroupStoredMessages, mtaGroupTransmittedMessages,
mtaGroupReceivedVolume, mtaGroupStoredVolume,
mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
mtaGroupOutboundAssociations, mtaLoopsDetected,
mtaGroupAccumulatedInboundAssociations,
mtaGroupAccumulatedOutboundAssociations,
mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
mtaGroupLastOutboundAssociationAttempt,
mtaGroupRejectedInboundAssociations,
mtaGroupFailedOutboundAssociations,
mtaGroupInboundRejectionReason,
mtaGroupOutboundConnectFailureReason,
mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName,
mtaGroupSuccessfulConvertedMessages,
mtaGroupFailedConvertedMessages, mtaGroupDescription,
mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy,
mtaGroupOldestMessageId, mtaGroupLoopsDetected}STATUScurrentDESCRIPTION"A collection of objects providing basic monitoring of MTAs."::={mtaGroups 1}mtaAssocGroup OBJECT-GROUPOBJECTS{
mtaGroupAssociationIndex}
STATUScurrentDESCRIPTION"A collection of objects providing monitoring of MTA
associations."::={mtaGroups 2}mtaErrorGroup OBJECT-GROUPOBJECTS{
mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
mtaGroupOutboundErrorCount}STATUScurrentDESCRIPTION"A collection of objects providing monitoring of
detailed MTA errors."::={mtaGroups 3}END