smilint output for ./MTA-MIB

Messages:

MTA-MIB

   1: -- extracted from rfc2789.txt
   2: -- at Fri Mar 24 07:07:17 2000

   3: 
   4:    MTA-MIB DEFINITIONS ::= BEGIN
   5: 
   6:    IMPORTS
   7:       OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2
   8:         FROM SNMPv2-SMI
   9:       TimeInterval
  10:         FROM SNMPv2-TC
  11:       MODULE-COMPLIANCE, OBJECT-GROUP
  12:         FROM SNMPv2-CONF
  13:       SnmpAdminString
  14:           FROM SNMP-FRAMEWORK-MIB
  15:       applIndex, URLString
  16:         FROM NETWORK-SERVICES-MIB;
  17: 
  18:    mta MODULE-IDENTITY
  19:       LAST-UPDATED "200003030000Z"
  20:       ORGANIZATION "IETF Mail and Directory Management Working Group"
  21:       CONTACT-INFO
  22:         "        Ned Freed
  23: 
  24:          Postal: Innosoft International, Inc.
  25:                  1050 Lakes Drive
  26:                  West Covina, CA 91790
  27:                  US
  28: 
  29:          Tel: +1 626 919 3600
  30:          Fax: +1 626 919 3614
  31: 
  32:          E-Mail: ned.freed@innosoft.com"
  33:       DESCRIPTION
  34:         "The MIB module describing Message Transfer Agents (MTAs)"
  35:       REVISION "200003030000Z"
  36:       DESCRIPTION
  37:         "This revision, published in RFC 2789, changes a number of
  38:          DisplayStrings to SnmpAdminStrings. Note that this change
  39:          is not strictly supported by SMIv2.  However, the alternative
  40:          of deprecating the old objects and defining new objects
  41:          would have a more adverse impact on backward compatibility
  42:          and interoperability, given the particular semantics of
  43:          these objects.  The defining reference for distinguished
  44:          names has also been updated from RFC 1779 to RFC 2253."
  45:       REVISION "199905120000Z"
  46:       DESCRIPTION
  47:         "This revision fixes a number of technical problems found in
  48:          previous versions: The conformance groups for different
  49:          versions of this MIB have been corrected, the recommendation
  50:          that an empty string be returned if the last operation was
  51:          successful has been removed from
  52:          mtaGroupInboundRejectionReason and
  53:          mtaGroupOutboundConnectFailureReason as it conflicts
  54:          with the stated purpose of these variables, and the
  55:          required mtaStatusCode entry has been added to
  56:          MtaGroupErrorEntry.  It should be noted that this last
  57:          change in no way affects the bits on the wire."
  58:       REVISION "199708170000Z"
  59:       DESCRIPTION
  60:         "This revision, published in RFC 2249, adds the
  61:          mtaGroupDescription and mtaGroupURL fields, conversion
  62:          operation counters, a group hierarchy description mechanism,
  63:          counters for specific errors, oldest message IDs, per-MTA
  64:          and per-group loop counters, and a new table for tracking
  65:          any errors an MTA encounters."
  66:       REVISION "199311280000Z"
  67:       DESCRIPTION
  68:         "The original version of this MIB was published in RFC 1566"
  69:       ::= {mib-2 28}
  70: 
  71:    mtaTable OBJECT-TYPE
  72:       SYNTAX SEQUENCE OF MtaEntry
  73:       MAX-ACCESS not-accessible
  74:       STATUS current
  75:       DESCRIPTION
  76:         "The table holding information specific to an MTA."
  77:       ::= {mta 1}
  78: 
  79:    mtaEntry OBJECT-TYPE
  80:       SYNTAX MtaEntry
  81:       MAX-ACCESS not-accessible
  82:       STATUS current
  83:       DESCRIPTION
  84:         "The entry associated with each MTA."
  85:       INDEX {applIndex}
  86:       ::= {mtaTable 1}
  87: 
  88:    MtaEntry ::= SEQUENCE {
  89:       mtaReceivedMessages
  90:         Counter32,
  91:       mtaStoredMessages
  92:         Gauge32,
  93:       mtaTransmittedMessages
  94:         Counter32,
  95:       mtaReceivedVolume
  96:         Counter32,
  97:       mtaStoredVolume
  98:         Gauge32,
  99:       mtaTransmittedVolume
 100:         Counter32,
 101:       mtaReceivedRecipients
 102:         Counter32,
 103:       mtaStoredRecipients
 104:         Gauge32,
 105:       mtaTransmittedRecipients
 106:         Counter32,
 107:       mtaSuccessfulConvertedMessages
 108:         Counter32,
 109:       mtaFailedConvertedMessages
 110:         Counter32,
 111:       mtaLoopsDetected
 112:         Counter32
 113:    }
 114: 
 115:    mtaReceivedMessages OBJECT-TYPE
 116:       SYNTAX Counter32
 117:       MAX-ACCESS read-only
 118:       STATUS current
 119:       DESCRIPTION
 120:         "The number of messages received since MTA initialization.
 121:          This includes messages transmitted to this MTA from other
 122:          MTAs as well as messages that have been submitted to the
 123:          MTA directly by end-users or applications."
 124:       ::= {mtaEntry 1}
 125: 
 126:    mtaStoredMessages OBJECT-TYPE
 127:       SYNTAX Gauge32
 128:       MAX-ACCESS read-only
 129:       STATUS current
 130:       DESCRIPTION
 131:         "The total number of messages currently stored in the MTA.
 132:          This includes messages that are awaiting transmission to
 133:          some other MTA or are waiting for delivery to an end-user
 134:          or application."
 135:       ::= {mtaEntry 2}
 136: 
 137:    mtaTransmittedMessages OBJECT-TYPE
 138:       SYNTAX Counter32
 139:       MAX-ACCESS read-only
 140:       STATUS current
 141:       DESCRIPTION
 142:         "The number of messages transmitted since MTA initialization.
 143:          This includes messages that were transmitted to some other
 144:          MTA or are waiting for delivery to an end-user or
 145:          application."
 146:       ::= {mtaEntry 3}
 147: 
 148:    mtaReceivedVolume OBJECT-TYPE
 149:       SYNTAX Counter32
 150:       UNITS "K-octets"
 151:       MAX-ACCESS read-only
 152:       STATUS current
 153:       DESCRIPTION
 154:         "The total volume of messages received since MTA
 155:          initialization, measured in kilo-octets.  This volume should
 156:          include all transferred data that is logically above the mail
 157:          transport protocol level.  For example, an SMTP-based MTA
 158:          should use the number of kilo-octets in the message header
 159:          and body, while an X.400-based MTA should use the number of
 160:          kilo-octets of P2 data.  This includes messages transmitted
 161:          to this MTA from other MTAs as well as messages that have
 162:          been submitted to the MTA directly by end-users or
 163:          applications."
 164:       ::= {mtaEntry 4}
 165: 
 166:    mtaStoredVolume OBJECT-TYPE
 167:       SYNTAX Gauge32
 168:       UNITS "K-octets"
 169:       MAX-ACCESS read-only
 170:       STATUS current
 171:       DESCRIPTION
 172:         "The total volume of messages currently stored in the MTA,
 173:          measured in kilo-octets.  This volume should include all
 174:          stored data that is logically above the mail transport
 175:          protocol level.  For example, an SMTP-based MTA should
 176:          use the number of kilo-octets in the message header and
 177:          body, while an X.400-based MTA would use the number of
 178:          kilo-octets of P2 data.  This includes messages that are
 179:          awaiting transmission to some other MTA or are waiting
 180:          for delivery to an end-user or application."
 181:       ::= {mtaEntry 5}
 182: 
 183:    mtaTransmittedVolume OBJECT-TYPE
 184:       SYNTAX Counter32
 185:       UNITS "K-octets"
 186:       MAX-ACCESS read-only
 187:       STATUS current
 188:       DESCRIPTION
 189:         "The total volume of messages transmitted since MTA
 190:          initialization, measured in kilo-octets.  This volume should
 191:          include all transferred data that is logically above the mail
 192:          transport protocol level.  For example, an SMTP-based MTA
 193:          should use the number of kilo-octets in the message header
 194:          and body, while an X.400-based MTA should use the number of
 195:          kilo-octets of P2 data.  This includes messages that were
 196:          transmitted to some other MTA or are waiting for delivery
 197:          to an end-user or application."
 198:       ::= {mtaEntry 6}
 199: 
 200:    mtaReceivedRecipients OBJECT-TYPE
 201:       SYNTAX Counter32
 202:       MAX-ACCESS read-only
 203:       STATUS current
 204:       DESCRIPTION
 205:         "The total number of recipients specified in all messages
 206:          received since MTA initialization.  Recipients this MTA
 207:          has no responsibility for, i.e. inactive envelope
 208:          recipients or ones referred to in message headers,
 209:          should not be counted even if information about such
 210:          recipients is available.  This includes messages
 211:          transmitted to this MTA from other MTAs as well as
 212:          messages that have been submitted to the MTA directly
 213:          by end-users or applications."
 214:       ::= {mtaEntry 7}
 215: 
 216:    mtaStoredRecipients OBJECT-TYPE
 217:       SYNTAX Gauge32
 218:       MAX-ACCESS read-only
 219:       STATUS current
 220:       DESCRIPTION
 221:         "The total number of recipients specified in all messages
 222:          currently stored in the MTA.  Recipients this MTA has no
 223:          responsibility for, i.e. inactive envelope recipients or
 224:          ones referred to in message headers, should not be
 225:          counted.  This includes messages that are awaiting
 226:          transmission to some other MTA or are waiting for
 227:          delivery to an end-user or application."
 228:       ::= {mtaEntry 8}
 229: 
 230:    mtaTransmittedRecipients OBJECT-TYPE
 231:       SYNTAX Counter32
 232:       MAX-ACCESS read-only
 233:       STATUS current
 234:       DESCRIPTION
 235:         "The total number of recipients specified in all messages
 236:          transmitted since MTA initialization.  Recipients this
 237:          MTA had no responsibility for, i.e. inactive envelope
 238:          recipients or ones referred to in message headers,
 239:          should not be counted.  This includes messages that were
 240:          transmitted to some other MTA or are waiting for
 241:          delivery to an end-user or application."
 242:       ::= {mtaEntry 9}
 243: 
 244:    mtaSuccessfulConvertedMessages OBJECT-TYPE
 245:       SYNTAX Counter32
 246:       MAX-ACCESS read-only
 247:       STATUS current
 248:       DESCRIPTION
 249:         "The number of messages that have been successfully
 250:          converted from one form to another since MTA
 251:          initialization."
 252:       ::= {mtaEntry 10}
 253: 
 254:    mtaFailedConvertedMessages OBJECT-TYPE
 255:       SYNTAX Counter32
 256:       MAX-ACCESS read-only
 257:       STATUS current
 258:       DESCRIPTION
 259:         "The number of messages for which an unsuccessful
 260:          attempt was made to convert them from one form to
 261:          another since MTA initialization."
 262:       ::= {mtaEntry 11}
 263: 
 264:    mtaLoopsDetected OBJECT-TYPE
 265:       SYNTAX Counter32
 266:       MAX-ACCESS read-only
 267:       STATUS current
 268:       DESCRIPTION
 269:         "A message loop is defined as a situation where the MTA
 270:          decides that a given message will never be delivered to
 271:          one or more recipients and instead will continue to
 272:          loop endlessly through one or more MTAs.  This variable
 273:          counts the number of times the MTA has detected such a
 274:          situation since MTA initialization. Note that the
 275:          mechanism MTAs use to detect loops (e.g., trace field
 276:          counting, count of references to this MTA in a trace
 277:          field, examination of DNS or other directory information,
 278:          etc.), the level at which loops are detected (e.g., per
 279:          message, per recipient, per directory entry, etc.), and
 280:          the handling of a loop once it is detected (e.g., looping
 281:          messages are held, looping messages are bounced or sent
 282:          to the postmaster, messages that the MTA knows will loop
 283:          won't be accepted, etc.) vary widely from one MTA to the
 284:          next and cannot be inferred from this variable."
 285:       ::= {mtaEntry 12}
 286: 
 287:    -- MTAs typically group inbound reception, queue storage, and
 288:    -- outbound transmission in some way, rather than accounting for
 289:    -- such operations only across the MTA as a whole. In the most
 290:    -- extreme case separate information will be maintained for each
 291:    -- different entity that receives messages and for each entity
 292:    -- the MTA stores messages for and delivers messages to.  Other
 293:    -- MTAs may elect to treat all reception equally, all queue
 294:    -- storage equally, all deliveries equally, or some combination
 295:    -- of this. Overlapped groupings are also possible, where an MTA
 296:    -- decomposes its traffic in different ways for different
 297:    -- purposes.
 298: 
 299:    -- In any case, a grouping abstraction is an extremely useful for
 300:    -- breaking down the activities of an MTA. For purposes of
 301:    -- labelling this will be called a "group" in this MIB.
 302: 
 303:    -- Each group contains all the variables needed to monitor all
 304:    -- aspects of an MTA's operation.  However, the fact that all
 305:    -- groups contain all possible variables does not imply that all
 306:    -- groups must use all possible variables. For example, a single
 307:    -- group might be used to monitor only one kind of event (inbound
 308:    -- processing, outbound processing, or storage). In this sort of
 309:    -- configuration any counters that are unused as a result of a
 310:    -- given MTA's use of the group construct must be inaccessible;
 311:    -- e.g., returning either a noSuchName error (for an SNMPv1 get),
 312:    -- or a noSuchInstance exception (for an SNMPv2 get).
 313: 
 314:    -- Groups can be created at any time after MTA initialization. Once
 315:    -- a group is created it should not be deleted or its mtaGroupIndex
 316:    -- changed unless the MTA is reinitialized.
 317: 
 318:    -- Groups are not necessarily mutually exclusive. A given event may
 319:    -- be recorded by more than one group, a message may be seen as
 320:    -- stored by more than one group, and so on.  Groups should be all
 321:    -- inclusive, however: if groups are implemented all aspects of an
 322:    -- MTA's operation should be registered in at least one group.
 323:    -- This freedom lets implementors use different sets of groups to
 324:    -- provide different "views" of an MTA.
 325: 
 326:    -- The possibility of overlap between groups means that summing
 327:    -- variables across groups may not produce values equal to those in
 328:    -- the mtaTable. mtaTable should always provide accurate information
 329:    -- about the MTA as a whole.
 330: 
 331:    -- The term "channel" is often used in MTA implementations; channels
 332:    -- are usually, but not always, equivalent to a group. However,
 333:    -- this MIB does not use the term "channel" because there is no
 334:    -- requirement that an MTA supporting this MIB has to map its
 335:    -- "channel" abstraction one-to-one onto the MIB's group abstraction.
 336: 
 337:    -- An MTA may create a group or group of groups at any time. Once
 338:    -- created, however, an MTA cannot delete an entry for a group from
 339:    -- the group table.  Deletion is only allowed when the MTA is
 340:    -- reinitialized, and is not required even then.  This restriction
 341:    -- is imposed so that monitoring agents can rely on group
 342:    -- assignments being consistent across multiple query operations.
 343: 
 344:    -- Groups may be laid out so as to form a hierarchical arrangement,
 345:    -- with some groups acting as subgroups for other groups.
 346:    -- Alternately, disjoint groups of groups may be used to provide
 347:    -- different sorts of "snapshots" of MTA operation.  The
 348:    -- mtaGroupHierarchy variable provides an indication of how each
 349:    -- group fits into the overall arrangement being used.
 350: 
 351:    -- Note that SNMP also defines and uses term "group". MTA groups are
 352:    -- NOT the same as SNMP groups.
 353: 
 354:    mtaGroupTable OBJECT-TYPE
 355:        SYNTAX SEQUENCE OF MtaGroupEntry
 356:        MAX-ACCESS not-accessible
 357:        STATUS current
 358:        DESCRIPTION
 359:          "The table holding information specific to each MTA group."
 360:        ::= {mta 2}
 361: 
 362:    mtaGroupEntry OBJECT-TYPE
 363:        SYNTAX MtaGroupEntry
 364:        MAX-ACCESS not-accessible
 365:        STATUS current
 366:        DESCRIPTION
 367:          "The entry associated with each MTA group."
 368:        INDEX {applIndex, mtaGroupIndex}
 369:        ::= {mtaGroupTable 1}
 370: 
 371:    MtaGroupEntry ::= SEQUENCE {

 372:       mtaGroupIndex
 373:           INTEGER,
 374:       mtaGroupReceivedMessages
 375:           Counter32,
 376:       mtaGroupRejectedMessages
 377:           Counter32,
 378:       mtaGroupStoredMessages
 379:           Gauge32,
 380:       mtaGroupTransmittedMessages
 381:           Counter32,
 382:       mtaGroupReceivedVolume
 383:           Counter32,
 384:       mtaGroupStoredVolume
 385:           Gauge32,
 386:       mtaGroupTransmittedVolume
 387:           Counter32,
 388:       mtaGroupReceivedRecipients
 389:           Counter32,
 390:       mtaGroupStoredRecipients
 391:           Gauge32,
 392:       mtaGroupTransmittedRecipients
 393:           Counter32,
 394:       mtaGroupOldestMessageStored
 395:           TimeInterval,
 396:       mtaGroupInboundAssociations
 397:           Gauge32,
 398:       mtaGroupOutboundAssociations
 399:           Gauge32,
 400:       mtaGroupAccumulatedInboundAssociations
 401:           Counter32,
 402:       mtaGroupAccumulatedOutboundAssociations
 403:           Counter32,
 404:       mtaGroupLastInboundActivity
 405:           TimeInterval,
 406:       mtaGroupLastOutboundActivity
 407:           TimeInterval,
 408:       mtaGroupLastOutboundAssociationAttempt
 409:           TimeInterval,
 410:       mtaGroupRejectedInboundAssociations
 411:           Counter32,
 412:       mtaGroupFailedOutboundAssociations
 413:           Counter32,
 414:       mtaGroupInboundRejectionReason
 415:           SnmpAdminString,
 416:       mtaGroupOutboundConnectFailureReason
 417:           SnmpAdminString,
 418:       mtaGroupScheduledRetry
 419:           TimeInterval,
 420:       mtaGroupMailProtocol
 421:           OBJECT IDENTIFIER,
 422:       mtaGroupName
 423:           SnmpAdminString,
 424:       mtaGroupSuccessfulConvertedMessages
 425:           Counter32,
 426:       mtaGroupFailedConvertedMessages
 427:           Counter32,
 428:       mtaGroupDescription
 429:           SnmpAdminString,
 430:       mtaGroupURL
 431:           URLString,
 432:       mtaGroupCreationTime
 433:           TimeInterval,
 434:       mtaGroupHierarchy
 435:           INTEGER,
 436:       mtaGroupOldestMessageId
 437:           SnmpAdminString,
 438:       mtaGroupLoopsDetected
 439:           Counter32
 440:    }
 441: 
 442:    mtaGroupIndex OBJECT-TYPE
 443:       SYNTAX INTEGER (1..2147483647)

 444:       MAX-ACCESS not-accessible
 445:       STATUS current
 446:       DESCRIPTION
 447:         "The index associated with a group for a given MTA."
 448:       ::= {mtaGroupEntry 1}
 449: 
 450:    mtaGroupReceivedMessages OBJECT-TYPE
 451:       SYNTAX Counter32
 452:       MAX-ACCESS read-only
 453:       STATUS current
 454:       DESCRIPTION
 455:         "The number of messages received to this group since
 456:          group creation."
 457:       ::= {mtaGroupEntry 2}
 458: 
 459:    mtaGroupRejectedMessages OBJECT-TYPE
 460:       SYNTAX Counter32
 461:       MAX-ACCESS read-only
 462:       STATUS current
 463:       DESCRIPTION
 464:         "The number of messages rejected by this group since
 465:          group creation."
 466:       ::= {mtaGroupEntry 3}
 467: 
 468:    mtaGroupStoredMessages OBJECT-TYPE
 469:       SYNTAX Gauge32
 470:       MAX-ACCESS read-only
 471:       STATUS current
 472:       DESCRIPTION
 473:         "The total number of messages currently stored in this
 474:          group's queue."
 475:       ::= {mtaGroupEntry 4}
 476: 
 477:    mtaGroupTransmittedMessages OBJECT-TYPE
 478:       SYNTAX Counter32
 479:       MAX-ACCESS read-only
 480:       STATUS current
 481:       DESCRIPTION
 482:         "The number of messages transmitted by this group since
 483:          group creation."
 484:       ::= {mtaGroupEntry 5}
 485: 
 486:    mtaGroupReceivedVolume OBJECT-TYPE
 487:       SYNTAX Counter32
 488:       UNITS "K-octets"
 489:       MAX-ACCESS read-only
 490:       STATUS current
 491:       DESCRIPTION
 492:         "The total volume of messages received to this group since
 493:          group creation, measured in kilo-octets.  This volume
 494:          should include all transferred data that is logically above
 495:          the mail transport protocol level.  For example, an
 496:          SMTP-based MTA should use the number of kilo-octets in the
 497:          message header and body, while an X.400-based MTA should use
 498:          the number of kilo-octets of P2 data."
 499:       ::= {mtaGroupEntry 6}
 500: 
 501:    mtaGroupStoredVolume OBJECT-TYPE
 502:       SYNTAX Gauge32
 503:       UNITS "K-octets"
 504:       MAX-ACCESS read-only
 505:       STATUS current
 506:       DESCRIPTION
 507:         "The total volume of messages currently stored in this
 508:          group's queue, measured in kilo-octets.  This volume should
 509:          include all stored data that is logically above the mail
 510:          transport protocol level.  For example, an SMTP-based
 511:          MTA should use the number of kilo-octets in the message
 512:          header and body, while an X.400-based MTA would use the
 513:          number of kilo-octets of P2 data."
 514:       ::= {mtaGroupEntry 7}
 515: 
 516:    mtaGroupTransmittedVolume OBJECT-TYPE
 517:       SYNTAX Counter32
 518:       UNITS "K-octets"
 519:       MAX-ACCESS read-only
 520:       STATUS current
 521:       DESCRIPTION
 522:         "The total volume of messages transmitted by this group
 523:          since group creation, measured in kilo-octets.  This
 524:          volume should include all transferred data that is logically
 525:          above the mail transport protocol level.  For example, an
 526:          SMTP-based MTA should use the number of kilo-octets in the
 527:          message header and body, while an X.400-based MTA should use
 528:          the number of kilo-octets of P2 data."
 529:       ::= {mtaGroupEntry 8}
 530: 
 531:    mtaGroupReceivedRecipients OBJECT-TYPE
 532:       SYNTAX Counter32
 533:       MAX-ACCESS read-only
 534:       STATUS current
 535:       DESCRIPTION
 536:         "The total number of recipients specified in all messages
 537:          received to this group since group creation.
 538:          Recipients this MTA has no responsibility for should not
 539:          be counted."
 540:       ::= {mtaGroupEntry 9}
 541: 
 542:    mtaGroupStoredRecipients OBJECT-TYPE
 543:       SYNTAX Gauge32
 544:       MAX-ACCESS read-only
 545:       STATUS current
 546:       DESCRIPTION
 547:         "The total number of recipients specified in all messages
 548:          currently stored in this group's queue.  Recipients this
 549:          MTA has no responsibility for should not be counted."
 550:       ::= {mtaGroupEntry 10}
 551: 
 552:    mtaGroupTransmittedRecipients OBJECT-TYPE
 553:       SYNTAX Counter32
 554:       MAX-ACCESS read-only
 555:       STATUS current
 556:       DESCRIPTION
 557:         "The total number of recipients specified in all messages
 558:          transmitted by this group since group creation.
 559:          Recipients this MTA had no responsibility for should not
 560:          be counted."
 561:       ::= {mtaGroupEntry 11}
 562: 
 563:    mtaGroupOldestMessageStored OBJECT-TYPE
 564:       SYNTAX TimeInterval
 565:       MAX-ACCESS read-only
 566:       STATUS current
 567:       DESCRIPTION
 568:         "Time since the oldest message in this group's queue was
 569:          placed in the queue."
 570:       ::= {mtaGroupEntry 12}
 571: 
 572:    mtaGroupInboundAssociations OBJECT-TYPE
 573:       SYNTAX Gauge32
 574:       MAX-ACCESS read-only
 575:       STATUS current
 576:       DESCRIPTION
 577:         "The number of current associations to the group, where the
 578:          group is the responder."
 579:       ::= {mtaGroupEntry 13}
 580: 
 581:    mtaGroupOutboundAssociations OBJECT-TYPE
 582:       SYNTAX Gauge32
 583:       MAX-ACCESS read-only
 584:       STATUS current
 585:       DESCRIPTION
 586:         "The number of current associations to the group, where the
 587:         group is the initiator."
 588:       ::= {mtaGroupEntry 14}
 589: 
 590:    mtaGroupAccumulatedInboundAssociations OBJECT-TYPE
 591:       SYNTAX Counter32
 592:       MAX-ACCESS read-only
 593:       STATUS current
 594:       DESCRIPTION
 595:         "The total number of associations to the group since
 596:         group creation, where the MTA was the responder."
 597:       ::= {mtaGroupEntry 15}
 598: 
 599:    mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE
 600:       SYNTAX Counter32
 601:       MAX-ACCESS read-only
 602:       STATUS current
 603:       DESCRIPTION
 604:         "The total number of associations from the group since
 605:          group creation, where the MTA was the initiator."
 606:       ::= {mtaGroupEntry 16}
 607: 
 608:    mtaGroupLastInboundActivity OBJECT-TYPE
 609:       SYNTAX TimeInterval
 610:       MAX-ACCESS read-only
 611:       STATUS current
 612:       DESCRIPTION
 613:         "Time since the last time that this group had an active
 614:         inbound association for purposes of message reception."
 615:       ::= {mtaGroupEntry 17}
 616: 
 617:    mtaGroupLastOutboundActivity OBJECT-TYPE
 618:       SYNTAX TimeInterval
 619:       MAX-ACCESS read-only
 620:       STATUS current
 621:       DESCRIPTION
 622:         "Time since the last time that this group had a
 623:          successful outbound association for purposes of
 624:          message delivery."
 625:       ::= {mtaGroupEntry 18}
 626: 
 627:    mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE
 628:       SYNTAX TimeInterval
 629:       MAX-ACCESS read-only
 630:       STATUS current
 631:       DESCRIPTION
 632:         "Time since the last time that this group attempted
 633:          to make an outbound association for purposes of
 634:          message delivery."
 635:       ::= {mtaGroupEntry 34}
 636: 
 637:    mtaGroupRejectedInboundAssociations OBJECT-TYPE
 638:       SYNTAX Counter32
 639:       MAX-ACCESS read-only
 640:       STATUS current
 641:       DESCRIPTION
 642:         "The total number of inbound associations the group has
 643:         rejected, since group creation.  Rejected associations
 644:         are not counted in the accumulated association totals."
 645:       ::= {mtaGroupEntry 19}
 646: 
 647:    mtaGroupFailedOutboundAssociations OBJECT-TYPE
 648:       SYNTAX Counter32
 649:       MAX-ACCESS read-only
 650:       STATUS current
 651:       DESCRIPTION
 652:         "The total number associations where the group was the
 653:         initiator and association establishment has failed,
 654:         since group creation.  Failed associations are
 655:         not counted in the accumulated association totals."
 656:       ::= {mtaGroupEntry 20}
 657: 
 658:    mtaGroupInboundRejectionReason OBJECT-TYPE
 659:       SYNTAX SnmpAdminString
 660:       MAX-ACCESS read-only
 661:       STATUS current
 662:       DESCRIPTION
 663:         "The failure reason, if any, for the last association this
 664:         group refused to respond to. If no association attempt
 665:         has been made since the MTA was initialized the value
 666:         should be 'never'."
 667:       ::= {mtaGroupEntry 21}
 668: 
 669:    mtaGroupOutboundConnectFailureReason OBJECT-TYPE
 670:       SYNTAX SnmpAdminString
 671:       MAX-ACCESS read-only
 672:       STATUS current
 673:       DESCRIPTION
 674:         "The failure reason, if any, for the last association attempt
 675:         this group initiated. If no association attempt has been
 676:         made since the MTA was initialized the value should be
 677:         'never'."
 678:       ::= {mtaGroupEntry 22}
 679: 
 680:    mtaGroupScheduledRetry OBJECT-TYPE
 681:       SYNTAX TimeInterval
 682:       MAX-ACCESS read-only
 683:       STATUS current
 684:       DESCRIPTION
 685:         "The amount of time until this group is next scheduled to
 686:          attempt to make an association."
 687:       ::= {mtaGroupEntry 23}
 688: 
 689:    mtaGroupMailProtocol OBJECT-TYPE
 690:       SYNTAX OBJECT IDENTIFIER
 691:       MAX-ACCESS read-only
 692:       STATUS current
 693:       DESCRIPTION
 694:         "An identification of the protocol being used by this group.
 695:          For an group employing OSI protocols, this will be the
 696:          Application Context.    For Internet applications, OID
 697:          values of the form {applTCPProtoID port} or {applUDPProtoID
 698:          port} are used for TCP-based and UDP-based protocols,
 699:          respectively. In either case 'port' corresponds to the
 700:          primary port number being used by the protocol. The
 701:          usual IANA procedures may be used to register ports for
 702:          new protocols. applTCPProtoID and applUDPProtoID are
 703:          defined in the NETWORK-SERVICES-MIB, RFC 2788."
 704:       ::= {mtaGroupEntry 24}
 705: 
 706:    mtaGroupName OBJECT-TYPE
 707:       SYNTAX SnmpAdminString
 708:       MAX-ACCESS read-only
 709:       STATUS current
 710:       DESCRIPTION
 711:         "A descriptive name for the group. If this group connects to
 712:          a single remote MTA this should be the name of that MTA. If
 713:          this in turn is an Internet MTA this should be the domain
 714:          name.  For an OSI MTA it should be the string encoded
 715:          distinguished name of the managed object using the format
 716:          defined in RFC 2253.  For X.400(1984) MTAs which do not
 717:          have a Distinguished Name, the RFC 2156 syntax
 718:          'mta in globalid' used in X400-Received: fields can be
 719:          used."
 720:       ::= {mtaGroupEntry 25}
 721: 
 722:    mtaGroupSuccessfulConvertedMessages OBJECT-TYPE
 723:       SYNTAX Counter32
 724:       MAX-ACCESS read-only
 725:       STATUS current
 726:       DESCRIPTION
 727:         "The number of messages that have been successfully
 728:          converted from one form to another in this group
 729:          since group creation."
 730:       ::= {mtaGroupEntry 26}
 731: 
 732:    mtaGroupFailedConvertedMessages OBJECT-TYPE
 733:       SYNTAX Counter32
 734:       MAX-ACCESS read-only
 735:       STATUS current
 736:       DESCRIPTION
 737:         "The number of messages for which an unsuccessful
 738:          attempt was made to convert them from one form to
 739:          another in this group since group creation."
 740:       ::= {mtaGroupEntry 27}
 741: 
 742:    mtaGroupDescription OBJECT-TYPE
 743:       SYNTAX SnmpAdminString
 744:       MAX-ACCESS read-only
 745:       STATUS current
 746:       DESCRIPTION
 747:         "A description of the group's purpose.  This information is
 748:          intended to identify the group in a status display."
 749:       ::= {mtaGroupEntry 28}
 750: 
 751:    mtaGroupURL OBJECT-TYPE
 752:       SYNTAX URLString
 753:       MAX-ACCESS read-only
 754:       STATUS current
 755:       DESCRIPTION
 756:         "A URL pointing to a description of the group.  This
 757:          information is intended to identify and briefly describe
 758:          the group in a status display."
 759:       ::= {mtaGroupEntry 29}
 760: 
 761:    mtaGroupCreationTime OBJECT-TYPE
 762:       SYNTAX TimeInterval
 763:       MAX-ACCESS read-only
 764:       STATUS current
 765:       DESCRIPTION
 766:         "Time since this group was first created."
 767:       ::= {mtaGroupEntry 30}
 768: 
 769:    mtaGroupHierarchy OBJECT-TYPE
 770:       SYNTAX INTEGER (-2147483648..2147483647)

 771:       MAX-ACCESS read-only
 772:       STATUS current
 773:       DESCRIPTION
 774:         "Describes how this group fits into the hierarchy. A
 775:          positive value is interpreted as an mtaGroupIndex
 776:          value for some other group whose variables include
 777:          those of this group (and usually others). A negative
 778:          value is interpreted as a group collection code: Groups
 779:          with common negative hierarchy values comprise one
 780:          particular breakdown of MTA activity as a whole. A
 781:          zero value means that this MIB implementation doesn't
 782:          implement hierarchy indicators and thus the overall
 783:          group hierarchy cannot be determined."
 784:       ::= {mtaGroupEntry 31}
 785: 
 786:    mtaGroupOldestMessageId OBJECT-TYPE
 787:       SYNTAX SnmpAdminString
 788:       MAX-ACCESS read-only
 789:       STATUS current
 790:       DESCRIPTION
 791:         "Message ID of the oldest message in the group's queue.
 792:          Whenever possible this should be in the form of an
 793:          RFC 822 msg-id; X.400 may convert X.400 message
 794:          identifiers to this form by following the rules laid
 795:          out in RFC2156."
 796:       ::= {mtaGroupEntry 32}
 797: 
 798:    mtaGroupLoopsDetected OBJECT-TYPE
 799:       SYNTAX Counter32
 800:       MAX-ACCESS read-only
 801:       STATUS current
 802:       DESCRIPTION
 803:         "A message loop is defined as a situation where the MTA
 804:          decides that a given message will never be delivered to
 805:          one or more recipients and instead will continue to
 806:          loop endlessly through one or more MTAs.  This variable
 807:          counts the number of times the MTA has detected such a
 808:          situation in conjunction with something associated with
 809:          this group since group creation.  Note that the
 810:          mechanism MTAs use to detect loops (e.g., trace field
 811:          counting, count of references to this MTA in a trace
 812:          field, examination of DNS or other directory information,
 813:          etc.), the level at which loops are detected (e.g., per
 814:          message, per recipient, per directory entry, etc.), and
 815:          the handling of a loop once it is detected (e.g., looping
 816:          messages are held, looping messages are bounced or sent
 817:          to the postmaster, messages that the MTA knows will loop
 818:          won't be accepted, etc.) vary widely from one MTA to the
 819:          next and cannot be inferred from this variable."
 820:       ::= {mtaGroupEntry 33}
 821: 
 822:    -- The mtaGroupAssociationTable provides a means of correlating
 823:    -- entries in the network services association table with the
 824:    -- MTA group responsible for the association.
 825: 
 826:    mtaGroupAssociationTable OBJECT-TYPE
 827:       SYNTAX SEQUENCE OF MtaGroupAssociationEntry
 828:       MAX-ACCESS not-accessible
 829:       STATUS current
 830:       DESCRIPTION
 831:         "The table holding information regarding the associations
 832:          for each MTA group."
 833:       ::= {mta 3}
 834: 
 835:    mtaGroupAssociationEntry OBJECT-TYPE
 836:       SYNTAX MtaGroupAssociationEntry
 837:       MAX-ACCESS not-accessible
 838:       STATUS current
 839:       DESCRIPTION
 840:         "The entry holding information regarding the associations
 841:          for each MTA group."
 842:       INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex}
 843:       ::= {mtaGroupAssociationTable 1}
 844: 
 845:    MtaGroupAssociationEntry ::= SEQUENCE {
 846:       mtaGroupAssociationIndex
 847:           INTEGER
 848:    }
 849: 
 850:    mtaGroupAssociationIndex OBJECT-TYPE
 851:       SYNTAX INTEGER (1..2147483647)

 852:       MAX-ACCESS read-only
 853:       STATUS current
 854:       DESCRIPTION
 855:         "Reference into association table to allow correlation of
 856:          this group's active associations with the association table."
 857:       ::= {mtaGroupAssociationEntry 1}
 858: 
 859:    -- The mtaGroupErrorTable gives each group a way of tallying
 860:    -- the specific errors it has encountered.  The mechanism
 861:    -- defined here uses RFC 1893 status codes to identify
 862:    -- various specific errors.  There are also classes for generic
 863:    -- errors of various sorts, and the entire mechanism is also
 864:    -- extensible, in that new error codes can be defined at any
 865:    -- time.
 866: 
 867:    mtaGroupErrorTable OBJECT-TYPE
 868:       SYNTAX SEQUENCE OF MtaGroupErrorEntry
 869:       MAX-ACCESS not-accessible
 870:       STATUS current
 871:       DESCRIPTION
 872:         "The table holding information regarding accumulated errors
 873:          for each MTA group."
 874:       ::= {mta 5}
 875: 
 876:    mtaGroupErrorEntry OBJECT-TYPE
 877:       SYNTAX MtaGroupErrorEntry
 878:       MAX-ACCESS not-accessible
 879:       STATUS current
 880:       DESCRIPTION
 881:         "The entry holding information regarding accumulated
 882:          errors for each MTA group."
 883:       INDEX {applIndex, mtaGroupIndex, mtaStatusCode}
 884:       ::= {mtaGroupErrorTable 1}
 885: 
 886:    MtaGroupErrorEntry ::= SEQUENCE {

 887:       mtaStatusCode
 888:           INTEGER (4000000..5999999),

 889:       mtaGroupInboundErrorCount
 890:           Counter32,
 891:       mtaGroupInternalErrorCount
 892:           Counter32,
 893:       mtaGroupOutboundErrorCount
 894:           Counter32
 895:    }
 896: 
 897:    mtaGroupInboundErrorCount OBJECT-TYPE
 898:       SYNTAX Counter32
 899:       MAX-ACCESS read-only
 900:       STATUS current
 901:       DESCRIPTION
 902:         "Count of the number of errors of a given type that have
 903:          been accumulated in association with a particular group
 904:          while processing incoming messages. In the case of SMTP
 905:          these will typically be errors reporting by an SMTP
 906:          server to the remote client; in the case of X.400
 907:          these will typically be errors encountered while
 908:          processing an incoming message."
 909:       ::= {mtaGroupErrorEntry 1}
 910: 
 911:    mtaGroupInternalErrorCount OBJECT-TYPE
 912:       SYNTAX Counter32
 913:       MAX-ACCESS read-only
 914:       STATUS current
 915:       DESCRIPTION
 916:         "Count of the number of errors of a given type that have
 917:          been accumulated in association with a particular group
 918:          during internal MTA processing."
 919:       ::= {mtaGroupErrorEntry 2}
 920: 
 921:    mtaGroupOutboundErrorCount OBJECT-TYPE
 922:       SYNTAX Counter32
 923:       MAX-ACCESS read-only
 924:       STATUS current
 925:       DESCRIPTION
 926:         "Count of the number of errors of a given type that have
 927:          been accumulated in association with a particular group's
 928:          outbound connection activities. In the case of an SMTP
 929:          client these will typically be errors reported while
 930:          attempting to contact or while communicating with the
 931:          remote SMTP server. In the case of X.400 these will
 932:          typically be errors encountered while constructing
 933:          or attempting to deliver an outgoing message."
 934:       ::= {mtaGroupErrorEntry 3}
 935: 
 936:    mtaStatusCode OBJECT-TYPE
 937:       SYNTAX INTEGER (4000000..5999999)

 938:       MAX-ACCESS not-accessible
 939:       STATUS current
 940:       DESCRIPTION
 941:         "An index capable of representing an Enhanced Mail System
 942:          Status Code.  Enhanced Mail System Status Codes are
 943:          defined in RFC 1893.  These codes have the form
 944: 
 945:              class.subject.detail
 946: 
 947:          Here 'class' is either 2, 4, or 5 and both 'subject' and
 948:          'detail'  are integers in the range 0..999. Given a status
 949:          code the corresponding index value is defined to be
 950:          ((class * 1000) + subject) * 1000 + detail.  Both SMTP
 951:          error response codes and X.400 reason and diagnostic codes
 952:          can be mapped into these codes, resulting in a namespace
 953:          capable of describing most error conditions a mail system
 954:          encounters in a generic yet detailed way."
 955:       ::= {mtaGroupErrorEntry 4}
 956: 
 957:    -- Conformance information
 958: 
 959:    mtaConformance OBJECT IDENTIFIER ::= {mta 4}
 960: 
 961:    mtaGroups      OBJECT IDENTIFIER ::= {mtaConformance 1}
 962:    mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2}
 963: 
 964: 
 965:    -- Compliance statements
 966: 
 967:    mtaCompliance MODULE-COMPLIANCE
 968:       STATUS current
 969:       DESCRIPTION
 970:         "The compliance statement for RFC 1566 implementations
 971:          which support the Mail Monitoring MIB for basic
 972:          monitoring of MTAs."
 973:       MODULE  -- this module
 974:         MANDATORY-GROUPS {mtaRFC1566Group}
 975:       ::= {mtaCompliances 1}
 976: 
 977:    mtaAssocCompliance MODULE-COMPLIANCE
 978:       STATUS current
 979:       DESCRIPTION
 980:         "The compliance statement for RFC 1566 implementations
 981:          which support the Mail Monitoring MIB for monitoring
 982:          of MTAs and their associations."
 983:       MODULE  -- this module
 984:         MANDATORY-GROUPS {mtaRFC1566Group, mtaRFC1566AssocGroup}
 985:       ::= {mtaCompliances 2}
 986: 
 987:    mtaRFC2249Compliance MODULE-COMPLIANCE
 988:       STATUS current
 989:       DESCRIPTION
 990:         "The compliance statement for RFC 2249 implementations
 991:          which support the Mail Monitoring MIB for basic
 992:          monitoring of MTAs."
 993:       MODULE  -- this module
 994:         MANDATORY-GROUPS {mtaRFC2249Group}
 995:       ::= {mtaCompliances 5}
 996: 
 997:    mtaRFC2249AssocCompliance MODULE-COMPLIANCE
 998:       STATUS current
 999:       DESCRIPTION
1000:         "The compliance statement for RFC 2249 implementations
1001:          which support the Mail Monitoring MIB for monitoring of
1002:          MTAs and their associations."
1003:       MODULE  -- this module
1004:         MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup}
1005:       ::= {mtaCompliances 6}
1006: 
1007:    mtaRFC2249ErrorCompliance MODULE-COMPLIANCE
1008:       STATUS current
1009:       DESCRIPTION
1010:         "The compliance statement for RFC 2249 implementations
1011:          which support the Mail Monitoring MIB for monitoring of
1012:          MTAs and detailed errors."
1013:       MODULE  -- this module
1014:         MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249ErrorGroup}
1015:       ::= {mtaCompliances 7}
1016: 
1017:    mtaRFC2249FullCompliance MODULE-COMPLIANCE
1018:       STATUS current
1019:       DESCRIPTION
1020:         "The compliance statement for RFC 2249 implementations
1021:          which support the full Mail Monitoring MIB for
1022:          monitoring of MTAs, associations, and detailed errors."
1023:       MODULE  -- this module
1024:         MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup,
1025:                           mtaRFC2249ErrorGroup}
1026:       ::= {mtaCompliances 8}
1027: 
1028:    mtaRFC2789Compliance MODULE-COMPLIANCE
1029:       STATUS current
1030:       DESCRIPTION
1031:         "The compliance statement for RFC 2789 implementations
1032:          which support the Mail Monitoring MIB for basic
1033:          monitoring of MTAs."
1034:       MODULE  -- this module
1035:         MANDATORY-GROUPS {mtaRFC2789Group}
1036:       ::= {mtaCompliances 9}
1037: 
1038:    mtaRFC2789AssocCompliance MODULE-COMPLIANCE
1039:       STATUS current
1040:       DESCRIPTION
1041:         "The compliance statement for RFC 2789 implementations
1042:          which support the Mail Monitoring MIB for monitoring of
1043:          MTAs and their associations."
1044:       MODULE  -- this module
1045:         MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789AssocGroup}
1046:       ::= {mtaCompliances 10}
1047: 
1048:    mtaRFC2789ErrorCompliance MODULE-COMPLIANCE
1049:       STATUS current
1050:       DESCRIPTION
1051:         "The compliance statement for RFC 2789 implementations
1052:          which support the Mail Monitoring MIB for monitoring of
1053:          MTAs and detailed errors."
1054:       MODULE  -- this module
1055:         MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789ErrorGroup}
1056:       ::= {mtaCompliances 11}
1057: 
1058:    mtaRFC2789FullCompliance MODULE-COMPLIANCE
1059:       STATUS current
1060:       DESCRIPTION
1061:         "The compliance statement for RFC 2789 implementations
1062:          which support the full Mail Monitoring MIB for
1063:          monitoring of MTAs, associations, and detailed errors."
1064:       MODULE  -- this module
1065:         MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789AssocGroup,
1066:                           mtaRFC2789ErrorGroup}
1067:       ::= {mtaCompliances 12}
1068: 
1069:    -- Units of conformance
1070: 
1071:    mtaRFC1566Group OBJECT-GROUP
1072:       OBJECTS {
1073:         mtaReceivedMessages, mtaStoredMessages,
1074:         mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1075:         mtaTransmittedVolume, mtaReceivedRecipients,
1076:         mtaStoredRecipients, mtaTransmittedRecipients,
1077:         mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1078:         mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1079:         mtaGroupReceivedVolume, mtaGroupStoredVolume,
1080:         mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1081:         mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1082:         mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1083:         mtaGroupOutboundAssociations,
1084:         mtaGroupAccumulatedInboundAssociations,
1085:         mtaGroupAccumulatedOutboundAssociations,
1086:         mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1087:         mtaGroupRejectedInboundAssociations,
1088:         mtaGroupFailedOutboundAssociations,
1089:         mtaGroupInboundRejectionReason,
1090:         mtaGroupOutboundConnectFailureReason,
1091:         mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName}
1092:       STATUS current
1093:       DESCRIPTION
1094:         "A collection of objects providing basic monitoring of MTAs.
1095:          This is the original set of such objects defined in RFC
1096:          1566."
1097:       ::= {mtaGroups 10}
1098: 
1099:    mtaRFC1566AssocGroup OBJECT-GROUP
1100:       OBJECTS {
1101:         mtaGroupAssociationIndex}
1102:       STATUS current
1103:       DESCRIPTION
1104:         "A collection of objects providing monitoring of MTA
1105:          associations.  This is the original set of such objects
1106:          defined in RFC 1566."
1107:       ::= {mtaGroups 11}
1108: 
1109:    mtaRFC2249Group OBJECT-GROUP
1110:       OBJECTS {
1111:         mtaReceivedMessages, mtaStoredMessages,
1112:         mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1113:         mtaTransmittedVolume, mtaReceivedRecipients,
1114:         mtaStoredRecipients, mtaTransmittedRecipients,
1115:         mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
1116:         mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1117:         mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1118:         mtaGroupReceivedVolume, mtaGroupStoredVolume,
1119:         mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1120:         mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1121:         mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1122:         mtaGroupOutboundAssociations, mtaLoopsDetected,
1123:         mtaGroupAccumulatedInboundAssociations,
1124:         mtaGroupAccumulatedOutboundAssociations,
1125:         mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1126:         mtaGroupLastOutboundAssociationAttempt,
1127:         mtaGroupRejectedInboundAssociations,
1128:         mtaGroupFailedOutboundAssociations,
1129:         mtaGroupInboundRejectionReason,
1130:         mtaGroupOutboundConnectFailureReason,
1131:         mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName,
1132:         mtaGroupSuccessfulConvertedMessages,
1133:         mtaGroupFailedConvertedMessages, mtaGroupDescription,
1134:         mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy,
1135:         mtaGroupOldestMessageId, mtaGroupLoopsDetected}
1136:       STATUS current
1137:       DESCRIPTION
1138:         "A collection of objects providing basic monitoring of MTAs.
1139:          This group was originally defined in RFC 2249."
1140:       ::= {mtaGroups 4}
1141: 
1142:    mtaRFC2249AssocGroup OBJECT-GROUP
1143:       OBJECTS {
1144:         mtaGroupAssociationIndex}
1145: 
1146:       STATUS current
1147:       DESCRIPTION
1148:         "A collection of objects providing monitoring of MTA
1149:          associations.  This group was originally defined in RFC
1150:          2249."
1151:       ::= {mtaGroups 5}
1152: 
1153:    mtaRFC2249ErrorGroup OBJECT-GROUP
1154:       OBJECTS {
1155:         mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
1156:         mtaGroupOutboundErrorCount}
1157:       STATUS current
1158:       DESCRIPTION
1159:         "A collection of objects providing monitoring of
1160:          detailed MTA errors.  This group was originally defined
1161:          in RFC 2249."
1162:       ::= {mtaGroups 6}
1163: 
1164:    mtaRFC2789Group OBJECT-GROUP
1165:       OBJECTS {
1166:         mtaReceivedMessages, mtaStoredMessages,
1167:         mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1168:         mtaTransmittedVolume, mtaReceivedRecipients,
1169:         mtaStoredRecipients, mtaTransmittedRecipients,
1170:         mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
1171:         mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1172:         mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1173:         mtaGroupReceivedVolume, mtaGroupStoredVolume,
1174:         mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1175:         mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1176:         mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1177:         mtaGroupOutboundAssociations, mtaLoopsDetected,
1178:         mtaGroupAccumulatedInboundAssociations,
1179:         mtaGroupAccumulatedOutboundAssociations,
1180:         mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1181:         mtaGroupLastOutboundAssociationAttempt,
1182:         mtaGroupRejectedInboundAssociations,
1183:         mtaGroupFailedOutboundAssociations,
1184:         mtaGroupInboundRejectionReason,
1185:         mtaGroupOutboundConnectFailureReason,
1186:         mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName,
1187:         mtaGroupSuccessfulConvertedMessages,
1188:         mtaGroupFailedConvertedMessages, mtaGroupDescription,
1189:         mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy,
1190:         mtaGroupOldestMessageId, mtaGroupLoopsDetected}
1191:       STATUS current
1192:       DESCRIPTION
1193:         "A collection of objects providing basic monitoring of MTAs.
1194:          This is the appropriate group for RFC 2789."
1195:       ::= {mtaGroups 7}
1196: 
1197:    mtaRFC2789AssocGroup OBJECT-GROUP
1198:       OBJECTS {
1199:         mtaGroupAssociationIndex}
1200:       STATUS current
1201:       DESCRIPTION
1202:         "A collection of objects providing monitoring of MTA
1203:          associations.  This is the appropriate group for RFC
1204:          2789 association monitoring."
1205:       ::= {mtaGroups 8}
1206: 
1207:    mtaRFC2789ErrorGroup OBJECT-GROUP
1208:       OBJECTS {
1209:         mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
1210:         mtaGroupOutboundErrorCount}
1211:       STATUS current
1212:       DESCRIPTION
1213:         "A collection of objects providing monitoring of
1214:          detailed MTA errors.  This is the appropriate group
1215:          for RFC 2789 error monitoring."
1216:       ::= {mtaGroups 9}
1217: 
1218:    END
1219: 
1220: -- 
1221: --    Copyright (C) The Internet Society (2000).  All Rights Reserved.
1222: -- 
1223: --    This document and translations of it may be copied and furnished to
1224: --    others, and derivative works that comment on or otherwise explain it
1225: --    or assist in its implementation may be prepared, copied, published
1226: --    and distributed, in whole or in part, without restriction of any
1227: --    kind, provided that the above copyright notice and this paragraph are
1228: --    included on all such copies and derivative works.  However, this
1229: --    document itself may not be modified in any way, such as by removing
1230: --    the copyright notice or references to the Internet Society or other
1231: --    Internet organizations, except as needed for the purpose of
1232: --    developing Internet standards in which case the procedures for
1233: --    copyrights defined in the Internet Standards process must be
1234: --    followed, or as required to translate it into languages other than
1235: --    English.
1236: -- 
1237: --    The limited permissions granted above are perpetual and will not be
1238: --    revoked by the Internet Society or its successors or assigns.
1239: -- 
1240: --    This document and the information contained herein is provided on an
1241: --    "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
1242: --    TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
1243: --    BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
1244: --    HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
1245: --    MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1246: -- 
1247: