draft-ietf-madman-email-mib-05.txt   rfc2789.txt 
Network Working Group Ned Freed, Innosoft
Internet Draft Steve Kille, ISODE Consortium
Obsoletes: 1566, 2249 <draft-ietf-madman-email-mib-05.txt>
Mail Monitoring MIB
December 1999
Status of this Memo
This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Task Network Working Group N. Freed
Force (IETF), its areas, and its working groups. Note that other groups Request for Comments: 2789 Innosoft
may also distribute working documents as Internet-Drafts. Obsoletes: 2249, 1566 S. Kille
Category: Standards Track MessagingDirect Ltd.
March 2000
Internet-Drafts are draft documents valid for a maximum of six months Mail Monitoring MIB
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Status of this Memo
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/shadow.html. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
1. Introduction Introduction
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
Specifically, this memo extends the basic Network Services Monitoring Specifically, this memo extends the basic Network Services Monitoring
MIB defined in RFC XXXX [16] to allow monitoring of Message Transfer MIB defined in RFC 2788 [16] to allow monitoring of Message Transfer
Agents (MTAs). It may also be used to monitor MTA components within Agents (MTAs). It may also be used to monitor MTA components within
gateways. gateways.
2. Table of Contents Table of Contents
1 Introduction .................................................... 1 1 The SNMP Network Management Framework ....................... 2
2 Table of Contents ............................................... 2 2 Message Flow Model .......................................... 3
3 The SNMPv2 Network Management Framework ......................... 2 3 MTA Objects ................................................. 3
4 Message Flow Model .............................................. 3 4 Definitions ................................................. 4
5 MTA Objects ..................................................... 4 5 Changes made since RFC 2249 ................................. 29
6 Definitions ..................................................... 5 6 Acknowledgements ............................................ 30
7 Changes made since RFC 2249 ..................................... 34 7 References .................................................. 30
8 Acknowledgements ................................................ 35 8 Security Considerations ..................................... 31
9 References ...................................................... 35 9 Author and Chair Addresses .................................. 32
10 Security Considerations ........................................ 37 10 Full Copyright Statement .................................... 33
11 Author and Chair Addresses ..................................... 38
12 Full Copyright Statement ....................................... 38
3. The SNMPv2 Network Management Framework 1. The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [1]. o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in STD
RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
called SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC second version, called SMIv2, is described in STD 58, RFC 2578
2580 [7]. [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message described in STD 15, RFC 1157 [8]. A second version of the SNMP
protocol, which is not an Internet standards track protocol, is message protocol, which is not an Internet standards track
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC
The third version of the message protocol is called SNMPv3 and 1906 [10]. The third version of the message protocol is called
described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations described in STD 15, RFC 1157 [8]. A second set of protocol
and associated PDU formats is described in RFC 1905 [13]. operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14] and o A set of fundamental applications described in RFC 2573 [14] and
the view-based access control mechanism described in RFC 2575 the view-based access control mechanism described in RFC 2575
[15]. [15].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed
Management Information Base or MIB. Objects in the MIB are defined the Management Information Base or MIB. Objects in the MIB are
using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB This memo specifies a MIB module that is compliant to the SMIv2. A
conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
4. Message Flow Model 2. 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
a MIB can be described. Generally speaking, message flow is modelled as before a MIB can be described. Generally speaking, message flow is
occurring in four steps: modelled as occurring 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.
(3) If necessary messages are converted into the format that's (3) If necessary messages are converted into the format that's
appropriate for the next hop. Conversion operations may be appropriate for the next hop. Conversion operations may be
successful or unsuccessful. successful or unsuccessful.
(4) Messages are transmitted to the appropriate destination, which (4) Messages are transmitted to the appropriate destination, which
may be a User Agent, Message Store, another MTA, or gateway. may be a User Agent, Message Store, another MTA, or gateway.
Storage of messages in the MTA occurs at some point during this process. Storage of messages in the MTA occurs at some point during this
However, it is important to note that storage may occur at different and process. However, it is important to note that storage may occur at
possibly even multiple points during this process. For example, some different and possibly even multiple points during this process. For
MTAs expand messages into multiple copies as they are received. In this example, some MTAs expand messages into multiple copies as they are
case (1), (2), and (3) may all occur prior to storage. Other MTAs store received. In this case (1), (2), and (3) may all occur prior to
messages precisely as they are received and perform all expansions and storage. Other MTAs store messages precisely as they are received and
conversions during retransmission processing. So here only (1) occurs perform all expansions and conversions during retransmission
prior to storage. This leads to situations where, in general, a processing. So here only (1) occurs prior to storage. This leads to
measurement of messages received may not equal a measurement of messages situations where, in general, a measurement of messages received may
in store, or a measurement of messages stored may not equal a not equal a measurement of messages in store, or a measurement of
measurement of messages retransmitted, or both. messages stored may not equal a measurement of messages
retransmitted, or both.
5. MTA Objects 3. 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
to monitor them. Any number of the MTAs on a single host or group of used to monitor them. Any number of the MTAs on a single host or
hosts may be monitored. Each MTA is dealt with as a separate network group of hosts may be monitored. Each MTA is dealt with as a separate
service and has its own applTable entry in the Network Services network service and has its own applTable entry in the Network
Monitoring MIB. Services 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
the MIB is covered in RFC XXXX [8]. of the MIB is covered in RFC 2788 [16].
This MIB defines four tables. The first of these contains per-MTA This MIB defines four tables. The first of these contains per-MTA
information that isn't specific to any particular part of MTA. The information that isn't specific to any particular part of MTA. The
second breaks each MTA down into a collection of separate components second breaks each MTA down into a collection of separate components
called groups. Groups are described in detail in the comments embedded called groups. Groups are described in detail in the comments
in the MIB below. The third table provides a means of correlating embedded in the MIB below. The third table provides a means of
associations tracked by the network services MIB with specific groups correlating associations tracked by the network services MIB with
within different MTAs. Finally, the fourth table provides a means of specific groups within different MTAs. Finally, the fourth table
tracking any errors encountered during the operation of the MTA. The provides a means of tracking any errors encountered during the
first two tables must be implemented to conform with this MIB; the last operation of the MTA. The first two tables must be implemented to
two are optional. conform with this MIB; the last two are optional.
6. Definitions 4. Definitions
MTA-MIB DEFINITIONS ::= BEGIN MTA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2 OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TimeInterval TimeInterval
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
applIndex, URLString applIndex, URLString
FROM NETWORK-SERVICES-MIB; FROM NETWORK-SERVICES-MIB;
mta MODULE-IDENTITY mta MODULE-IDENTITY
LAST-UPDATED "9912210000Z" LAST-UPDATED "200003030000Z"
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 Lakes Drive 1050 Lakes Drive
West Covina, CA 91790 West Covina, CA 91790
US US
Tel: +1 626 919 3600 Tel: +1 626 919 3600
Fax: +1 626 919 3614 Fax: +1 626 919 3614
E-Mail: ned.freed@innosoft.com" E-Mail: ned.freed@innosoft.com"
DESCRIPTION DESCRIPTION
"The MIB module describing Message Transfer Agents (MTAs)" "The MIB module describing Message Transfer Agents (MTAs)"
REVISION "9912210000Z" REVISION "200003030000Z"
DESCRIPTION DESCRIPTION
"This revision, published in RFC YYYY, changes a number of "This revision, published in RFC 2789, changes a number of
DisplayStrings to SnmpAdminStrings. Note that this change DisplayStrings to SnmpAdminStrings. Note that this change
is not strictly supported by SMIv2. However, the alternative is not strictly supported by SMIv2. However, the alternative
of deprecating the old objects and defining new objects of deprecating the old objects and defining new objects
would have a more adverse impact on backward compatibility would have a more adverse impact on backward compatibility
and interoperability, given the particular semantics of and interoperability, given the particular semantics of
these objects. The defining reference for distinguished these objects. The defining reference for distinguished
names has also been updated from RFC 1779 to RFC 2253." names has also been updated from RFC 1779 to RFC 2253."
REVISION "9905120000Z" REVISION "199905120000Z"
DESCRIPTION DESCRIPTION
"This revision fixes a number of technical problems found in "This revision fixes a number of technical problems found in
previous versions: The conformance groups for different previous versions: The conformance groups for different
versions of this MIB have been corrected, the recommendation versions of this MIB have been corrected, the recommendation
that an empty string be returned if the last operation was that an empty string be returned if the last operation was
successful has been removed from successful has been removed from
mtaGroupInboundRejectionReason and mtaGroupInboundRejectionReason and
mtaGroupOutboundConnectFailureReason as it conflicts mtaGroupOutboundConnectFailureReason as it conflicts
with the stated purpose of these variables, and the with the stated purpose of these variables, and the
required mtaStatusCode entry has been added to required mtaStatusCode entry has been added to
MtaGroupErrorEntry. It should be noted that this last MtaGroupErrorEntry. It should be noted that this last
change in no way affects the bits on the wire." change in no way affects the bits on the wire."
REVISION "9708170000Z" REVISION "199708170000Z"
DESCRIPTION DESCRIPTION
"This revision, published in RFC 2249, adds the "This revision, published in RFC 2249, adds the
mtaGroupDescription and mtaGroupURL fields, conversion mtaGroupDescription and mtaGroupURL fields, conversion
operation counters, a group hierarchy description mechanism, operation counters, a group hierarchy description mechanism,
counters for specific errors, oldest message IDs, per-MTA counters for specific errors, oldest message IDs, per-MTA
and per-group loop counters, and a new table for tracking and per-group loop counters, and a new table for tracking
any errors an MTA encounters." any errors an MTA encounters."
REVISION "9311280000Z" REVISION "199311280000Z"
DESCRIPTION DESCRIPTION
"The original version of this MIB was published in RFC 1566" "The original version of this MIB was published in RFC 1566"
::= {mib-2 28} ::= {mib-2 28}
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}
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}
MtaEntry ::= SEQUENCE { MtaEntry ::= SEQUENCE {
mtaReceivedMessages mtaReceivedMessages
Counter32, Counter32,
mtaStoredMessages mtaStoredMessages
Gauge32, Gauge32,
mtaTransmittedMessages mtaTransmittedMessages
Counter32, Counter32,
mtaReceivedVolume mtaReceivedVolume
Counter32, Counter32,
mtaStoredVolume mtaStoredVolume
Gauge32, Gauge32,
mtaTransmittedVolume mtaTransmittedVolume
Counter32, Counter32,
mtaReceivedRecipients mtaReceivedRecipients
Counter32, Counter32,
mtaStoredRecipients mtaStoredRecipients
Gauge32, Gauge32,
mtaTransmittedRecipients mtaTransmittedRecipients
Counter32, Counter32,
mtaSuccessfulConvertedMessages mtaSuccessfulConvertedMessages
Counter32, Counter32,
mtaFailedConvertedMessages mtaFailedConvertedMessages
Counter32, Counter32,
mtaLoopsDetected mtaLoopsDetected
Counter32 Counter32
} }
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
MTA directly by end-users or applications." MTA directly by end-users or applications."
::= {mtaEntry 1} ::= {mtaEntry 1}
mtaStoredMessages OBJECT-TYPE mtaStoredMessages OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of messages currently stored in the MTA. "The total number of messages currently stored in the MTA.
This includes messages that are awaiting transmission to This includes messages that are awaiting transmission to
some other MTA or are waiting for delivery to an end-user some other MTA or are waiting for delivery to an end-user
or application." or application."
::= {mtaEntry 2} ::= {mtaEntry 2}
mtaTransmittedMessages OBJECT-TYPE mtaTransmittedMessages OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of messages transmitted since MTA initialization. "The number of messages transmitted since MTA initialization.
This includes messages that were transmitted to some other This includes messages that were transmitted to some other
MTA or are waiting for delivery to an end-user or MTA or are waiting for delivery to an end-user or
application." application."
::= {mtaEntry 3} ::= {mtaEntry 3}
mtaReceivedVolume OBJECT-TYPE mtaReceivedVolume OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "K-octets" UNITS "K-octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total volume of messages received since MTA "The total volume of messages received since MTA
initialization, measured in kilo-octets. This volume should initialization, measured in kilo-octets. This volume should
include all transferred data that is logically above the mail include all transferred data that is logically above the mail
transport protocol level. For example, an SMTP-based MTA transport protocol level. For example, an SMTP-based MTA
should use the number of kilo-octets in the message header should use the number of kilo-octets in the message header
and body, while an X.400-based MTA should use the number of and body, while an X.400-based MTA should use the number of
kilo-octets of P2 data. This includes messages transmitted kilo-octets of P2 data. This includes messages transmitted
to this MTA from other MTAs as well as messages that have to this MTA from other MTAs as well as messages that have
been submitted to the MTA directly by end-users or been submitted to the MTA directly by end-users or
applications." applications."
::= {mtaEntry 4} ::= {mtaEntry 4}
mtaStoredVolume OBJECT-TYPE mtaStoredVolume OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "K-octets" UNITS "K-octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total volume of messages currently stored in the MTA, "The total volume of messages currently stored in the MTA,
measured in kilo-octets. This volume should include all measured in kilo-octets. This volume should include all
stored data that is logically above the mail transport stored data that is logically above the mail transport
protocol level. For example, an SMTP-based MTA should protocol level. For example, an SMTP-based MTA should
use the number of kilo-octets in the message header and use the number of kilo-octets in the message header and
body, while an X.400-based MTA would use the number of body, while an X.400-based MTA would use the number of
kilo-octets of P2 data. This includes messages that are kilo-octets of P2 data. This includes messages that are
awaiting transmission to some other MTA or are waiting awaiting transmission to some other MTA or are waiting
for delivery to an end-user or application." for delivery to an end-user or application."
::= {mtaEntry 5} ::= {mtaEntry 5}
mtaTransmittedVolume OBJECT-TYPE mtaTransmittedVolume OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "K-octets" UNITS "K-octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total volume of messages transmitted since MTA "The total volume of messages transmitted since MTA
initialization, measured in kilo-octets. This volume should initialization, measured in kilo-octets. This volume should
include all transferred data that is logically above the mail include all transferred data that is logically above the mail
transport protocol level. For example, an SMTP-based MTA transport protocol level. For example, an SMTP-based MTA
should use the number of kilo-octets in the message header should use the number of kilo-octets in the message header
and body, while an X.400-based MTA should use the number of and body, while an X.400-based MTA should use the number of
kilo-octets of P2 data. This includes messages that were kilo-octets of P2 data. This includes messages that were
transmitted to some other MTA or are waiting for delivery transmitted to some other MTA or are waiting for delivery
to an end-user or application." to an end-user or application."
::= {mtaEntry 6} ::= {mtaEntry 6}
mtaReceivedRecipients OBJECT-TYPE mtaReceivedRecipients OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of recipients specified in all messages "The total number of recipients specified in all messages
received since MTA initialization. Recipients this MTA received since MTA initialization. Recipients this MTA
has no responsibility for, i.e. inactive envelope has no responsibility for, i.e. inactive envelope
recipients or ones referred to in message headers, recipients or ones referred to in message headers,
should not be counted even if information about such should not be counted even if information about such
recipients is available. This includes messages recipients is available. This includes messages
transmitted to this MTA from other MTAs as well as transmitted to this MTA from other MTAs as well as
messages that have been submitted to the MTA directly messages that have been submitted to the MTA directly
by end-users or applications." by end-users or applications."
::= {mtaEntry 7} ::= {mtaEntry 7}
mtaStoredRecipients OBJECT-TYPE mtaStoredRecipients OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of recipients specified in all messages "The total number of recipients specified in all messages
currently stored in the MTA. Recipients this MTA has no currently stored in the MTA. Recipients this MTA has no
responsibility for, i.e. inactive envelope recipients or responsibility for, i.e. inactive envelope recipients or
ones referred to in message headers, should not be ones referred to in message headers, should not be
counted. This includes messages that are awaiting counted. This includes messages that are awaiting
transmission to some other MTA or are waiting for transmission to some other MTA or are waiting for
delivery to an end-user or application." delivery to an end-user or application."
::= {mtaEntry 8} ::= {mtaEntry 8}
mtaTransmittedRecipients OBJECT-TYPE mtaTransmittedRecipients OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of recipients specified in all messages "The total number of recipients specified in all messages
transmitted since MTA initialization. Recipients this transmitted since MTA initialization. Recipients this
MTA had no responsibility for, i.e. inactive envelope MTA had no responsibility for, i.e. inactive envelope
recipients or ones referred to in message headers, recipients or ones referred to in message headers,
should not be counted. This includes messages that were should not be counted. This includes messages that were
transmitted to some other MTA or are waiting for transmitted to some other MTA or are waiting for
delivery to an end-user or application." delivery to an end-user or application."
::= {mtaEntry 9} ::= {mtaEntry 9}
mtaSuccessfulConvertedMessages OBJECT-TYPE mtaSuccessfulConvertedMessages 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 since MTA converted from one form to another since MTA
initialization." initialization."
::= {mtaEntry 10} ::= {mtaEntry 10}
mtaFailedConvertedMessages OBJECT-TYPE mtaFailedConvertedMessages OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of messages for which an unsuccessful "The number of messages for which an unsuccessful
attempt was made to convert them from one form to attempt was made to convert them from one form to
another since MTA initialization." another since MTA initialization."
::= {mtaEntry 11} ::= {mtaEntry 11}
mtaLoopsDetected OBJECT-TYPE mtaLoopsDetected 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
loop endlessly through one or more MTAs. This variable loop endlessly through one or more MTAs. This variable
counts the number of times the MTA has detected such a counts the number of times the MTA has detected such a
situation since MTA initialization. Note that the situation since MTA initialization. Note that the
mechanism MTAs use to detect loops (e.g., trace field mechanism MTAs use to detect loops (e.g., trace field
counting, count of references to this MTA in a trace counting, count of references to this MTA in a trace
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}
-- 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 any counters that are unused as a result of a
-- given MTA's use of the group construct must 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 different "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 abstraction.
-- 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. Deletion 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.
-- Note that SNMP also defines and uses term "group". MTA groups are
-- NOT the same as SNMP groups.
mtaGroupTable OBJECT-TYPE mtaGroupTable OBJECT-TYPE
SYNTAX SEQUENCE OF MtaGroupEntry SYNTAX SEQUENCE OF MtaGroupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table holding information specific to each MTA group." "The table holding information specific to each MTA group."
::= {mta 2} ::= {mta 2}
mtaGroupEntry OBJECT-TYPE mtaGroupEntry OBJECT-TYPE
SYNTAX MtaGroupEntry SYNTAX MtaGroupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entry associated with each MTA group." "The entry associated with each MTA group."
INDEX {applIndex, mtaGroupIndex} INDEX {applIndex, mtaGroupIndex}
::= {mtaGroupTable 1} ::= {mtaGroupTable 1}
MtaGroupEntry ::= SEQUENCE { MtaGroupEntry ::= SEQUENCE {
mtaGroupIndex mtaGroupIndex
INTEGER, INTEGER,
mtaGroupReceivedMessages mtaGroupReceivedMessages
Counter32, Counter32,
mtaGroupRejectedMessages mtaGroupRejectedMessages
Counter32, Counter32,
mtaGroupStoredMessages mtaGroupStoredMessages
Gauge32, Gauge32,
mtaGroupTransmittedMessages mtaGroupTransmittedMessages
Counter32, Counter32,
mtaGroupReceivedVolume mtaGroupReceivedVolume
Counter32, Counter32,
mtaGroupStoredVolume mtaGroupStoredVolume
Gauge32, Gauge32,
mtaGroupTransmittedVolume mtaGroupTransmittedVolume
Counter32, Counter32,
mtaGroupReceivedRecipients mtaGroupReceivedRecipients
Counter32, Counter32,
mtaGroupStoredRecipients mtaGroupStoredRecipients
Gauge32, Gauge32,
mtaGroupTransmittedRecipients mtaGroupTransmittedRecipients
Counter32, Counter32,
mtaGroupOldestMessageStored mtaGroupOldestMessageStored
TimeInterval, TimeInterval,
mtaGroupInboundAssociations mtaGroupInboundAssociations
Gauge32, Gauge32,
mtaGroupOutboundAssociations mtaGroupOutboundAssociations
Gauge32, Gauge32,
mtaGroupAccumulatedInboundAssociations mtaGroupAccumulatedInboundAssociations
Counter32, Counter32,
mtaGroupAccumulatedOutboundAssociations mtaGroupAccumulatedOutboundAssociations
Counter32, Counter32,
mtaGroupLastInboundActivity mtaGroupLastInboundActivity
TimeInterval, TimeInterval,
mtaGroupLastOutboundActivity mtaGroupLastOutboundActivity
TimeInterval, TimeInterval,
mtaGroupLastOutboundAssociationAttempt mtaGroupLastOutboundAssociationAttempt
TimeInterval, TimeInterval,
mtaGroupRejectedInboundAssociations mtaGroupRejectedInboundAssociations
Counter32, Counter32,
mtaGroupFailedOutboundAssociations mtaGroupFailedOutboundAssociations
Counter32, Counter32,
mtaGroupInboundRejectionReason mtaGroupInboundRejectionReason
SnmpAdminString, 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
}
mtaGroupOutboundConnectFailureReason mtaGroupIndex OBJECT-TYPE
SnmpAdminString, SYNTAX INTEGER (1..2147483647)
mtaGroupScheduledRetry MAX-ACCESS not-accessible
TimeInterval, STATUS current
mtaGroupMailProtocol DESCRIPTION
OBJECT IDENTIFIER, "The index associated with a group for a given MTA."
mtaGroupName ::= {mtaGroupEntry 1}
SnmpAdminString,
mtaGroupSuccessfulConvertedMessages
Counter32,
mtaGroupFailedConvertedMessages
Counter32,
mtaGroupDescription
SnmpAdminString,
mtaGroupURL
URLString,
mtaGroupCreationTime
TimeInterval,
mtaGroupHierarchy
INTEGER,
mtaGroupOldestMessageId
SnmpAdminString,
mtaGroupLoopsDetected
Counter32
}
mtaGroupIndex OBJECT-TYPE mtaGroupReceivedMessages OBJECT-TYPE
SYNTAX INTEGER (1..2147483647) SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index associated with a group for a given MTA." "The number of messages received to this group since
::= {mtaGroupEntry 1} group creation."
::= {mtaGroupEntry 2}
mtaGroupReceivedMessages OBJECT-TYPE mtaGroupRejectedMessages 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 to this group since "The number of messages rejected by this group since
group creation." group creation."
::= {mtaGroupEntry 2} ::= {mtaGroupEntry 3}
mtaGroupRejectedMessages OBJECT-TYPE mtaGroupStoredMessages OBJECT-TYPE
SYNTAX Counter32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of messages rejected by this group since "The total number of messages currently stored in this
group creation." group's queue."
::= {mtaGroupEntry 3} ::= {mtaGroupEntry 4}
mtaGroupStoredMessages OBJECT-TYPE mtaGroupTransmittedMessages OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of messages currently stored in this "The number of messages transmitted by this group since
group's queue." group creation."
::= {mtaGroupEntry 4} ::= {mtaGroupEntry 5}
mtaGroupTransmittedMessages OBJECT-TYPE mtaGroupReceivedVolume OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only UNITS "K-octets"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"The number of messages transmitted by this group since DESCRIPTION
group creation." "The total volume of messages received to this group since
::= {mtaGroupEntry 5} 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}
mtaGroupReceivedVolume OBJECT-TYPE mtaGroupStoredVolume OBJECT-TYPE
SYNTAX Counter32 SYNTAX Gauge32
UNITS "K-octets" UNITS "K-octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total volume of messages received to this group since "The total volume of messages currently stored in this
group creation, measured in kilo-octets. This volume group's queue, measured in kilo-octets. This volume should
should include all transferred data that is logically above include all stored data that is logically above the mail
the mail transport protocol level. For example, an transport protocol level. For example, an SMTP-based
SMTP-based MTA should use the number of kilo-octets in the MTA should use the number of kilo-octets in the message
message header and body, while an X.400-based MTA should use header and body, while an X.400-based MTA would use the
the number of kilo-octets of P2 data." number of kilo-octets of P2 data."
::= {mtaGroupEntry 6} ::= {mtaGroupEntry 7}
mtaGroupStoredVolume OBJECT-TYPE mtaGroupTransmittedVolume OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Counter32
UNITS "K-octets" UNITS "K-octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total volume of messages currently stored in this "The total volume of messages transmitted by this group
group's queue, measured in kilo-octets. This volume should since group creation, measured in kilo-octets. This
include all stored data that is logically above the mail volume should include all transferred data that is logically
transport protocol level. For example, an SMTP-based above the mail transport protocol level. For example, an
MTA should use the number of kilo-octets in the message SMTP-based MTA should use the number of kilo-octets in the
header and body, while an X.400-based MTA would use the message header and body, while an X.400-based MTA should use
number of kilo-octets of P2 data." the number of kilo-octets of P2 data."
::= {mtaGroupEntry 7} ::= {mtaGroupEntry 8}
mtaGroupTransmittedVolume OBJECT-TYPE mtaGroupReceivedRecipients OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "K-octets" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The total number of recipients specified in all messages
"The total volume of messages transmitted by this group received to this group since group creation.
since group creation, measured in kilo-octets. This Recipients this MTA has no responsibility for should not
volume should include all transferred data that is logically be counted."
above the mail transport protocol level. For example, an ::= {mtaGroupEntry 9}
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-TYPE mtaGroupStoredRecipients OBJECT-TYPE
SYNTAX Counter32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of recipients specified in all messages "The total number of recipients specified in all messages
received to this group since group creation. currently stored in this group's queue. Recipients this
Recipients this MTA has no responsibility for should not MTA has no responsibility for should not be counted."
be counted." ::= {mtaGroupEntry 10}
::= {mtaGroupEntry 9}
mtaGroupStoredRecipients OBJECT-TYPE mtaGroupTransmittedRecipients OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of recipients specified in all messages "The total number of recipients specified in all messages
currently stored in this group's queue. Recipients this transmitted by this group since group creation.
MTA has no responsibility for should not be counted." Recipients this MTA had no responsibility for should not
::= {mtaGroupEntry 10} be counted."
::= {mtaGroupEntry 11}
mtaGroupTransmittedRecipients OBJECT-TYPE mtaGroupOldestMessageStored OBJECT-TYPE
SYNTAX Counter32 SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of recipients specified in all messages "Time since the oldest message in this group's queue was
transmitted by this group since group creation. placed in the queue."
Recipients this MTA had no responsibility for should not ::= {mtaGroupEntry 12}
be counted."
::= {mtaGroupEntry 11}
mtaGroupOldestMessageStored OBJECT-TYPE mtaGroupInboundAssociations OBJECT-TYPE
SYNTAX TimeInterval SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the oldest message in this group's queue was "The number of current associations to the group, where the
placed in the queue." group is the responder."
::= {mtaGroupEntry 12} ::= {mtaGroupEntry 13}
mtaGroupInboundAssociations OBJECT-TYPE mtaGroupOutboundAssociations OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of current associations to the group, where the "The number of current associations to the group, where the
group is the responder." group is the initiator."
::= {mtaGroupEntry 13} ::= {mtaGroupEntry 14}
mtaGroupOutboundAssociations OBJECT-TYPE mtaGroupAccumulatedInboundAssociations OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of current associations to the group, where the "The total number of associations to the group since
group is the initiator." group creation, where the MTA was the responder."
::= {mtaGroupEntry 14} ::= {mtaGroupEntry 15}
mtaGroupAccumulatedInboundAssociations OBJECT-TYPE mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of associations to the group since "The total number of associations from the group since
group creation, where the MTA was the responder." group creation, where the MTA was the initiator."
::= {mtaGroupEntry 15} ::= {mtaGroupEntry 16}
mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE mtaGroupLastInboundActivity OBJECT-TYPE
SYNTAX Counter32 SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of associations from the group since "Time since the last time that this group had an active
group creation, where the MTA was the initiator." inbound association for purposes of message reception."
::= {mtaGroupEntry 16} ::= {mtaGroupEntry 17}
mtaGroupLastInboundActivity OBJECT-TYPE mtaGroupLastOutboundActivity OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last time that this group had an active "Time since the last time that this group had a
inbound association for purposes of message reception." successful outbound association for purposes of
::= {mtaGroupEntry 17} message delivery."
::= {mtaGroupEntry 18}
mtaGroupLastOutboundActivity OBJECT-TYPE mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last time that this group had a "Time since the last time that this group attempted
successful outbound association for purposes of to make an outbound association for purposes of
message delivery." message delivery."
::= {mtaGroupEntry 18} ::= {mtaGroupEntry 34}
mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE mtaGroupRejectedInboundAssociations OBJECT-TYPE
SYNTAX TimeInterval SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last time that this group attempted "The total number of inbound associations the group has
to make an outbound association for purposes of rejected, since group creation. Rejected associations
message delivery." are not counted in the accumulated association totals."
::= {mtaGroupEntry 34} ::= {mtaGroupEntry 19}
mtaGroupRejectedInboundAssociations 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 of inbound associations the group has "The total number associations where the group was the
rejected, since group creation. Rejected associations initiator and association establishment has failed,
are not counted in the accumulated association totals." since group creation. Failed associations are
::= {mtaGroupEntry 19} not counted in the accumulated association totals."
::= {mtaGroupEntry 20}
mtaGroupFailedOutboundAssociations OBJECT-TYPE mtaGroupInboundRejectionReason OBJECT-TYPE
SYNTAX Counter32 SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number associations where the group was the "The failure reason, if any, for the last association this
initiator and association establishment has failed, group refused to respond to. If no association attempt
since group creation. Failed associations are has been made since the MTA was initialized the value
not counted in the accumulated association totals." should be 'never'."
::= {mtaGroupEntry 20} ::= {mtaGroupEntry 21}
mtaGroupInboundRejectionReason OBJECT-TYPE mtaGroupOutboundConnectFailureReason OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The failure reason, if any, for the last association this "The failure reason, if any, for the last association attempt
group refused to respond to. If no association attempt this group initiated. If no association attempt has been
has been made since the MTA was initialized the value made since the MTA was initialized the value should be
should be 'never'." 'never'."
::= {mtaGroupEntry 21} ::= {mtaGroupEntry 22}
mtaGroupOutboundConnectFailureReason OBJECT-TYPE mtaGroupScheduledRetry OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The failure reason, if any, for the last association attempt "The amount of time until this group is next scheduled to
this group initiated. If no association attempt has been attempt to make an association."
made since the MTA was initialized the value should be ::= {mtaGroupEntry 23}
'never'."
::= {mtaGroupEntry 22}
mtaGroupScheduledRetry OBJECT-TYPE mtaGroupMailProtocol OBJECT-TYPE
SYNTAX TimeInterval SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The amount of time until this group is next scheduled to "An identification of the protocol being used by this group.
attempt to make an association." For an group employing OSI protocols, this will be the
::= {mtaGroupEntry 23} 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."
::= {mtaGroupEntry 24}
mtaGroupMailProtocol OBJECT-TYPE mtaGroupName OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An identification of the protocol being used by this group. "A descriptive name for the group. If this group connects to
For an group employing OSI protocols, this will be the a single remote MTA this should be the name of that MTA. If
Application Context. For Internet applications, the IANA this in turn is an Internet MTA this should be the domain
maintains a registry of the OIDs which correspond to well-known name. For an OSI MTA it should be the string encoded
message transfer protocols. If the application protocol is distinguished name of the managed object using the format
not listed in the registry, an OID value of the form defined in RFC 2253. For X.400(1984) MTAs which do not
{applTCPProtoID port} or {applUDPProtoID port} are used for have a Distinguished Name, the RFC 2156 syntax
TCP-based and UDP-based protocols, respectively. In either 'mta in globalid' used in X400-Received: fields can be
case 'port' corresponds to the primary port number being used."
used by the group. applTCPProtoID and applUDPProtoID are ::= {mtaGroupEntry 25}
defined in the NETWORK-SERVICES-MIB, RFC XXXX."
::= {mtaGroupEntry 24}
mtaGroupName OBJECT-TYPE mtaGroupSuccessfulConvertedMessages OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX Counter32
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 "The number of messages that have been successfully
a single remote MTA this should be the name of that MTA. If converted from one form to another in this group
this in turn is an Internet MTA this should be the domain since group creation."
name. For an OSI MTA it should be the string encoded ::= {mtaGroupEntry 26}
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."
::= {mtaGroupEntry 25}
mtaGroupSuccessfulConvertedMessages OBJECT-TYPE mtaGroupFailedConvertedMessages 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 for which an unsuccessful
converted from one form to another in this group attempt was made to convert them from one form to
since group creation." another in this group since group creation."
::= {mtaGroupEntry 26} ::= {mtaGroupEntry 27}
mtaGroupFailedConvertedMessages OBJECT-TYPE mtaGroupDescription OBJECT-TYPE
SYNTAX Counter32 SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of messages for which an unsuccessful "A description of the group's purpose. This information is
attempt was made to convert them from one form to intended to identify the group in a status display."
another in this group since group creation." ::= {mtaGroupEntry 28}
::= {mtaGroupEntry 27}
mtaGroupDescription OBJECT-TYPE mtaGroupURL OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX URLString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A description of the group's purpose. This information is "A URL pointing to a description of the group. This
intended to identify the group in a status display." information is intended to identify and briefly describe
::= {mtaGroupEntry 28} the group in a status display."
::= {mtaGroupEntry 29}
mtaGroupURL OBJECT-TYPE mtaGroupCreationTime OBJECT-TYPE
SYNTAX URLString SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A URL pointing to a description of the group. This "Time since this group was first created."
information is intended to identify and briefly describe ::= {mtaGroupEntry 30}
the group in a status display."
::= {mtaGroupEntry 29}
mtaGroupCreationTime OBJECT-TYPE mtaGroupHierarchy OBJECT-TYPE
SYNTAX TimeInterval SYNTAX INTEGER (-2147483648..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since this group was first created." "Describes how this group fits into the hierarchy. A
::= {mtaGroupEntry 30} 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}
mtaGroupHierarchy OBJECT-TYPE mtaGroupOldestMessageId OBJECT-TYPE
SYNTAX INTEGER (-2147483648..2147483647) SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes how this group fits into the hierarchy. A "Message ID of the oldest message in the group's queue.
positive value is interpreted as an mtaGroupIndex Whenever possible this should be in the form of an
value for some other group whose variables include RFC 822 msg-id; X.400 may convert X.400 message
those of this group (and usually others). A negative identifiers to this form by following the rules laid
value is interpreted as a group collection code: Groups out in RFC2156."
with common negative hierarchy values comprise one ::= {mtaGroupEntry 32}
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-TYPE mtaGroupLoopsDetected OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX Counter32
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. "A message loop is defined as a situation where the MTA
Whenever possible this should be in the form of an decides that a given message will never be delivered to
RFC 822 msg-id; X.400 may convert X.400 message one or more recipients and instead will continue to
identifiers to this form by following the rules laid loop endlessly through one or more MTAs. This variable
out in RFC2156." counts the number of times the MTA has detected such a
::= {mtaGroupEntry 32} 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}
mtaGroupLoopsDetected OBJECT-TYPE -- The mtaGroupAssociationTable provides a means of correlating
SYNTAX Counter32 -- entries in the network services association table with the
MAX-ACCESS read-only -- MTA group responsible for the association.
STATUS current
DESCRIPTION
"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}
mtaGroupAssociationTable OBJECT-TYPE
SYNTAX SEQUENCE OF MtaGroupAssociationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table holding information regarding the associations
for each MTA group."
::= {mta 3}
mtaGroupAssociationTable OBJECT-TYPE mtaGroupAssociationEntry OBJECT-TYPE
SYNTAX SEQUENCE OF MtaGroupAssociationEntry SYNTAX MtaGroupAssociationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table holding information regarding the associations "The entry holding information regarding the associations
for each MTA group." for each MTA group."
::= {mta 3} INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex}
::= {mtaGroupAssociationTable 1}
mtaGroupAssociationEntry OBJECT-TYPE MtaGroupAssociationEntry ::= SEQUENCE {
SYNTAX MtaGroupAssociationEntry mtaGroupAssociationIndex
MAX-ACCESS not-accessible INTEGER
STATUS current }
DESCRIPTION
"The entry holding information regarding the associations
for each MTA group."
INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex}
::= {mtaGroupAssociationTable 1}
MtaGroupAssociationEntry ::= SEQUENCE { mtaGroupAssociationIndex OBJECT-TYPE
mtaGroupAssociationIndex SYNTAX INTEGER (1..2147483647)
INTEGER MAX-ACCESS read-only
} STATUS current
DESCRIPTION
"Reference into association table to allow correlation of
this group's active associations with the association table."
mtaGroupAssociationIndex OBJECT-TYPE ::= {mtaGroupAssociationEntry 1}
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 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 mtaGroupErrorTable OBJECT-TYPE
SYNTAX SEQUENCE OF MtaGroupErrorEntry SYNTAX SEQUENCE OF MtaGroupErrorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table holding information regarding accumulated errors "The table holding information regarding accumulated errors
for each MTA group." for each MTA group."
::= {mta 5} ::= {mta 5}
mtaGroupErrorEntry OBJECT-TYPE mtaGroupErrorEntry OBJECT-TYPE
SYNTAX MtaGroupErrorEntry SYNTAX MtaGroupErrorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entry holding information regarding accumulated "The entry holding information regarding accumulated
errors for each MTA group." errors for each MTA group."
INDEX {applIndex, mtaGroupIndex, mtaStatusCode} INDEX {applIndex, mtaGroupIndex, mtaStatusCode}
::= {mtaGroupErrorTable 1} ::= {mtaGroupErrorTable 1}
MtaGroupErrorEntry ::= SEQUENCE { MtaGroupErrorEntry ::= SEQUENCE {
mtaStatusCode mtaStatusCode
INTEGER (4000000..5999999), INTEGER (4000000..5999999),
mtaGroupInboundErrorCount mtaGroupInboundErrorCount
Counter32, Counter32,
mtaGroupInternalErrorCount mtaGroupInternalErrorCount
Counter32, Counter32,
mtaGroupOutboundErrorCount mtaGroupOutboundErrorCount
Counter32 Counter32
} }
mtaGroupInboundErrorCount OBJECT-TYPE mtaGroupInboundErrorCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of the number of errors of a given type that have "Count of the number of errors of a given type that have
been accumulated in association with a particular group been accumulated in association with a particular group
while processing incoming messages. In the case of SMTP while processing incoming messages. In the case of SMTP
these will typically be errors reporting by an SMTP these will typically be errors reporting by an SMTP
server to the remote client; in the case of X.400 server to the remote client; in the case of X.400
these will typically be errors encountered while these will typically be errors encountered while
processing an incoming message." processing an incoming message."
::= {mtaGroupErrorEntry 1} ::= {mtaGroupErrorEntry 1}
mtaGroupInternalErrorCount OBJECT-TYPE mtaGroupInternalErrorCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of the number of errors of a given type that have "Count of the number of errors of a given type that have
been accumulated in association with a particular group been accumulated in association with a particular group
during internal MTA processing." during internal MTA processing."
::= {mtaGroupErrorEntry 2} ::= {mtaGroupErrorEntry 2}
mtaGroupOutboundErrorCount OBJECT-TYPE mtaGroupOutboundErrorCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of the number of errors of a given type that have "Count of the number of errors of a given type that have
been accumulated in association with a particular group's been accumulated in association with a particular group's
outbound connection activities. In the case of an SMTP outbound connection activities. In the case of an SMTP
client these will typically be errors reported while client these will typically be errors reported while
attempting to contact or while communicating with the attempting to contact or while communicating with the
remote SMTP server. In the case of X.400 these will remote SMTP server. In the case of X.400 these will
typically be errors encountered while constructing typically be errors encountered while constructing
or attempting to deliver an outgoing message." or attempting to deliver an outgoing message."
::= {mtaGroupErrorEntry 3} ::= {mtaGroupErrorEntry 3}
mtaStatusCode OBJECT-TYPE mtaStatusCode OBJECT-TYPE
SYNTAX INTEGER (4000000..5999999) 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 Status Code. Enhanced Mail System Status Codes are
defined in RFC 1893. These codes have the form defined in RFC 1893. These codes have the form
class.subject.detail class.subject.detail
Here 'class' is either 2, 4, or 5 and both 'subject' and Here 'class' is either 2, 4, or 5 and both 'subject' and
'detail' are integers in the range 0..999. Given a status 'detail' are integers in the range 0..999. Given a status
code the corresponding index value is defined to be code the corresponding index value is defined to be
((class * 1000) + subject) * 1000 + detail. Both SMTP ((class * 1000) + subject) * 1000 + detail. Both SMTP
error response codes and X.400 reason and diagnostic codes error response codes and X.400 reason and diagnostic codes
can be mapped into these codes, resulting in a namespace can be mapped into these codes, resulting in a namespace
capable of describing most error conditions a mail system capable of describing most error conditions a mail system
encounters in a generic yet detailed way." encounters in a generic yet detailed way."
::= {mtaGroupErrorEntry 4} ::= {mtaGroupErrorEntry 4}
-- 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
mtaCompliance MODULE-COMPLIANCE mtaCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for RFC 1566 implementations "The compliance statement for RFC 1566 implementations
which support the Mail Monitoring MIB for basic which support the Mail Monitoring MIB for basic
monitoring of MTAs." monitoring of MTAs."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {mtaRFC1566Group} MANDATORY-GROUPS {mtaRFC1566Group}
::= {mtaCompliances 1} ::= {mtaCompliances 1}
mtaAssocCompliance MODULE-COMPLIANCE mtaAssocCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for RFC 1566 implementations "The compliance statement for RFC 1566 implementations
which support the Mail Monitoring MIB for monitoring which support the Mail Monitoring MIB for monitoring
of MTAs and their associations." of MTAs and their associations."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {mtaRFC1566Group, mtaRFC1566AssocGroup} MANDATORY-GROUPS {mtaRFC1566Group, mtaRFC1566AssocGroup}
::= {mtaCompliances 2} ::= {mtaCompliances 2}
mtaRFC2249Compliance MODULE-COMPLIANCE mtaRFC2249Compliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for RFC 2249 implementations "The compliance statement for RFC 2249 implementations
which support the Mail Monitoring MIB for basic which support the Mail Monitoring MIB for basic
monitoring of MTAs." monitoring of MTAs."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {mtaRFC2249Group} MANDATORY-GROUPS {mtaRFC2249Group}
::= {mtaCompliances 5} ::= {mtaCompliances 5}
mtaRFC2249AssocCompliance MODULE-COMPLIANCE mtaRFC2249AssocCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for RFC 2249 implementations "The compliance statement for RFC 2249 implementations
which support the Mail Monitoring MIB for monitoring of which support the Mail Monitoring MIB for monitoring of
MTAs and their associations." MTAs and their associations."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup} MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup}
::= {mtaCompliances 6} ::= {mtaCompliances 6}
mtaRFC2249ErrorCompliance MODULE-COMPLIANCE mtaRFC2249ErrorCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for RFC 2249 implementations "The compliance statement for RFC 2249 implementations
which support the Mail Monitoring MIB for monitoring of which support the Mail Monitoring MIB for monitoring of
MTAs and detailed errors." MTAs and detailed errors."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249ErrorGroup} MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249ErrorGroup}
::= {mtaCompliances 7} ::= {mtaCompliances 7}
mtaRFC2249FullCompliance MODULE-COMPLIANCE mtaRFC2249FullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for RFC 2249 implementations "The compliance statement for RFC 2249 implementations
which support the full Mail Monitoring MIB for which support the full Mail Monitoring MIB for
monitoring of MTAs, associations, and detailed errors." monitoring of MTAs, associations, and detailed errors."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup, MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup,
mtaRFC2249ErrorGroup} mtaRFC2249ErrorGroup}
::= {mtaCompliances 8} ::= {mtaCompliances 8}
mtaRFCYYYYCompliance MODULE-COMPLIANCE mtaRFC2789Compliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for RFC YYYY implementations "The compliance statement for RFC 2789 implementations
which support the Mail Monitoring MIB for basic which support the Mail Monitoring MIB for basic
monitoring of MTAs." monitoring of MTAs."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {mtaRFCYYYYGroup} MANDATORY-GROUPS {mtaRFC2789Group}
::= {mtaCompliances 9} ::= {mtaCompliances 9}
mtaRFCYYYYAssocCompliance MODULE-COMPLIANCE mtaRFC2789AssocCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for RFC YYYY implementations "The compliance statement for RFC 2789 implementations
which support the Mail Monitoring MIB for monitoring of which support the Mail Monitoring MIB for monitoring of
MTAs and their associations." MTAs and their associations."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {mtaRFCYYYYGroup, mtaRFCYYYYAssocGroup} MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789AssocGroup}
::= {mtaCompliances 10} ::= {mtaCompliances 10}
mtaRFCYYYYErrorCompliance MODULE-COMPLIANCE mtaRFC2789ErrorCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for RFC YYYY implementations "The compliance statement for RFC 2789 implementations
which support the Mail Monitoring MIB for monitoring of which support the Mail Monitoring MIB for monitoring of
MTAs and detailed errors." MTAs and detailed errors."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {mtaRFCYYYYGroup, mtaRFCYYYYErrorGroup} MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789ErrorGroup}
::= {mtaCompliances 11} ::= {mtaCompliances 11}
mtaRFCYYYYFullCompliance MODULE-COMPLIANCE mtaRFC2789FullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for RFC YYYY implementations "The compliance statement for RFC 2789 implementations
which support the full Mail Monitoring MIB for which support the full Mail Monitoring MIB for
monitoring of MTAs, associations, and detailed errors." monitoring of MTAs, associations, and detailed errors."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {mtaRFCYYYYGroup, mtaRFCYYYYAssocGroup, MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789AssocGroup,
mtaRFCYYYYErrorGroup} mtaRFC2789ErrorGroup}
::= {mtaCompliances 12} ::= {mtaCompliances 12}
-- Units of conformance
mtaRFC1566Group OBJECT-GROUP mtaRFC1566Group OBJECT-GROUP
OBJECTS { OBJECTS {
mtaReceivedMessages, mtaStoredMessages, mtaReceivedMessages, mtaStoredMessages,
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
mtaTransmittedVolume, mtaReceivedRecipients, mtaTransmittedVolume, mtaReceivedRecipients,
mtaStoredRecipients, mtaTransmittedRecipients, mtaStoredRecipients, mtaTransmittedRecipients,
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,
mtaGroupAccumulatedInboundAssociations, mtaGroupAccumulatedInboundAssociations,
mtaGroupAccumulatedOutboundAssociations, mtaGroupAccumulatedOutboundAssociations,
mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity, mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
mtaGroupRejectedInboundAssociations, mtaGroupRejectedInboundAssociations,
mtaGroupFailedOutboundAssociations, mtaGroupFailedOutboundAssociations,
mtaGroupInboundRejectionReason, mtaGroupInboundRejectionReason,
mtaGroupOutboundConnectFailureReason, mtaGroupOutboundConnectFailureReason,
mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName} mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing basic monitoring of MTAs. "A collection of objects providing basic monitoring of MTAs.
This is the original set of such objects defined in RFC This is the original set of such objects defined in RFC
1566." 1566."
::= {mtaGroups 10}
mtaRFC1566AssocGroup OBJECT-GROUP ::= {mtaGroups 10}
OBJECTS {
mtaGroupAssociationIndex}
STATUS current
DESCRIPTION
"A collection of objects providing monitoring of MTA
associations. This is the original set of such objects
defined in RFC 1566."
::= {mtaGroups 11}
mtaRFC2249Group OBJECT-GROUP mtaRFC1566AssocGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mtaReceivedMessages, mtaStoredMessages, mtaGroupAssociationIndex}
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, STATUS current
mtaTransmittedVolume, mtaReceivedRecipients, DESCRIPTION
mtaStoredRecipients, mtaTransmittedRecipients, "A collection of objects providing monitoring of MTA
mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages, associations. This is the original set of such objects
mtaGroupReceivedMessages, mtaGroupRejectedMessages, defined in RFC 1566."
mtaGroupStoredMessages, mtaGroupTransmittedMessages, ::= {mtaGroups 11}
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}
STATUS current
DESCRIPTION
"A collection of objects providing basic monitoring of MTAs.
This group was originally defined in RFC 2249."
::= {mtaGroups 4}
mtaRFC2249AssocGroup OBJECT-GROUP mtaRFC2249Group OBJECT-GROUP
OBJECTS { OBJECTS {
mtaGroupAssociationIndex} mtaReceivedMessages, mtaStoredMessages,
STATUS current mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
DESCRIPTION mtaTransmittedVolume, mtaReceivedRecipients,
"A collection of objects providing monitoring of MTA mtaStoredRecipients, mtaTransmittedRecipients,
associations. This group was originally defined in RFC mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
2249." mtaGroupReceivedMessages, mtaGroupRejectedMessages,
::= {mtaGroups 5} 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}
STATUS current
DESCRIPTION
"A collection of objects providing basic monitoring of MTAs.
This group was originally defined in RFC 2249."
::= {mtaGroups 4}
mtaRFC2249ErrorGroup OBJECT-GROUP mtaRFC2249AssocGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mtaGroupInboundErrorCount, mtaGroupInternalErrorCount, mtaGroupAssociationIndex}
mtaGroupOutboundErrorCount}
STATUS current
DESCRIPTION
"A collection of objects providing monitoring of
detailed MTA errors. This group was originally defined
in RFC 2249."
::= {mtaGroups 6}
mtaRFCYYYYGroup OBJECT-GROUP STATUS current
OBJECTS { DESCRIPTION
mtaReceivedMessages, mtaStoredMessages, "A collection of objects providing monitoring of MTA
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, associations. This group was originally defined in RFC
mtaTransmittedVolume, mtaReceivedRecipients, 2249."
mtaStoredRecipients, mtaTransmittedRecipients, ::= {mtaGroups 5}
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}
STATUS current
DESCRIPTION
"A collection of objects providing basic monitoring of MTAs.
This is the appropriate group for RFC YYYY."
::= {mtaGroups 7}
mtaRFCYYYYAssocGroup OBJECT-GROUP mtaRFC2249ErrorGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mtaGroupAssociationIndex} mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
STATUS current mtaGroupOutboundErrorCount}
DESCRIPTION STATUS current
"A collection of objects providing monitoring of MTA DESCRIPTION
associations. This is the appropriate group for RFC "A collection of objects providing monitoring of
YYYY association monitoring." detailed MTA errors. This group was originally defined
::= {mtaGroups 8} in RFC 2249."
::= {mtaGroups 6}
mtaRFCYYYYErrorGroup OBJECT-GROUP mtaRFC2789Group OBJECT-GROUP
OBJECTS { OBJECTS {
mtaGroupInboundErrorCount, mtaGroupInternalErrorCount, mtaReceivedMessages, mtaStoredMessages,
mtaGroupOutboundErrorCount} mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
STATUS current mtaTransmittedVolume, mtaReceivedRecipients,
DESCRIPTION mtaStoredRecipients, mtaTransmittedRecipients,
"A collection of objects providing monitoring of mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
detailed MTA errors. This is the appropriate group mtaGroupReceivedMessages, mtaGroupRejectedMessages,
for RFC YYYY error monitoring." mtaGroupStoredMessages, mtaGroupTransmittedMessages,
::= {mtaGroups 9} 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}
STATUS current
DESCRIPTION
"A collection of objects providing basic monitoring of MTAs.
END This is the appropriate group for RFC 2789."
::= {mtaGroups 7}
7. Changes made since RFC 2249 mtaRFC2789AssocGroup OBJECT-GROUP
OBJECTS {
mtaGroupAssociationIndex}
STATUS current
DESCRIPTION
"A collection of objects providing monitoring of MTA
associations. This is the appropriate group for RFC
2789 association monitoring."
::= {mtaGroups 8}
This revision corrects a number of minor technical errors in the mtaRFC2789ErrorGroup OBJECT-GROUP
construction of the mail monitoring MIB in RFC 2249 [18]: OBJECTS {
mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
mtaGroupOutboundErrorCount}
STATUS current
DESCRIPTION
"A collection of objects providing monitoring of
detailed MTA errors. This is the appropriate group
for RFC 2789 error monitoring."
::= {mtaGroups 9}
(1) All DisplayStrings have been changed to SnmpAdminStrings, END
(2) the conformance groups for different versions of this MIB have 5. Changes made since RFC 2249
This revision corrects a number of minor technical errors in the
construction of the mail monitoring MIB in RFC 2249 [18]:
(1) All DisplayStrings have been changed to SnmpAdminStrings,
(2) the conformance groups for different versions of this MIB have
been corrected, been corrected,
(3) the required mtaStatusCode entry has been added to (3) the required mtaStatusCode entry has been added to
MtaGroupErrorEntry (which does not affect the bits on the wire in MtaGroupErrorEntry (which does not affect the bits on the wire in
any way), and any way), and
(4) the recommendation that an empty string be returned if the last (4) the recommendation that an empty string be returned if the last
operation was successful has been removed from operation was successful has been removed from
mtaGroupInboundRejectionReason and mtaGroupInboundRejectionReason and
mtaGroupOutboundConnectFailureReason as it conflicts with the mtaGroupOutboundConnectFailureReason as it conflicts with the
stated purpose of these variables. stated purpose of these variables.
8. Acknowledgements 6. Acknowledgements
This document is a work product of the Mail and Directory Management This document is a work product of the Mail and Directory Management
(MADMAN) Working Group of the IETF. It is based on an earlier MIB (MADMAN) Working Group of the IETF. It is based on an earlier MIB
designed by S. Kille, T. Lenggenhager, D. Partain, and W. Yeong. The designed by S. Kille, T. Lenggenhager, D. Partain, and W. Yeong. The
Electronic Mail Association's TSC committee was instrumental in Electronic Mail Association's TSC committee was instrumental in
providing feedback on and suggesting enhancements to RFC 1566 [19] that providing feedback on and suggesting enhancements to RFC 1566 [19]
have led to the present document. that have led to the present document.
9. References 7. References
[1] Harrington, D., Presuhn, R., and Wijnen, B., "An Architecture for [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2571, April 1999. Describing SNMP Management Frameworks", RFC 2571, April 1999.
[2] Rose, M. and McCloghrie, K., "Structure and Identification of [2] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155, May Management Information for TCP/IP-based Internets", STD 16, RFC
1990. 1155, May 1990.
[3] Rose, M. and McCloghrie, K., "Concise MIB Definitions", RFC 1212, [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
March 1991. RFC 1212, March 1991.
[4] Rose, M., "A Convention for Defining Traps for use with the SNMP", [4] Rose, M., "A Convention for Defining Traps for use with the
RFC 1215, March 1991. SNMP", RFC 1215, March 1991.
[5] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Structure of [5] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of
Management Information Version 2 (SMIv2)", RFC 2578, April 1999. Management Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999.
[6] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Textual [6] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual
Conventions for SMIv2", RFC 2579, April 1999. Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[7] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Conformance [7] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance
Statements for SMIv2", RFC 2580, April 1999. Statements for SMIv2", STD 58, RFC 2580, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M., and Davin, J., "Simple [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
Network Management Protocol", RFC 1157, May 1990. Network Management Protocol", STD 15, RFC 1157, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January 1996. "Introduction to Community-based SNMPv2", RFC 1901, January
1996.
[10] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
Mappings for Version 2 of the Simple Network Management Protocol Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, January 1996. (SNMPv2)", RFC 1906, January 1996.
[11] Case, J., Harrington D., Presuhn R., and Wijnen, B., "Message [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999. Protocol (SNMP)", RFC 2572, April 1999.
[12] Blumenthal, U., and Wijnen, B., "User-based Security Model (USM) [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol (SNMPv3)", for version 3 of the Simple Network Management Protocol
RFC 2574, April 1999. (SNMPv3)", RFC 2574, April 1999.
[13] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol Operations for Version 2 of the Simple Network Management
(SNMPv2)", RFC 1905, January 1996. Protocol (SNMPv2)", RFC 1905, January 1996.
[14] Levi, D., Meyer, P., and Stewart, B., "SNMPv3 Applications", RFC [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
2573, April 1999. 2573, April 1999.
[15] Wijnen, B., Presuhn, R., and McCloghrie, K., "View-based Access [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999. (SNMP)", RFC 2575, April 1999.
[16] Freed, N. and Kille, S., "The Network Services Monitoring MIB", [16] Freed, N. and S. Kille, "Network Services Monitoring MIB", RFC
Internet Draft, May 1999. 2788, March 2000.
[17] Wahl, M., Kille, S., Howes, T., "Lightweight Directory Access [17] Wahl, M., Kille, S. and T. Howes, "Lightweight Directory Access
Protocol (v3): UTF-8 String Representation of Distinguished Names", Protocol (v3): UTF-8 String Representation of Distinguished
RFC 2253, December 1997. Names", RFC 2253, December 1997.
[18] Freed, N. and Kille, S., "Mail Monitoring MIB", RFC 2249, January [18] Freed, N. and S. Kille, "Mail Monitoring MIB", RFC 2249, January
1998. 1998.
[19] Freed, N. and Kille, S., "Mail Monitoring MIB", RFC 1566, January [19] Freed, N. and S. Kille, "Mail Monitoring MIB", RFC 1566, January
1994. 1994.
[20] Kille, S., "Mapping between X.400(1988) and RFC 822/MIME", RFC [20] Kille, S., "Mapping between X.400(1988) and RFC 822/MIME", RFC
2156, January 1998. 2156, January 1998.
[21] Crocker, D., "Standard for the Format of ARPA Internet Text [21] Crocker, D., "Standard for the Format of ARPA Internet Text
Message", STD 11, RFC 822, August 1982. Message", STD 11, RFC 822, August 1982.
[22] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893, [22] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893,
January 1996. January 1996.
10. Security Considerations 8. Security Considerations
There are no management objects defined in this MIB that have a MAX- There are no management objects defined in this MIB that have a MAX-
ACCESS clause of read-write and/or read-create. So, if this MIB is ACCESS clause of read-write and/or read-create. So, if this MIB is
implemented correctly, then there is no risk that an intruder can alter implemented correctly, then there is no risk that an intruder can
or create any management objects of this MIB via direct SNMP SET alter or create any management objects of this MIB via direct SNMP
operations. SET operations.
However, this MIB does provide passive information about the existence, However, this MIB does provide passive information about the
type, and configuration of applications on a given host that could existence, type, and configuration of applications on a given host
potentially indicate some sort of vulnerability. Finally, the that could potentially indicate some sort of vulnerability. Finally,
information MIB provides about network usage could be used to analyze the information MIB provides about network usage could be used to
network traffic patterns. analyze network traffic patterns.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and GET/SET control as to who on the secure network is allowed to access and
(read/change/create/delete) the objects in this MIB. GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features It is recommended that the implementers consider the security
as provided by the SNMPv3 framework. Specifically, the use of the features as provided by the SNMPv3 framework. Specifically, the use
User-based Security Model RFC 2574 [12] and the View-based Access of the User-based Security Model RFC 2574 [12] and the View-based
Control Model RFC 2575 [15] is recommended. Access Control Model RFC 2575 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity It is then a customer/user responsibility to ensure that the SNMP
giving access to an instance of this MIB, is properly configured to give entity giving access to an instance of this MIB, is properly
access to the objects only to those principals (users) that have configured to give access to the objects only to those principals
legitimate rights to indeed GET or SET (change/create/delete) them. (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them.
11. Author and Chair Addresses 9. Author and Chair Addresses
Ned Freed Ned Freed
Innosoft International, Inc. Innosoft International, Inc.
1050 Lakes Drive 1050 Lakes Drive
West Covina, CA 91790 West Covina, CA 91790
USA USA
tel: +1 626 919 3600
fax: +1 626 919 3614
email: ned.freed@innosoft.com
Steve Kille, MADMAN WG Chair Phone: +1 626 919 3600
ISODE Consortium Fax: +1 626 919 3614
The Dome, The Square EMail: ned.freed@innosoft.com
Richmond TW9 1DT
UK
tel: +44 181 332 9091
email: S.Kille@isode.com
12. Full Copyright Statement Steve Kille, MADMAN WG Chair
MessagingDirect Ltd.
The Dome, The Square
Richmond TW9 1DT
UK
Copyright (C) The Internet Society (1999). All Rights Reserved. Phone: +44 20 8332 9091
EMail: Steve.Kille@MessagingDirect.com
This document and translations of it may be copied and furnished to 10. Full Copyright Statement
others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into
languages other than English.
The limited permissions granted above are perpetual and will not be Copyright (C) The Internet Society (2000). All Rights Reserved.
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS This document and translations of it may be copied and furnished to
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK others, and derivative works that comment on or otherwise explain it
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT or assist in its implementation may be prepared, copied, published
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT and distributed, in whole or in part, without restriction of any
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR kind, provided that the above copyright notice and this paragraph are
FITNESS FOR A PARTICULAR PURPOSE. included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 185 change blocks. 
1279 lines changed or deleted 1330 lines changed or added

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