draft-ietf-madman-mail-monitor-mib-02.txt   draft-ietf-madman-mail-monitor-mib-03.txt 
Network Working Group Steve Kille, WG Chair Network Working Group Ned Freed
Internet Draft Ned Freed, Editor Internet Draft <draft-ietf-madman-mail-monitor-mib-03.txt>
<draft-ietf-madman-mail-monitor-mib-02.txt>
Mail Monitoring MIB Mail Monitoring MIB
August 1996
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months. Internet-Drafts are draft documents valid for a maximum of six months.
Internet-Drafts may be updated, replaced, or obsoleted by other Internet-Drafts may be updated, replaced, or obsoleted by other
documents at any time. It is not appropriate to use Internet-Drafts as documents at any time. It is not appropriate to use Internet-Drafts as
skipping to change at page 2, line ? skipping to change at page 2, line ?
``work in progress.'' ``work in progress.''
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
1id-abstracts.txt listing contained in the Internet-Drafts Shadow 1id-abstracts.txt listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe),
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community.
particular, this memo extends the basic Network Services Monitoring MIB Specifically, this memo extends the basic Network Services Monitoring
[5] to allow monitoring of Message Transfer Agents (MTAs). It may also MIB [8] to allow monitoring of Message Transfer Agents (MTAs). It may
be used to monitor MTA components within gateways. also be used to monitor MTA components within gateways.
2. Table of Contents 2. Table of Contents
1 Introduction .................................................... 1 1 Introduction .................................................... 1
2 Table of Contents ............................................... 2 2 Table of Contents ............................................... 2
3 The SNMPv2 Network Management Framework ......................... 2 3 The SNMPv2 Network Management Framework ......................... 2
3.1 Object Definitions ............................................ 2 3.1 Object Definitions ............................................ 2
4 Message Flow Model .............................................. 3 4 Message Flow Model .............................................. 3
5 MTA Objects ..................................................... 3 5 MTA Objects ..................................................... 4
6 Definitions ..................................................... 4 6 Definitions ..................................................... 4
7 Changes made since RFC 1566 ..................................... 27 7 Changes made since RFC 1566 ..................................... 30
8 Acknowledgements ................................................ 28 8 Acknowledgements ................................................ 31
9 References ...................................................... 28 9 References ...................................................... 31
10 Security Considerations ........................................ 29 10 Security Considerations ........................................ 32
11 Authors' Addresses ............................................. 29 11 Author and Chair Addresses ..................................... 32
3. The SNMPv2 Network Management Framework 3. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major The SNMPv2 Network Management Framework consists of seven major
components. They are: components. They are:
o RFC 1902 [1] which defines the SMI, the mechanisms used for o RFC 1902 [1] which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of management. describing and naming objects for the purpose of management.
o RFC 1213 [2] defines MIB-II, the core set of managed objects for o RFC 1903 [2] defines textual conventions for SNMPv2.
the Internet suite of protocols.
o RFC 1445 [3] which defines the administrative and other o RFC 1904 [3] defines conformance statements for SNMPv2.
architectural aspects of the framework.
o RFC 1905 [4] which defines the protocol used for network access to o RFC 1905 [4] defines transport mappings for SNMPv2.
managed objects.
o RFC 1906 [5] defines the protocol operations used for network
access to managed objects.
o RFC 1907 [6] defines the Management Information Base for SNMPv2.
o RFC 1908 [7] specifies coexistance between SNMP and SNMPv2.
The Framework permits new objects to be defined for the purpose of The Framework permits new objects to be defined for the purpose of
experimentation and evaluation. experimentation and evaluation.
3.1. Object Definitions 3.1. Object Definitions
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined using Management Information Base or MIB. Objects in the MIB are defined using
the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI.
In particular, each object type is named by an OBJECT IDENTIFIER, an In particular, each object type is named by an OBJECT IDENTIFIER, an
administratively assigned name. The object type together with an object administratively assigned name. The object type together with an object
instance serves to uniquely identify a specific instantiation of the instance serves to uniquely identify a specific instantiation of the
object. For human convenience, we often use a textual string, termed object. For human convenience, we often use a textual string, termed
the descriptor, to refer to the object type. the descriptor, to refer to the object type.
4. Message Flow Model 4. Message Flow Model
A general model of message flow inside an MTA has to be presented before A general model of message flow inside an MTA has to be presented before
a MIB can be described. Generally speaking, message flow occurs in four a MIB can be described. Generally speaking, message flow is modelled as
steps: occuring in four steps:
(1) Messages are received by the MTA from User Agents, Message (1) Messages are received by the MTA from User Agents, Message
Stores, other MTAs, and gateways. Stores, other MTAs, and gateways.
(2) The "next hop" for the each message is determined. This is simply (2) The "next hop" for the each message is determined. This is simply
the destination the message is to be transmitted to; it may or the destination the message is to be transmitted to; it may or
may not be the final destination of the message. Multiple "next may not be the final destination of the message. Multiple "next
hops" may exist for a single message (as a result of either hops" may exist for a single message (as a result of either
having multiple recipients or distribution list expansion); this having multiple recipients or distribution list expansion); this
may make it necessary to duplicate messages. may make it necessary to duplicate messages.
skipping to change at page 3, line 46 skipping to change at page 4, line 8
messages precisely as they are received and perform all expansions and messages precisely as they are received and perform all expansions and
conversions during retransmission processing. So here only (1) occurs conversions during retransmission processing. So here only (1) occurs
prior to storage. This leads to situations where, in general, a prior to storage. This leads to situations where, in general, a
measurement of messages received may not equal a measurement of messages measurement of messages received may not equal a measurement of messages
in store, or a measurement of messages stored may not equal a in store, or a measurement of messages stored may not equal a
measurement of messages retransmitted, or both. measurement of messages retransmitted, or both.
5. MTA Objects 5. MTA Objects
If there are one or more MTAs on the host, the following MIB may be used If there are one or more MTAs on the host, the following MIB may be used
to monitor them. Any number of the MTAs on a host may be monitored. Each to monitor them. Any number of the MTAs on a single host or group of
MTA is dealt with as a separate application and has its own applTable hosts may be monitored. Each MTA is dealt with as a separate network
service and has its own applTable entry in the Network Services
entry in the Network Services Monitoring MIB. Monitoring MIB.
The MIB described in this document covers only the portion which is The MIB described in this document covers only the portion which is
specific to the monitoring of MTAs. The network service related part of specific to the monitoring of MTAs. The network service related part of
the MIB is covered in a separate document [5]. the MIB is covered in a separate document [8].
This MIB defines four tables. The first of these contains per-MTA
information that isn't specific to any particular part of MTA. The
second breaks each MTA down into a collection of separate components
called groups. Groups are described in detail in the comments embedded
in the MIB below. The third table provides a means of correlating
associations tracked by the network services MIB with specific groups
within different MTAs. Finally, the fourth table provides a means of
tracking any errors encountered during the operation of the MTA. The
first two tables must be implemented to conform with this MIB; the last
two are optional.
6. Definitions 6. Definitions
MTA-MIB DEFINITIONS ::= BEGIN MTA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY
FROM SNMPv2-SMI FROM SNMPv2-SMI
DisplayString, TimeInterval DisplayString, TimeInterval
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
mib-2 mib-2
FROM RFC1213-MIB FROM RFC1213-MIB
applIndex applIndex, URLString
FROM APPLICATION-MIB; FROM NETWORK-SERVICES-MIB
-- Textual conventions -- Textual conventions
URLString ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A Uniform Resource Locator represented in accordance
with RFC 1738 [7]."
SYNTAX DisplayString
mta MODULE-IDENTITY mta MODULE-IDENTITY
LAST-UPDATED "9608270000Z" LAST-UPDATED "9703020000Z"
ORGANIZATION "IETF Mail and Directory Management Working Group" ORGANIZATION "IETF Mail and Directory Management Working Group"
CONTACT-INFO CONTACT-INFO
" Ned Freed " Ned Freed
Postal: Innosoft International, Inc. Postal: Innosoft International, Inc.
1050 East Garvey Avenue South 1050 East Garvey Avenue South
West Covina, CA 91790 West Covina, CA 91790
US US
Tel: +1 818 919 3600 Tel: +1 818 919 3600
skipping to change at page 5, line 33 skipping to change at page 5, line 33
mtaTable OBJECT-TYPE mtaTable OBJECT-TYPE
SYNTAX SEQUENCE OF MtaEntry SYNTAX SEQUENCE OF MtaEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table holding information specific to an MTA." "The table holding information specific to an MTA."
::= {mta 1} ::= {mta 1}
mtaStatusCode OBJECT-TYPE mtaStatusCode OBJECT-TYPE
SYNTAX INTEGER (40000..59999) SYNTAX INTEGER (4000000..5999999)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index capable of representing an Enhanced Mail System "An index capable of representing an Enhanced Mail System
Status Code. Enhanced Mail System Status Codes are defined Status Code. Enhanced Mail System Status Codes are
in RFC 1893 [11]. Both SMTP error response codes and X.400 defined in RFC 1893 [14]. These codes have the form
reason and diagnostic codes can be mapped into these codes.
Specifically, given a status code of the form class.subject.detail
class.subject.detail, the corresponding index value is Here 'class' is either 2, 4, or 5 and both 'subject' and
defined to be ((class * 100) + subject) * 100 + detail." '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."
mtaEntry OBJECT-TYPE mtaEntry OBJECT-TYPE
SYNTAX MtaEntry SYNTAX MtaEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entry associated with each MTA." "The entry associated with each MTA."
INDEX {applIndex} INDEX {applIndex}
::= {mtaTable 1} ::= {mtaTable 1}
skipping to change at page 6, line 39 skipping to change at page 6, line 47
mtaStoredRecipients mtaStoredRecipients
Gauge32, Gauge32,
mtaTransmittedRecipients mtaTransmittedRecipients
Counter32, Counter32,
mtaSuccessfulConvertedMessages mtaSuccessfulConvertedMessages
Counter32, Counter32,
mtaFailedConvertedMessages mtaFailedConvertedMessages
Counter32, Counter32,
mtaLoopsDetected mtaLoopsDetected
Counter32, Counter32,
mtaDescription
DisplayString,
mtaURL,
URLString
} }
mtaReceivedMessages OBJECT-TYPE mtaReceivedMessages OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of messages received since MTA initialization. "The number of messages received since MTA initialization.
This includes messages transmitted to this MTA from other This includes messages transmitted to this MTA from other
MTAs as well as messages that have been submitted to the MTAs as well as messages that have been submitted to the
skipping to change at page 11, line 28 skipping to change at page 11, line 38
field, examination of DNS or other directory information, field, examination of DNS or other directory information,
etc.), the level at which loops are detected (e.g. per etc.), the level at which loops are detected (e.g. per
message, per recipient, per directory entry, etc.), and message, per recipient, per directory entry, etc.), and
the handling of a loop once it is detected (e.g. looping the handling of a loop once it is detected (e.g. looping
messages are held, looping messages are bounced or sent messages are held, looping messages are bounced or sent
to the postmaster, messages that the MTA knows will loop to the postmaster, messages that the MTA knows will loop
won't be accepted, etc.) vary widely from one MTA to the won't be accepted, etc.) vary widely from one MTA to the
next and cannot be inferred from this variable." next and cannot be inferred from this variable."
::= {mtaEntry 12} ::= {mtaEntry 12}
mtaDescription OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A description of the MTA. This information is
intended to identify the MTA in a status display."
::= {mtaEntry 13}
mtaURL OBJECT-TYPE
SYNTAX URLString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A URL pointing to a description of the MTA. This
information is intended to identify and describe the MTA
in a status display."
::= {mtaEntry 14}
-- MTAs typically group inbound reception, queue storage, and -- MTAs typically group inbound reception, queue storage, and
-- outbound transmission in some way, rather than accounting for -- outbound transmission in some way, rather than accounting for
-- such operations only across the MTA as a whole. In the most -- such operations only across the MTA as a whole. In the most
-- extreme case separate information will be maintained for each -- extreme case separate information will be maintained for each
-- different entity that receives messages and for each entity -- different entity that receives messages and for each entity
-- the MTA stores messages for and delivers messages to. Other -- the MTA stores messages for and delivers messages to. Other
-- MTAs may elect to treat all reception equally, all queue -- MTAs may elect to treat all reception equally, all queue
-- storage equally, all deliveries equally, or some combination -- storage equally, all deliveries equally, or some combination
-- of this. Overlapped groupings are also possible, where an MTA -- of this. Overlapped groupings are also possible, where an MTA
-- decomposes its traffic in different ways for different -- decomposes its traffic in different ways for different
skipping to change at page 20, line 21 skipping to change at page 20, line 21
to make an outbound association for purposes of to make an outbound association for purposes of
message delivery." message delivery."
::= {mtaGroupEntry 34} ::= {mtaGroupEntry 34}
mtaGroupRejectedInboundAssociations OBJECT-TYPE mtaGroupRejectedInboundAssociations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of inbound associations the group has "The total number of inbound associations the group has
rejected, since group creation. Rejected rejected, since group creation. Rejected associations
associations are not counted in the accumulated are not counted in the accumulated association totals."
association totals."
::= {mtaGroupEntry 19} ::= {mtaGroupEntry 19}
mtaGroupFailedOutboundAssociations OBJECT-TYPE mtaGroupFailedOutboundAssociations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number associations where the group was the "The total number associations where the group was the
initiator and association establishment has failed, initiator and association establishment has failed,
since group creation. Failed associations are since group creation. Failed associations are
skipping to change at page 21, line 41 skipping to change at page 21, line 41
"An identification of the protocol being used by this group. "An identification of the protocol being used by this group.
For an group employing OSI protocols, this will be the For an group employing OSI protocols, this will be the
Application Context. For Internet applications, the IANA Application Context. For Internet applications, the IANA
maintains a registry of the OIDs which correspond to well-known maintains a registry of the OIDs which correspond to well-known
message transfer protocols. If the application protocol is message transfer protocols. If the application protocol is
not listed in the registry, an OID value of the form not listed in the registry, an OID value of the form
{applTCPProtoID port} or {applUDProtoID port} are used for {applTCPProtoID port} or {applUDProtoID port} are used for
TCP-based and UDP-based protocols, respectively. In either TCP-based and UDP-based protocols, respectively. In either
case 'port' corresponds to the primary port number being case 'port' corresponds to the primary port number being
used by the group. applTCPProtoID and applUDPProtoID are used by the group. applTCPProtoID and applUDPProtoID are
defined in [5]." defined in [8]."
::= {mtaGroupEntry 24} ::= {mtaGroupEntry 24}
mtaGroupName OBJECT-TYPE mtaGroupName OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A descriptive name for the group. If this group connects to "A descriptive name for the group. If this group connects to
a single remote MTA this should be the name of that MTA. If 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 this in turn is an Internet MTA this should be the domain
name. For an OSI MTA it should be the string encoded name. For an OSI MTA it should be the string encoded
distinguished name of the managed object using the format distinguished name of the managed object using the format
defined in RFC 1779 [6]. For X.400(1984) MTAs which do not defined in RFC 1779 [9]. For X.400(1984) MTAs which do not
have a Distinguished Name, the RFC 1327 [9] syntax have a Distinguished Name, the RFC 1327 [12] syntax
'mta in globalid' should be used." 'mta in globalid' should be used."
::= {mtaGroupEntry 25} ::= {mtaGroupEntry 25}
mtaGroupSuccessfulConvertedMessages OBJECT-TYPE mtaGroupSuccessfulConvertedMessages OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of messages that have been successfully "The number of messages that have been successfully
converted from one form to another in this group converted from one form to another in this group
skipping to change at page 23, line 11 skipping to change at page 23, line 11
"A description of the group's purpose. This information is "A description of the group's purpose. This information is
intended to identify the group in a status display." intended to identify the group in a status display."
::= {mtaGroupEntry 28} ::= {mtaGroupEntry 28}
mtaGroupURL OBJECT-TYPE mtaGroupURL OBJECT-TYPE
SYNTAX URLString SYNTAX URLString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A URL pointing to a description of the group. This "A URL pointing to a description of the group. This
information is intended to identify and describe the group information is intended to identify and briefly describe
in a status display." the group in a status display."
::= {mtaEntry 29} ::= {mtaEntry 29}
mtaGroupCreationTime OBJECT-TYPE mtaGroupCreationTime OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since this group was first created." "Time since this group was first created."
::= {mtaGroupEntry 30} ::= {mtaGroupEntry 30}
skipping to change at page 23, line 47 skipping to change at page 24, line 12
group hierarchy cannot be determined." group hierarchy cannot be determined."
::= {mtaGroupEntry 31} ::= {mtaGroupEntry 31}
mtaGroupOldestMessageId OBJECT-TYPE mtaGroupOldestMessageId OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Message ID of the oldest message in the group's queue. "Message ID of the oldest message in the group's queue.
Whenever possible this should be in the form of an Whenever possible this should be in the form of an
RFC 822 [10] msg-id; X.400 may convert X.400 message RFC 822 [13] msg-id; X.400 may convert X.400 message
identifiers to this form by following the rules laid identifiers to this form by following the rules laid
out in RFC1327 [9]." out in RFC1327 [12]."
::= {mtaGroupEntry 32} ::= {mtaGroupEntry 32}
mtaGroupLoopsDetected OBJECT-TYPE mtaGroupLoopsDetected OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A message loop is defined as a situation where the MTA "A message loop is defined as a situation where the MTA
decides that a given message will never be delivered to decides that a given message will never be delivered to
one or more recipients and instead will continue to one or more recipients and instead will continue to
skipping to change at page 24, line 30 skipping to change at page 24, line 41
field, examination of DNS or other directory information, field, examination of DNS or other directory information,
etc.), the level at which loops are detected (e.g. per etc.), the level at which loops are detected (e.g. per
message, per recipient, per directory entry, etc.), and message, per recipient, per directory entry, etc.), and
the handling of a loop once it is detected (e.g. looping the handling of a loop once it is detected (e.g. looping
messages are held, looping messages are bounced or sent messages are held, looping messages are bounced or sent
to the postmaster, messages that the MTA knows will loop to the postmaster, messages that the MTA knows will loop
won't be accepted, etc.) vary widely from one MTA to the won't be accepted, etc.) vary widely from one MTA to the
next and cannot be inferred from this variable." next and cannot be inferred from this variable."
::= {mtaGroupEntry 33} ::= {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-TYPE mtaGroupAssociationTable OBJECT-TYPE
SYNTAX SEQUENCE OF MtaGroupAssociationEntry SYNTAX SEQUENCE OF MtaGroupAssociationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table holding information regarding the associations "The table holding information regarding the associations
for each MTA group." for each MTA group."
::= {mta 3} ::= {mta 3}
mtaGroupAssociationEntry OBJECT-TYPE mtaGroupAssociationEntry OBJECT-TYPE
skipping to change at page 25, line 19 skipping to change at page 25, line 38
mtaGroupAssociationIndex OBJECT-TYPE mtaGroupAssociationIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647) SYNTAX INTEGER (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Reference into association table to allow correlation of "Reference into association table to allow correlation of
this group's active associations with the association table." this group's active associations with the association table."
::= {mtaGroupAssociationEntry 1} ::= {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-TYPE
SYNTAX SEQUENCE OF MtaGroupErrorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table holding information regarding accumulated errors
for each MTA group."
::= {mta 4}
mtaGroupErrorEntry OBJECT-TYPE
SYNTAX MtaGroupErrorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 information -- Conformance information
mtaConformance OBJECT IDENTIFIER ::= {mta 4} mtaConformance OBJECT IDENTIFIER ::= {mta 4}
mtaGroups OBJECT IDENTIFIER ::= {mtaConformance 1} mtaGroups OBJECT IDENTIFIER ::= {mtaConformance 1}
mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2} mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2}
-- Compliance statements -- Compliance statements
mtaCompliance MODULE-COMPLIANCE mtaCompliance MODULE-COMPLIANCE
skipping to change at page 26, line 5 skipping to change at page 28, line 15
mtaAssocCompliance MODULE-COMPLIANCE mtaAssocCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMPv2 entities which "The compliance statement for SNMPv2 entities which
implement the Mail Monitoring MIB for monitoring of implement the Mail Monitoring MIB for monitoring of
MTAs and their associations." MTAs and their associations."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {mtaGroup, mtaAssocGroup} MANDATORY-GROUPS {mtaGroup, mtaAssocGroup}
::= {mtaCompliances 2} ::= {mtaCompliances 2}
mtaErrorCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities which
implement the Mail Monitoring MIB for monitoring of
MTAs and detailed errors."
MODULE -- this module
MANDATORY-GROUPS {mtaGroup, mtaErrorGroup}
::= {mtaCompliances 2}
mtaFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"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 2}
-- Units of conformance -- Units of conformance
mtaGroup OBJECT-GROUP mtaGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mtaReceivedMessages, mtaStoredMessages, mtaReceivedMessages, mtaStoredMessages,
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
mtaTransmittedVolume, mtaReceivedRecipients, mtaTransmittedVolume, mtaReceivedRecipients,
mtaStoredRecipients, mtaTransmittedRecipients, mtaStoredRecipients, mtaTransmittedRecipients,
mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages, mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
mtaLoopsDetected, mtaDescription, mtaURL,
mtaGroupReceivedMessages, mtaGroupRejectedMessages, mtaGroupReceivedMessages, mtaGroupRejectedMessages,
mtaGroupStoredMessages, mtaGroupTransmittedMessages, mtaGroupStoredMessages, mtaGroupTransmittedMessages,
mtaGroupReceivedVolume, mtaGroupStoredVolume, mtaGroupReceivedVolume, mtaGroupStoredVolume,
mtaGroupTransmittedVolume, mtaGroupReceivedRecipients, mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
mtaGroupStoredRecipients, mtaGroupTransmittedRecipients, mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
mtaGroupOldestMessageStored, mtaGroupInboundAssociations, mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
mtaGroupOutboundAssociations, mtaGroupOutboundAssociations, mtaLoopsDetected,
mtaGroupAccumulatedInboundAssociations, mtaGroupAccumulatedInboundAssociations,
mtaGroupAccumulatedOutboundAssociations, mtaGroupAccumulatedOutboundAssociations,
mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity, mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
mtaGroupLastOutboundAssociationAttempt, mtaGroupLastOutboundAssociationAttempt,
mtaGroupRejectedInboundAssociations, mtaGroupRejectedInboundAssociations,
mtaGroupFailedOutboundAssociations, mtaGroupFailedOutboundAssociations,
mtaGroupInboundRejectionReason, mtaGroupInboundRejectionReason,
mtaGroupOutboundConnectFailureReason, mtaGroupOutboundConnectFailureReason,
mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName, mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName,
mtaGroupSuccessfulConvertedMessages, mtaGroupSuccessfulConvertedMessages,
skipping to change at page 26, line 49 skipping to change at page 30, line 5
mtaAssocGroup OBJECT-GROUP mtaAssocGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mtaGroupAssociationIndex} mtaGroupAssociationIndex}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing monitoring of MTA "A collection of objects providing monitoring of MTA
associations." associations."
::= {mtaGroups 2} ::= {mtaGroups 2}
mtaErrorGroup OBJECT-GROUP
OBJECTS {
mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
mtaGroupOutboundErrorCount}
STATUS current
DESCRIPTION
"A collection of objects providing monitoring of
detailed MTA errors."
::= {mtaGroups 3}
END END
7. Changes made since RFC 1566 7. Changes made since RFC 1566
The only changes made to this document since it was issued as RFC 1566 The only changes made to this document since it was issued as RFC 1566
[8] are the following: [11] are the following:
(1) A number of DESCRIPTION fields have been reworded, hopefully (1) A number of DESCRIPTION fields have been reworded, hopefully
making them clearer. making them clearer.
(2) mtaDescription, mtaURL, mtaGroupDescription, mtaGroupURL fields (2) mtaGroupDescription and mtaGroupURL fields have been added.
have been added. These fields are intended to identify and These fields are intended to identify and describe the MTA and
describe the MTA and the various MTA groups. the various MTA groups.
(3) The time since the last outbound association attempt is now (3) The time since the last outbound association attempt is now
distinct from the time since the last successfuol outbound distinct from the time since the last successfuol outbound
association attempt. association attempt.
(4) Conversion operation counters have been added. (4) Conversion operation counters have been added.
(5) A mechanism to explicitly describe group hierarchies has been (5) A mechanism to explicitly describe group hierarchies has been
added. added.
(6) A field for the ID of the oldest message in a group's queue has (6) A mechanism to count specific sorts of errors has been added.
(7) A field for the ID of the oldest message in a group's queue has
been added. been added.
(7) Per-MTA and per-group message loop counters have been added. (8) Per-MTA and per-group message loop counters have been added.
(9) A new table has been added to keep track of any errors an MTA
encounters.
8. Acknowledgements 8. Acknowledgements
This document is a product of the Mail and Directory Management (MADMAN) This document is a work product of the Mail and Directory Management
Working Group. It is based on an earlier MIB designed by S. Kille, T. (MADMAN) Working Group of the IETF. It is based on an earlier MIB
Lenggenhager, D. Partain, and W. Yeong. The Electronic Mail designed by S. Kille, T. Lenggenhager, D. Partain, and W. Yeong. The
Association's TSC committee was instrumental in providing feedback on Electronic Mail Association's TSC committee was instrumental in
and suggesting enhancements to RFC 1566 [8] that have led to the present providing feedback on and suggesting enhancements to RFC 1566 [11] that
document. have led to the present document.
9. References 9. References
[1] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Structure [1] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Structure
of Management Information for Version 2 of the Simple Network of Management Information for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1902, January 1996. Management Protocol (SNMPv2)", RFC 1902, January 1996.
[2] McCloghrie, K., and Rose, M., Editors, "Management Information Base [2] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Textual
for Network Management of TCP/IP-based internets: MIB-II", STD 17, Conventions for Version 2 of the Simple Network Management Protocol
RFC 1213, March 1991. (SNMPv2)", RFC 1903, January 1996.
[3] Galvin, J., McCloghrie, K., " Administrative Model for version 2 of [3] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Conformance
the Simple Network Management Protocol (SNMPv2)", RFC 1445, April Statements for Version 2 of the Simple Network Management Protocol
1993. (SNMPv2)", RFC 1904, January 1996.
[4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol
Operations for Version 2 of the Simple Network Management Protocol Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, January 1996. (SNMPv2)", RFC 1905, January 1996.
[5] Freed, N., Kille, S., "The Network Services Monitoring MIB", [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport
Internet Draft, March 1996. Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, January 1996.
[6] Kille, S., "A String Representation of Distinguished Names", RFC [6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Management
Information Base for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1907, January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
"Coexistence between Version 1 and Version 2 of the Internet-
standard Network Management Framework", RFC 1908, January 1996.
[8] Freed, N., Kille, S., "The Network Services Monitoring MIB",
Internet Draft, March 1997.
[9] Kille, S., "A String Representation of Distinguished Names", RFC
1779, March 1995. 1779, March 1995.
[7] Berners-Lee, T., Masinter, L., McCahill, M., iform Resource [10] Berners-Lee, T., Masinter, L., McCahill, M., iform Resource
Locators (URL)", RFC 1738, December 1994. Locators (URL)", RFC 1738, December 1994.
[8] Freed, N., Kille, S., "Mail Monitoring MIB", RFC 1566, January [11] Freed, N., Kille, S., "Mail Monitoring MIB", RFC 1566, January
1994. 1994.
[9] Kille, S., "Mapping between X.400(1988) / ISO 10021 and RFC 822", [12] Kille, S., "Mapping between X.400(1988) / ISO 10021 and RFC 822",
RFC 1327, May 1992. RFC 1327, May 1992.
[10] Crocker, D., "Standard for the Format of ARPA Internet Text [13] Crocker, D., "Standard for the Format of ARPA Internet Text
Message", August 1982. Message", RFC 822, August 1982.
[11] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893, Octel [14] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893, Octel
Network Services, January 1996. Network Services, January 1996.
10. Security Considerations 10. Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
11. Authors' Addresses 11. Author and Chair Addresses
Ned Freed, Editor Ned Freed
Innosoft International, Inc. Innosoft International, Inc.
1050 East Garvey Avenue South 1050 East Garvey Avenue South
West Covina, CA 91790 West Covina, CA 91790
USA USA
tel: +1 818 919 3600 tel: +1 818 919 3600
fax: +1 818 919 3614 fax: +1 818 919 3614
email: ned@innosoft.com email: ned@innosoft.com
Steve Kille, WG Chair Steve Kille, MADMAN WG Chair
ISODE Consortium ISODE Consortium
The Dome, The Square The Dome, The Square
Richmond TW9 1DT Richmond TW9 1DT
UK UK
tel: +44 181 332 9091 tel: +44 181 332 9091
email: S.Kille@isode.com email: S.Kille@isode.com
 End of changes. 50 change blocks. 
114 lines changed or deleted 224 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/