view Side-By-Side changes

Network Working Group                              Steve Kille, WG Chair
Internet Draft                                         Ned Freed, Editor
draft-ietf-madman-mail-monitor-mib-00.txt
                             <draft-ietf-madman-mail-monitor-mib-02.txt>



                          Mail Monitoring MIB

                             November 1995

                              August 1996




                          Status of this Memo

This document is an Internet-Draft.  Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working
documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months.
Internet-Drafts may be updated, replaced, or obsoleted by other
documents at any time.  It is not appropriate to use Internet-Drafts as
reference material or to cite them other than as a ``working draft'' or
``work in progress.''

To learn the current status of any Internet-Draft, please check the
1id-abstracts.txt listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe),
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).


1.  Introduction

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In
particular, this memo extends the basic Network Services Monitoring MIB
[5] to allow monitoring of Message Transfer Agents (MTAs). It may also
be used to monitor MTA components within gateways.

















Internet Draft            Mail Monitoring MIB              November 1995                August 1996


2.  Table of Contents

1 Introduction ....................................................    1
2 Table of Contents ...............................................    2
3 The SNMPv2 Network Management Framework .........................    2
3.1 Object Definitions ............................................    2
4 Message Flow Model ..............................................    3
5 MTA Objects .....................................................    3
6 Definitions .....................................................    5    4
7 Changes made since RFC1565 ......................................   22 RFC 1566 .....................................   27
8 Acknowledgements ................................................   23   28
9 References ......................................................   23   28
10 Security Considerations ........................................   23   29
11 Authors' Addresses .............................................   24   29


3.  The SNMPv2 Network Management Framework

The SNMPv2 Network Management Framework consists of four major
components. They are:

o    RFC 1442 1902 [1] which defines the SMI, the mechanisms used for
     describing and naming objects for the purpose of management.

o    RFC 1213 [2] defines MIB-II, the core set of managed objects for
     the Internet suite of protocols.

o    RFC 1445 [3] which defines the administrative and other
     architectural aspects of the framework.

o    RFC 1448 1905 [4] which defines the protocol used for network access to
     managed objects.

The Framework permits new objects to be defined for the purpose of
experimentation and evaluation.


3.1.  Object Definitions

Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined using
the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI.
In particular, each object type is named by an OBJECT IDENTIFIER, an
administratively assigned name. The object type together with an object
instance serves to uniquely identify a specific instantiation of the





Expires May 1996 Frebruary 1997                                          [Page 2]





Internet Draft            Mail Monitoring MIB              November 1995                August 1996


object.  For human convenience, we often use a textual string, termed
the descriptor, to refer to the object type.


4.  Message Flow Model

A general model of message flow inside an MTA has to be presented before
a MIB can be described. Generally speaking, message flow occurs in four
steps:

 (1)   Messages are received by the MTA from User Agents, Message
       Stores, other MTAs, and gateways.

 (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
       may not be the final destination of the message. Multiple "next
       hops" may exist for a single message (as a result of either
       having multiple recipients or distribution list expansion); this
       may make it necessary to duplicate messages.

 (3)   Messages   If necessary messages are converted into the format that's
       appropriate for the next hop. Conversion operations may be
       successful or unsuccessful.

 (4)   Messages are transmitted to the appropriate destination, which
       may be a User Agent, Message Store, another MTA, or gateway.

Storage of messages in the MTA occurs at some point during this process.
However, it is important to note that storage may occur at different and
possibly even multiple points during this process. For example, some
MTAs expand messages into multiple copies as they are received. In this
case (1), (2), and (3) may all occur prior to storage. Other MTAs store
messages precisely as they are received and perform all expansions and
conversions during retransmission processing. So here only (1) occurs
prior to storage.  This leads to situations where, in general, a
measurement of messages received may not equal a measurement of messages
in store, or a measurement of messages stored may not equal a
measurement of messages retransmitted, or both.


5.  MTA Objects

If there are one or more MTAs on the host, the following mta group MIB may be used
to monitor them. Any number of the MTAs on a host may be monitored. Each
MTA is dealt with as a separate application and has its own applTable entry in the Network Services Monitoring MIB.





Expires May 1996 Frebruary 1997                                          [Page 3]





Internet Draft            Mail Monitoring MIB              November 1995                August 1996


entry in the Network Services Monitoring MIB.

The MIB described in this document covers only the portion which is
specific to the monitoring of MTAs. The network service related part of
the MIB is covered in a separate document [5].


6.  Definitions

MTA-MIB DEFINITIONS ::= BEGIN

IMPORTS
    OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY
      FROM SNMPv2-SMI
    DisplayString, TimeInterval
      FROM SNMPv2-TC
    MODULE-COMPLIANCE, OBJECT-GROUP
      FROM SNMPv2-CONF
    mib-2
      FROM RFC1213-MIB
    applIndex
      FROM APPLICATION-MIB;


-- Textual conventions

-- Uniform Resource Locators are stored in URLStrings.

URLString ::= TEXTUAL-CONVENTION
    STATUS current
    DESCRIPTION
        "A Uniform Resource Locator represented in accordance
         with RFC 1738 [7]."
    SYNTAX DisplayString
















Expires Frebruary 1997                                          [Page 4]





Internet Draft            Mail Monitoring MIB                August 1996


mta MODULE-IDENTITY
    LAST-UPDATED "9511170000Z" "9608270000Z"
    ORGANIZATION "IETF Mail and Directory Management Working Group"
    CONTACT-INFO
      "        Ned Freed

       Postal: Innosoft International, Inc.
               1050 East Garvey Avenue South
               West Covina, CA 91790
               US

       Tel: +1 818 919 3600
       Fax: +1 818 919 3614

       E-Mail: ned@innosoft.com"
    DESCRIPTION
      "The MIB module describing Message Transfer Agents (MTAs)"
    ::= {mib-2 28}











Expires May 1996                                                [Page 4]





Internet Draft            Mail Monitoring MIB              November 1995

mtaTable OBJECT-TYPE
    SYNTAX SEQUENCE OF MtaEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
      "The table holding information specific to an MTA."
    ::= {mta 1}

mtaStatusCode OBJECT-TYPE
    SYNTAX INTEGER (40000..59999)
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
      "An index capable of representing an Enhanced Mail System
       Status Code.  Enhanced Mail System Status Codes are defined
       in RFC 1893 [11].  Both SMTP error response codes and X.400
       reason and diagnostic codes can be mapped into these codes.
       Specifically, given a status code of the form
       class.subject.detail, the corresponding index value is
       defined to be ((class * 100) + subject) * 100 + detail."











Expires Frebruary 1997                                          [Page 5]





Internet Draft            Mail Monitoring MIB                August 1996


mtaEntry OBJECT-TYPE
    SYNTAX MtaEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
      "The entry associated with each MTA."
    INDEX {applIndex}
    ::= {mtaTable 1}

MtaEntry ::= SEQUENCE {
    mtaReceivedMessages
      Counter32,
    mtaStoredMessages
      Gauge32,
    mtaTransmittedMessages
      Counter32,
    mtaReceivedVolume
      Counter32,
    mtaStoredVolume
      Gauge32,
    mtaTransmittedVolume
      Counter32,
    mtaReceivedRecipients
      Counter32,
    mtaStoredRecipients
      Gauge32,
    mtaTransmittedRecipients
      Counter32
      Counter32,
    mtaSuccessfulConvertedMessages
      Counter32,
    mtaFailedConvertedMessages
      Counter32,
    mtaLoopsDetected
      Counter32,
    mtaDescription
      DisplayString,
    mtaURL,
      URLString
}











Expires Frebruary 1997                                          [Page 6]





Internet Draft            Mail Monitoring MIB                August 1996


mtaReceivedMessages OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The number of messages received since MTA initialization.
       This includes messages transmitted to this MTA from other





Expires May 1996                                                [Page 5]





Internet Draft            Mail Monitoring MIB              November 1995
       MTAs as well as messages that have been submitted to the
       MTA directly by end-users or applications."
    ::= {mtaEntry 1}

mtaStoredMessages OBJECT-TYPE
    SYNTAX Gauge32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number of messages currently stored in the MTA.
       This includes messages that are awaiting transmission to
       some other MTA or are waiting for delivery to an end-user
       or application."
    ::= {mtaEntry 2}

mtaTransmittedMessages OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The number of messages transmitted since MTA initialization.
       This includes messages that were transmitted to some other
       MTA or are waiting for delivery to an end-user or
       application."
    ::= {mtaEntry 3}


















Expires Frebruary 1997                                          [Page 7]





Internet Draft            Mail Monitoring MIB                August 1996


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







Expires May 1996                                                [Page 6]





Internet Draft            Mail Monitoring MIB              November 1995

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
















Expires Frebruary 1997                                          [Page 8]





Internet Draft            Mail Monitoring MIB                August 1996


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

mtaReceivedRecipients OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number of recipients specified in all messages
       received since MTA initialization.  Recipients this MTA
       has no responsibility for, i.e. inactive envelope
       recipients or ones referred to in message headers,
       should not be counted even if information about such
       recipients is available.  This includes messages





Expires May 1996                                                [Page 7]





Internet Draft            Mail Monitoring MIB              November 1995
       transmitted to this MTA from other MTAs as well as
       messages that have been submitted to the MTA directly
       by end-users or applications."
    ::= {mtaEntry 7}

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





Expires Frebruary 1997                                          [Page 9]





Internet Draft            Mail Monitoring MIB                August 1996


    ::= {mtaEntry 8}

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


-- MTAs typically group inbound reception, queue storage, and
-- outbound transmission in some way. In the most extreme case
-- information will be maintained for each different entity that
-- receives messages and for each entity the MTA stores messages for
-- and delivers

mtaSuccessfulConvertedMessages OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The number of messages to.  Other MTAs may elect that have been successfully
       converted from one form to treat all
-- reception equally, all queue storage equally, all deliveries
-- equally, or some combination another since MTA
       initialization."
    ::= {mtaEntry 10}

mtaFailedConvertedMessages OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The number of this.

-- In any case, a grouping abstraction is an extremely useful messages for
-- breaking down the activities of which an MTA. For purposes of labelling
-- this will be called a "group" in this MIB. unsuccessful
       attempt was made to convert them from one form to
       another since MTA initialization."
    ::= {mtaEntry 11}















Expires May 1996 Frebruary 1997                                         [Page 8] 10]





Internet Draft            Mail Monitoring MIB              November 1995


-- Each group contains all                August 1996


mtaLoopsDetected OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "A message loop is defined as a situation where the variables needed MTA
       decides that a given message will never be delivered to monitor all aspects
--
       one or more recipients and instead will continue to
       loop endlessly through one or more MTAs.  This variable
       counts the number of an MTA's operation.  However, times the fact that all groups contain
-- all possible variables does not imply MTA has detected such a
       situation since MTA initialization. Note that all groups must the
       mechanism MTAs use all
-- possible variables. For example, a single group might be used to
-- monitor only one kind detect loops (e.g. trace field
       counting, count of event (inbound processing, outbound
-- processing, or storage). In references to this sort of configuration all unused
-- counters would be inaccessible; e.g., returning either MTA in a
-- noSuchName error (for an SNMPv1 get), 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 noSuchInstance
-- exception (for an SNMPv2 get).

-- Groups loop once it is detected (e.g. looping
       messages are not necessarily mutually exclusive. A given event may
-- held, looping messages are bounced or sent
       to the postmaster, messages that the MTA knows will loop
       won't be recorded by more than one group, a message may be seen as
-- stored by more than accepted, etc.) vary widely from one group, MTA to the
       next and so on.  Groups should cannot be all
-- inclusive, however: if groups are implemented all aspects inferred from this variable."
    ::= {mtaEntry 12}

mtaDescription OBJECT-TYPE
    SYNTAX DisplayString
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "A description of an
-- MTA's operation should be registered in at least one group. the MTA.  This
-- freedom lets implementors use different sets of groups information is
       intended to
-- provide differents "views" identify the MTA in a status display."
    ::= {mtaEntry 13}

mtaURL OBJECT-TYPE
    SYNTAX URLString
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "A URL pointing to a description of an the MTA.

-- The possibility of overlap between groups means that summing
-- variables across groups may not produce values equal  This
       information is intended to those identify and describe the MTA
       in a status display."
    ::= {mtaEntry 14}









Expires Frebruary 1997                                         [Page 11]





Internet Draft            Mail Monitoring MIB                August 1996


-- the mtaTable. mtaTable should always provide accurate information MTAs typically group inbound reception, queue storage, and
-- about outbound transmission in some way, rather than accounting for
-- such operations only across the MTA as a whole. In the most
-- The term "channel" is often used in extreme case separate information will be maintained for each
-- different entity that receives messages and for each entity
-- the MTA implementations; channels stores messages for and delivers messages to.  Other
-- are usually, but not always, equivalent MTAs may elect to a group. However, treat all reception equally, all queue
-- this MIB does not use the term "channel" because there is no storage equally, all deliveries equally, or some combination
-- requirement that of this. Overlapped groupings are also possible, where an MTA
-- decomposes its traffic in different ways for different
-- purposes.

-- In any case, a grouping abstraction is an extremely useful for
-- breaking down the activities of an MTA. For purposes of
-- labelling this will be called a "group" in this MIB.

-- Each group contains all the variables needed to monitor all
-- aspects of an MTA's operation.  However, the fact that all
-- groups contain all possible variables does not imply that all
-- groups must use all possible variables. For example, a single
-- group might be used to monitor only one kind of event (inbound
-- processing, outbound processing, or storage). In this sort of
-- configuration all unused counters would be inaccessible; e.g.,
-- returning either a noSuchName error (for an SNMPv1 get), or a
-- noSuchInstance exception (for an SNMPv2 get).

-- Groups can be created at any time after MTA initialization. Once
-- a group is created it should not be deleted or its mtaGroupIndex
-- changed unless the MTA is reinitialized.

-- Groups are not necessarily mutually exclusive. A given event may
-- be recorded by more than one group, a message may be seen as
-- stored by more than one group, and so on.  Groups should be all
-- inclusive, however: if groups are implemented all aspects of an
-- MTA's operation should be registered in at least one group. This
-- freedom lets implementors use different sets of groups to
-- provide differents "views" of an MTA.

-- The possibility of overlap between groups means that summing
-- variables across groups may not produce values equal to those in
-- the mtaTable. mtaTable should always provide accurate information
-- about the MTA as a whole.








Expires Frebruary 1997                                         [Page 12]





Internet Draft            Mail Monitoring MIB                August 1996


-- The term "channel" is often used in MTA implementations; channels
-- are usually, but not always, equivalent to a group. However,
-- this MIB does not use the term "channel" because there is no
-- requirement that an MTA supporting this MIB has to map its
-- "channel" abstraction one-to-one onto the MIB's group abstration.

-- An MTA may create a group or group of groups at any time. Once
-- created, however, an MTA cannot delete an entry for a group from
-- the group table.  Deletation is only allowed when the MTA is
-- reinitialized, and is not required even then.  This restriction
-- is imposed so that monitoring agents can rely on group
-- assignments being consistent across multiple query operations.

-- Groups may be laid out so as to form a hierarchical arrangement,
-- with some groups acting as subgroups for other groups.
-- Alternately, disjoint groups of groups may be used to provide
-- different sorts of "snapshots" of MTA operation.  The
-- mtaGroupHierarchy variable provides an indication of how each
-- group fits into the overall arrangement being used.

mtaGroupTable OBJECT-TYPE
    SYNTAX SEQUENCE OF MtaGroupEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
      "The table holding information specific to each MTA group."
    ::= {mta 2}

mtaGroupEntry OBJECT-TYPE
    SYNTAX MtaGroupEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
      "The entry associated with each MTA group."
    INDEX {applIndex, mtaGroupIndex}
    ::= {mtaGroupTable 1}

MtaGroupEntry ::= SEQUENCE {
    mtaGroupIndex
        INTEGER,
    mtaGroupReceivedMessages
        Counter32,
    mtaGroupRejectedMessages
        Counter32,
    mtaGroupStoredMessages





Expires Frebruary 1997                                         [Page 13]





Internet Draft            Mail Monitoring MIB                August 1996


        Gauge32,
    mtaGroupTransmittedMessages
        Counter32,
    mtaGroupReceivedVolume
        Counter32,
    mtaGroupStoredVolume
        Gauge32,
    mtaGroupTransmittedVolume
        Counter32,
    mtaGroupReceivedRecipients
        Counter32,
    mtaGroupStoredRecipients
        Gauge32,
    mtaGroupTransmittedRecipients
        Counter32,
    mtaGroupOldestMessageStored
        TimeInterval,
    mtaGroupInboundAssociations
        Gauge32,
    mtaGroupOutboundAssociations
        Gauge32,
    mtaGroupAccumulatedInboundAssociations
        Counter32,
    mtaGroupAccumulatedOutboundAssociations
        Counter32,
    mtaGroupLastInboundActivity
        TimeInterval,
    mtaGroupLastOutboundActivity
        TimeInterval,
    mtaGroupLastOutboundAssociationAttempt
        TimeInterval,
    mtaGroupRejectedInboundAssociations
        Counter32,
    mtaGroupFailedOutboundAssociations
        Counter32,
    mtaGroupInboundRejectionReason
        DisplayString,
    mtaGroupOutboundConnectFailureReason
        DisplayString,
    mtaGroupScheduledRetry
        TimeInterval,
    mtaGroupMailProtocol
        OBJECT IDENTIFIER,
    mtaGroupName
        DisplayString,





Expires Frebruary 1997                                         [Page 14]





Internet Draft            Mail Monitoring MIB                August 1996


    mtaGroupSuccessfulConvertedMessages
        Counter32,
    mtaGroupFailedConvertedMessages
        Counter32,
    mtaGroupDescription
        DisplayString,
    mtaGroupURL
        URLString,
    mtaGroupCreationTime
        TimeInterval,
    mtaGroupHierarchy
        INTEGER,
    mtaGroupOldestMessageId
        DisplayString,
    mtaGroupLoopsDetected
        Counter32
}

mtaGroupIndex OBJECT-TYPE
    SYNTAX INTEGER (1..2147483647)
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
      "The index associated with a group for a given MTA."
    ::= {mtaGroupEntry 1}

mtaGroupReceivedMessages OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The number of messages received to this group since
       group creation."
    ::= {mtaGroupEntry 2}

mtaGroupRejectedMessages OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The number of messages rejected by this group since
       group creation."
    ::= {mtaGroupEntry 3}







Expires Frebruary 1997                                         [Page 15]





Internet Draft            Mail Monitoring MIB                August 1996


mtaGroupStoredMessages OBJECT-TYPE
    SYNTAX Gauge32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number of messages currently stored in this
       group's queue."
    ::= {mtaGroupEntry 4}

mtaGroupTransmittedMessages OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The number of messages transmitted by this group since
       group creation."
    ::= {mtaGroupEntry 5}

mtaGroupReceivedVolume OBJECT-TYPE
    SYNTAX Counter32
    UNITS "K-octets"
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total volume of messages received to this group since
       group creation, measured in kilo-octets.  This volume
       should include all transferred data that is logically above
       the mail transport protocol level.  For example, an
       SMTP-based MTA should use the number of kilo-octets in the
       message header and body, while an X.400-based MTA should use
       the number of kilo-octets of P2 data."
    ::= {mtaGroupEntry 6}


















Expires Frebruary 1997                                         [Page 16]





Internet Draft            Mail Monitoring MIB                August 1996


mtaGroupStoredVolume OBJECT-TYPE
    SYNTAX Gauge32
    UNITS "K-octets"
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total volume of messages currently stored in this
       group's queue, measured in kilo-octets.  This volume should
       include all stored data that is logically above the mail
       transport protocol level.  For example, an SMTP-based
       MTA should use the number of kilo-octets in the message
       header and body, while an X.400-based MTA would use the
       number of kilo-octets of P2 data."
    ::= {mtaGroupEntry 7}

mtaGroupTransmittedVolume OBJECT-TYPE
    SYNTAX Counter32
    UNITS "K-octets"
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total volume of messages transmitted by this group
       since group creation, measured in kilo-octets.  This
       volume should include all transferred data that is logically
       above the mail transport protocol level.  For example, an
       SMTP-based MTA should use the number of kilo-octets in the
       message header and body, while an X.400-based MTA supporting this MIB has to map its
-- "channel" abstraction one-to-one onto should use
       the MIB's group abstration.

mtaGroupTable OBJECT-TYPE
    SYNTAX SEQUENCE OF MtaGroupEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
      "The table holding information specific to each MTA group." number of kilo-octets of P2 data."
    ::= {mta 2}

mtaGroupEntry {mtaGroupEntry 8}

mtaGroupReceivedRecipients OBJECT-TYPE
    SYNTAX MtaGroupEntry Counter32
    MAX-ACCESS not-accessible read-only
    STATUS current
    DESCRIPTION
      "The entry associated with each total number of recipients specified in all messages
       received to this group since group creation.
       Recipients this MTA group."
    INDEX {applIndex, mtaGroupIndex} has no responsibility for should not
       be counted."
    ::= {mtaGroupTable 1} {mtaGroupEntry 9}










Expires May 1996 Frebruary 1997                                         [Page 9] 17]





Internet Draft            Mail Monitoring MIB              November 1995


MtaGroupEntry ::= SEQUENCE {
    mtaGroupIndex
        INTEGER,
    mtaGroupReceivedMessages
        Counter32,
    mtaGroupRejectedMessages
        Counter32,
    mtaGroupStoredMessages
        Gauge32,
    mtaGroupTransmittedMessages
        Counter32,
    mtaGroupReceivedVolume
        Counter32,
    mtaGroupStoredVolume
        Gauge32,
    mtaGroupTransmittedVolume
        Counter32,
    mtaGroupReceivedRecipients
        Counter32,
    mtaGroupStoredRecipients
        Gauge32,
    mtaGroupTransmittedRecipients
        Counter32,
    mtaGroupOldestMessageStored
        TimeInterval,
    mtaGroupInboundAssociations
        Gauge32,
    mtaGroupOutboundAssociations
        Gauge32,
    mtaGroupAccumulatedInboundAssociations
        Counter32,
    mtaGroupAccumulatedOutboundAssociations
        Counter32,
    mtaGroupLastInboundActivity
        TimeInterval,
    mtaGroupLastOutboundActivity
        TimeInterval,
    mtaGroupRejectedInboundAssociations
        Counter32,
    mtaGroupFailedOutboundAssociations
        Counter32,
    mtaGroupInboundRejectionReason
        DisplayString,
    mtaGroupOutboundConnectFailureReason
        DisplayString,





Expires May                August 1996                                               [Page 10]





Internet Draft            Mail Monitoring MIB              November 1995


    mtaGroupScheduledRetry
        TimeInterval,
    mtaGroupMailProtocol
        OBJECT IDENTIFIER,
    mtaGroupName
        DisplayString
}

mtaGroupIndex


mtaGroupStoredRecipients OBJECT-TYPE
    SYNTAX INTEGER (1..2147483647) Gauge32
    MAX-ACCESS not-accessible read-only
    STATUS current
    DESCRIPTION
      "The index associated with a group total number of recipients specified in all messages
       currently stored in this group's queue.  Recipients this
       MTA has no responsibility for a given MTA." should not be counted."
    ::= {mtaGroupEntry 1}

mtaGroupReceivedMessages 10}

mtaGroupTransmittedRecipients OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number of recipients specified in all messages received to
       transmitted by this group since group creation.
       Recipients this MTA
       initialization." had no responsibility for should not
       be counted."
    ::= {mtaGroupEntry 2}

mtaGroupRejectedMessages 11}

mtaGroupOldestMessageStored OBJECT-TYPE
    SYNTAX Counter32 TimeInterval
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The number of messages rejected by this group
      "Time since MTA
       initialization." the oldest message in this group's queue was
       placed in the queue."
    ::= {mtaGroupEntry 3}

mtaGroupStoredMessages 12}

mtaGroupInboundAssociations OBJECT-TYPE
    SYNTAX Gauge32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number of messages currently stored in this
       group's queue." current associations to the group, where the
       group is the responder."
    ::= {mtaGroupEntry 4} 13}












Expires May 1996 Frebruary 1997                                         [Page 11] 18]





Internet Draft            Mail Monitoring MIB              November 1995


mtaGroupTransmittedMessages                August 1996


mtaGroupOutboundAssociations OBJECT-TYPE
    SYNTAX Counter32 Gauge32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The number of messages transmitted by this current associations to the group, where the
      group since MTA
       initialization." is the initiator."
    ::= {mtaGroupEntry 5}

mtaGroupReceivedVolume 14}

mtaGroupAccumulatedInboundAssociations OBJECT-TYPE
    SYNTAX Counter32
    UNITS "K-octets"
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total volume number of messages received associations to this the group since
       MTA initialization, measured in kilo-octets.  This volume
       should include all transferred data that is logically above
      group creation, where the mail transport protocol level.  For example, an
       SMTP-based MTA should use was the responder."
    ::= {mtaGroupEntry 15}

mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number of kilo-octets in associations from the group since
       group creation, where the
       message header and body, while an X.400-based MTA should use was the number of kilo-octets of P2 data." initiator."
    ::= {mtaGroupEntry 6}

mtaGroupStoredVolume 16}

mtaGroupLastInboundActivity OBJECT-TYPE
    SYNTAX Gauge32
    UNITS "K-octets" TimeInterval
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total volume of messages currently stored in this
       group's queue, measured in kilo-octets.  This volume should
       include all stored data that is logically above
      "Time since the mail
       transport protocol level.  For example, last time that this group had an SMTP-based
       MTA should use the number active
      inbound association for purposes of kilo-octets in the message
       header and body, while an X.400-based MTA would use reception."
    ::= {mtaGroupEntry 17}

mtaGroupLastOutboundActivity OBJECT-TYPE
    SYNTAX TimeInterval
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "Time since the
       number of kilo-octets last time that this group had a
       successful outbound association for purposes of P2 data."
       message delivery."
    ::= {mtaGroupEntry 7} 18}





Expires May 1996 Frebruary 1997                                         [Page 12] 19]





Internet Draft            Mail Monitoring MIB              November 1995


mtaGroupTransmittedVolume                August 1996


mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE
    SYNTAX Counter32
    UNITS "K-octets" TimeInterval
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total volume of messages transmitted by
      "Time since the last time that this group
       since MTA initialization, measured in kilo-octets.  This
       volume should include all transferred data that is logically
       above the mail transport protocol level.  For example, attempted
       to make an
       SMTP-based MTA should use the number outbound association for purposes 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." delivery."
    ::= {mtaGroupEntry 8}

mtaGroupReceivedRecipients 34}

mtaGroupRejectedInboundAssociations OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number of recipients specified in all messages
       received to this inbound associations the group since MTA initialization.
       Recipients this MTA has no responsibility for should
      rejected, since group creation.  Rejected
      associations are not
       be counted." counted in the accumulated
      association totals."
    ::= {mtaGroupEntry 9}

mtaGroupStoredRecipients 19}

mtaGroupFailedOutboundAssociations OBJECT-TYPE
    SYNTAX Gauge32 Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number of recipients specified in all messages
       currently stored in this group's queue.  Recipients this
       MTA associations where the group was the
      initiator and association establishment has no responsibility for should failed,
      since group creation.  Failed associations are
      not be counted." counted in the accumulated association totals."
    ::= {mtaGroupEntry 10}

mtaGroupTransmittedRecipients 20}

mtaGroupInboundRejectionReason OBJECT-TYPE
    SYNTAX Counter32 DisplayString
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number of recipients specified in all messages
       transmitted by failure reason, if any, for the last association this
      group refused to respond to. An empty string indicates that
      the last attempt was successful.  If no association attempt
      has been made since the MTA initialization.
       Recipients this MTA had no responsibility for was initialized the value
      should not be counted." 'never'."
    ::= {mtaGroupEntry 21}







Expires May 1996 Frebruary 1997                                         [Page 13] 20]





Internet Draft            Mail Monitoring MIB              November 1995


    ::= {mtaGroupEntry 11}

mtaGroupOldestMessageStored                August 1996


mtaGroupOutboundConnectFailureReason OBJECT-TYPE
    SYNTAX TimeInterval DisplayString
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "Time since
      "The failure reason, if any, for the oldest message in last association attempt
      this group's queue group initiated. An empty string indicates that the last
      attempt was successful.  If no association attempt has been
      made since the MTA was
       placed in initialized the queue." value should be
      'never'."
    ::= {mtaGroupEntry 12}

mtaGroupInboundAssociations 22}

mtaGroupScheduledRetry OBJECT-TYPE
    SYNTAX Gauge32 TimeInterval
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The number of current associations to the group, where the time when this group is the responder." scheduled to next attempt to
       make an association."
    ::= {mtaGroupEntry 13}

mtaGroupOutboundAssociations 23}

mtaGroupMailProtocol OBJECT-TYPE
    SYNTAX Gauge32 OBJECT IDENTIFIER
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The number
      "An identification of current associations to the group, where the protocol being used by this group.
      For an group is employing OSI protocols, this will be the initiator."
    ::= {mtaGroupEntry 14}

mtaGroupAccumulatedInboundAssociations OBJECT-TYPE
    SYNTAX Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number
      Application Context.  For Internet applications, the IANA
      maintains a registry of associations to the group since MTA
      initialization, where OIDs which correspond to well-known
      message transfer protocols.  If the group application protocol is
      not listed in the responder." registry, an OID value of the form
      {applTCPProtoID port} or {applUDProtoID port} are used for
      TCP-based and UDP-based protocols, respectively.  In either
      case 'port' corresponds to the primary port number being
      used by the group.  applTCPProtoID and applUDPProtoID are
      defined in [5]."
    ::= {mtaGroupEntry 15} 24}












Expires May 1996 Frebruary 1997                                         [Page 14] 21]





Internet Draft            Mail Monitoring MIB              November 1995


mtaGroupAccumulatedOutboundAssociations                August 1996


mtaGroupName OBJECT-TYPE
    SYNTAX Counter32 DisplayString
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number of associations from
      "A descriptive name for the group. If this group since connects to
       a single remote MTA
       initialization, where this should be the group was name of that MTA. If
       this in turn is an Internet MTA this should be the initiator." domain
       name.  For an OSI MTA it should be the string encoded
       distinguished name of the managed object using the format
       defined in RFC 1779 [6]. For X.400(1984) MTAs which do not
       have a Distinguished Name, the RFC 1327 [9] syntax
       'mta in globalid' should be used."
    ::= {mtaGroupEntry 16}

mtaGroupLastInboundActivity 25}

mtaGroupSuccessfulConvertedMessages OBJECT-TYPE
    SYNTAX TimeInterval Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "Time since the last time
      "The number of messages that have been successfully
       converted from one form to another in this group had an active
      inbound association for purposes of message reception."
       since group creation."
    ::= {mtaGroupEntry 17}

mtaGroupLastOutboundActivity 26}

mtaGroupFailedConvertedMessages OBJECT-TYPE
    SYNTAX TimeInterval Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "Time since the last time that
      "The number of messages for which an unsuccessful
       attempt was made to convert them from one form to
       another in this group had an
      outbound association for purposes of message delivery." since group creation."
    ::= {mtaGroupEntry 18}

mtaGroupRejectedInboundAssociations 27}

mtaGroupDescription OBJECT-TYPE
    SYNTAX Counter32 DisplayString
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number
      "A description of inbound associations the group's purpose.  This information is
       intended to identify the group has
      rejected, since MTA initialization.  Rejected
      associations are not counted in the accumulated
      association totals." a status display."
    ::= {mtaGroupEntry 19} 28}







Expires May 1996 Frebruary 1997                                         [Page 15] 22]





Internet Draft            Mail Monitoring MIB              November 1995


mtaGroupFailedOutboundAssociations                August 1996


mtaGroupURL OBJECT-TYPE
    SYNTAX Counter32 URLString
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The total number associations where the group was
      "A URL pointing to a description of the
      initiator group.  This
       information is intended to identify and association establishment has failed,
      since MTA initialization.  Failed associations are
      not counted in the accumulated association totals."
    ::= {mtaGroupEntry 20}

mtaGroupInboundRejectionReason OBJECT-TYPE
    SYNTAX DisplayString
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The failure reason, if any, for describe the last association this group refused to respond to. An empty string indicates that
      the last attempt was successful.  If no association attempt
      has been made since the MTA was initialized the value
      should be 'never'."
       in a status display."
    ::= {mtaGroupEntry 21}

mtaGroupOutboundConnectFailureReason {mtaEntry 29}

mtaGroupCreationTime OBJECT-TYPE
    SYNTAX DisplayString TimeInterval
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The failure reason, if any, for the last association attempt
      "Time since this group initiated. An empty string indicates that the last
      attempt was successful.  If no association attempt has been
      made since the MTA was initialized the value should be
      'never'." first created."
    ::= {mtaGroupEntry 22}

mtaGroupScheduledRetry 30}

mtaGroupHierarchy OBJECT-TYPE
    SYNTAX TimeInterval INTEGER (-2147483648..2147483647)
    MAX-ACCESS read-only not-accessible
    STATUS current
    DESCRIPTION
      "The time when
      "Describes how this group fits into the hierarchy. A
       positive value is scheduled to next attempt to
       make interpreted as an association." 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 23}







Expires May 1996                                               [Page 16]





Internet Draft            Mail Monitoring MIB              November 1995


mtaGroupMailProtocol 31}

mtaGroupOldestMessageId OBJECT-TYPE
    SYNTAX OBJECT IDENTIFIER DisplayString
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "An identification of the protocol being used by this group.
      For an group employing OSI protocols, this will be the
      Application Context.  For Internet applications, the IANA
      maintains a registry
      "Message ID of the OIDs which correspond to well-known oldest message transfer protocols.  If the application protocol is
      not listed in the registry, an OID value of group's queue.
       Whenever possible this should be in the form
      {applTCPProtoID port} or {applUDProtoID port} are used for
      TCP-based and UDP-based protocols, respectively.  In either
      case 'port' corresponds of an
       RFC 822 [10] msg-id; X.400 may convert X.400 message
       identifiers to the primary port number being
      used this form by following the group.  applTCPProtoID and applUDPProtoID are
      defined rules laid
       out in [5]." RFC1327 [9]."





Expires Frebruary 1997                                         [Page 23]





Internet Draft            Mail Monitoring MIB                August 1996


    ::= {mtaGroupEntry 24}

mtaGroupName 32}

mtaGroupLoopsDetected OBJECT-TYPE
    SYNTAX DisplayString Counter32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "A descriptive name for the group. If this group connects to message loop is defined as a single remote situation where the MTA this should
       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 name number of that MTA. If
      this in turn is an Internet times the MTA has detected such a
       situation in conjunction with something associated with
       this should be group since group creation.  Note that the domain name.
      For an OSI
       mechanism MTAs use to detect loops (e.g. trace field
       counting, count of references to this MTA it should be the string encoded distinguished
      name in a trace
       field, examination of DNS or other directory information,
       etc.), the managed object using the format defined in RFC-1485.
      For X.400(1984) MTAs level at which do not have loops are detected (e.g. per
       message, per recipient, per directory entry, etc.), and
       the handling of a Distinguished Name, loop once it is detected (e.g. looping
       messages are held, looping messages are bounced or sent
       to the RFC-1327 syntax 'mta in globalid' should postmaster, messages that the MTA knows will loop
       won't be used." accepted, etc.) vary widely from one MTA to the
       next and cannot be inferred from this variable."
    ::= {mtaGroupEntry 25} 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}










Expires May 1996                                               [Page 17]





Internet Draft            Mail Monitoring MIB              November 1995

mtaGroupAssociationEntry OBJECT-TYPE
    SYNTAX MtaGroupAssociationEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
      "The entry holding information regarding the associations
       for each MTA group."
    INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex}
    ::= {mtaGroupAssociationTable 1}






Expires Frebruary 1997                                         [Page 24]





Internet Draft            Mail Monitoring MIB                August 1996


MtaGroupAssociationEntry ::= SEQUENCE {
    mtaGroupAssociationIndex
        INTEGER
}

mtaGroupAssociationIndex OBJECT-TYPE
    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}

-- Conformance information

mtaConformance OBJECT IDENTIFIER ::= {mta 4}

mtaGroups      OBJECT IDENTIFIER ::= {mtaConformance 1}
mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2}


-- Compliance statements

mtaCompliance MODULE-COMPLIANCE
    STATUS current
    DESCRIPTION
      "The compliance statement for SNMPv2 entities which
       implement the Mail Monitoring MIB for basic
       monitoring of MTAs."
    MODULE  -- this module
      MANDATORY-GROUPS {mtaGroup}
    ::= {mtaCompliances 1}







Expires May 1996                                               [Page 18]





Internet Draft            Mail Monitoring MIB              November 1995


mtaAssocCompliance MODULE-COMPLIANCE
    STATUS current
    DESCRIPTION
      "The compliance statement for SNMPv2 entities which
       implement the Mail Monitoring MIB for monitoring of
       MTAs and their associations."
    MODULE  -- this module
      MANDATORY-GROUPS {mtaGroup, mtaAssocGroup}
    ::= {mtaCompliances 2}






Expires Frebruary 1997                                         [Page 25]





Internet Draft            Mail Monitoring MIB                August 1996


-- Units of conformance

mtaGroup OBJECT-GROUP
    OBJECTS {
      mtaReceivedMessages, mtaStoredMessages,
      mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
      mtaTransmittedVolume, mtaReceivedRecipients,
      mtaStoredRecipients, mtaTransmittedRecipients,
      mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
      mtaLoopsDetected, mtaDescription, mtaURL,
      mtaGroupReceivedMessages, mtaGroupRejectedMessages,
      mtaGroupStoredMessages, mtaGroupTransmittedMessages,
      mtaGroupReceivedVolume, mtaGroupStoredVolume,
      mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
      mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
      mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
      mtaGroupOutboundAssociations,
      mtaGroupAccumulatedInboundAssociations,
      mtaGroupAccumulatedOutboundAssociations,
      mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
      mtaGroupLastOutboundAssociationAttempt,
      mtaGroupRejectedInboundAssociations,
      mtaGroupFailedOutboundAssociations,
      mtaGroupInboundRejectionReason,
      mtaGroupOutboundConnectFailureReason,
      mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName} mtaGroupName,
      mtaGroupSuccessfulConvertedMessages,
      mtaGroupFailedConvertedMessages, mtaGroupDescription,
      mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy,
      mtaGroupOldestMessageId, mtaGroupLoopsDetected}
    STATUS current
    DESCRIPTION
      "A collection of objects providing basic monitoring of MTAs."
    ::= {mtaGroups 1}













Expires May 1996                                               [Page 19]





Internet Draft            Mail Monitoring MIB              November 1995

mtaAssocGroup OBJECT-GROUP
    OBJECTS {
      mtaGroupAssociationIndex}
    STATUS current
    DESCRIPTION
      "A collection of objects providing monitoring of MTA
       associations."
    ::= {mtaGroups 2}

END





Expires May 1996 Frebruary 1997                                         [Page 20] 26]





Internet Draft            Mail Monitoring MIB              November 1995                August 1996


7.  Changes made since RFC1565 RFC 1566

The only changes made to this document since it was issued as RFC1566 RFC 1566
[8] are the following:

 (1)   A number of DESCRIPTION fields have been reworded, hopefully
       making them clearer.

 (2)   mtaDescription, mtaURL, mtaGroupDescription, mtaGroupURL fields
       have been added.  These fields are intended to identify and
       describe the MTA and the various MTA groups.

 (3)   The time since the last outbound association attempt is now
       distinct from the time since the last successfuol outbound
       association attempt.

 (4)   Conversion operation counters have been added.

 (5)   A mechanism to explicitly describe group hierarchies has been
       added.

 (6)   A field for the ID of the oldest message in a group's queue has
       been added.

 (7)   Per-MTA and per-group message loop counters have been added.

























Expires May 1996 Frebruary 1997                                         [Page 21] 27]





Internet Draft            Mail Monitoring MIB              November 1995                August 1996


8.  Acknowledgements

This document is a product of the Mail and Directory Management (MADMAN)
Working Group. It is based on an earlier MIB designed by S. Kille, T.
Lenggenhager, D. Partain, and W. Yeong. The Electronic Mail
Association's TSC committee was instrumental in  providing feedback on
and suggesting enhancements to RFC 1566 [8] that have led to the present
document.


9.  References

[1]  Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Structure
     of Management Information for version Version 2 of the Simple Network
     Management Protocol (SNMPv2)", RFC1442, SNMP Research, Inc., Hughes
     LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon
     University, April 1993. RFC 1902, January 1996.

[2]  McCloghrie, K., and Rose, M., Editors, "Management Information Base
     for Network Management of TCP/IP-based internets: MIB-II", STD 17,
     RFC 1213, Hughes LAN Systems, Performance Systems International, March 1991.

[3]  Galvin, J., McCloghrie, K., " Administrative Model for version 2 of
     the Simple Network Management Protocol (SNMPv2)", RFC 1445, Trusted
     Information Systems, Hughes LAN Systems, April
     1993.

[4]  Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol
     Operations for version Version 2 of the Simple Network Management Protocol
     (SNMPv2)", RFC1448, SNMP Research, Inc., Hughes LAN Systems, Dover
     Beach Consulting, Inc., Carnegie Mellon University, April 1993. RFC 1905, January 1996.

[5]  Freed, N., Kille, S., "The Network Services Monitoring MIB",
     Internet Draft, November, March 1996.

[6]  Kille, S., "A String Representation of Distinguished Names", RFC
     1779, March 1995.

[7]  Berners-Lee, T., Masinter, L., McCahill, M., iform Resource
     Locators (URL)", RFC 1738, December 1994.

[8]  Freed, N., Kille, S., "Mail Monitoring MIB", RFC 1566, January
     1994.

[9]  Kille, S., "Mapping between X.400(1988) / ISO 10021 and RFC 822",
     RFC 1327, May 1992.

[10] Crocker, D., "Standard for the Format of ARPA Internet Text
     Message", August 1982.





Expires Frebruary 1997                                         [Page 28]





Internet Draft            Mail Monitoring MIB                August 1996


[11] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893, Octel
     Network Services, January 1996.


10.  Security Considerations

Security issues are not discussed in this memo.














Expires May 1996                                               [Page 22]





Internet Draft            Mail Monitoring MIB              November 1995


11.  Authors' Addresses

     Ned Freed, Editor
     Innosoft International, Inc.
     1050 East Garvey Avenue South
     West Covina, CA 91790
     USA
      tel: +1 818 919 3600
      fax: +1 818 919 3614
      email: ned@innosoft.com

     Steve Kille, WG Chair
     ISODE Consortium
     The Dome, The Square
     Richmond TW9 1DT
     UK
       tel: +44 81 181 332 9091
       email: S.Kille@isode.com























Expires May 1996 Frebruary 1997                                         [Page 23] 29]



----