idnits 2.17.1 draft-ietf-madman-email-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 2) being 89 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 38 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. -- The draft header indicates that this document obsoletes RFC1566, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document obsoletes RFC2249, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 1999) is 9114 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '17' is defined on line 1449, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 1458, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 1461, but no explicit reference was found in the text == Unused Reference: '22' is defined on line 1464, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) -- Possible downref: Non-RFC (?) normative reference: ref. '16' ** Obsolete normative reference: RFC 1779 (ref. '17') (Obsoleted by RFC 2253, RFC 3494) ** Obsolete normative reference: RFC 2249 (ref. '18') (Obsoleted by RFC 2789) ** Obsolete normative reference: RFC 1566 (ref. '19') (Obsoleted by RFC 2249, RFC 2789) ** Obsolete normative reference: RFC 822 (ref. '21') (Obsoleted by RFC 2822) ** Obsolete normative reference: RFC 1893 (ref. '22') (Obsoleted by RFC 3463) Summary: 22 errors (**), 0 flaws (~~), 9 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Ned Freed, Innosoft 2 Internet Draft Steve Kille, ISODE Consortium 3 Obsoletes: 1566, 2249 5 Mail Monitoring MIB 7 May 1999 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with all 12 provisions of Section 10 of RFC 2026. 14 Internet-Drafts are working documents of the Internet Engineering Task 15 Force (IETF), its areas, and its working groups. Note that other groups 16 may also distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet- Drafts as reference material 21 or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Copyright Notice 31 Copyright (C) The Internet Society (1999). All Rights Reserved. 33 1. Introduction 35 This memo defines a portion of the Management Information Base (MIB) for 36 use with network management protocols in the Internet community. 37 Specifically, this memo extends the basic Network Services Monitoring 38 MIB defined in RFC XXXX [16] to allow monitoring of Message Transfer 39 Agents (MTAs). It may also be used to monitor MTA components within 40 gateways. 42 2. Table of Contents 44 1 Introduction .................................................... 1 45 2 Table of Contents ............................................... 2 46 3 The SNMPv2 Network Management Framework ......................... 2 47 4 Message Flow Model .............................................. 3 48 5 MTA Objects ..................................................... 4 49 6 Definitions ..................................................... 4 50 7 Changes made since RFC 2249 ..................................... 34 51 8 Acknowledgements ................................................ 35 52 9 References ...................................................... 35 53 10 Security Considerations ........................................ 37 54 11 Author and Chair Addresses ..................................... 38 55 12 Full Copyright Statement ....................................... 38 57 3. The SNMPv2 Network Management Framework 59 The SNMP Management Framework presently consists of five major 60 components: 62 o An overall architecture, described in RFC 2571 [1]. 64 o Mechanisms for describing and naming objects and events for the 65 purpose of management. The first version of this Structure of 66 Management Information (SMI) is called SMIv1 and described in 67 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 68 called SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 69 2580 [7]. 71 o Message protocols for transferring management information. The 72 first version of the SNMP message protocol is called SNMPv1 and 73 described in RFC 1157 [8]. A second version of the SNMP message 74 protocol, which is not an Internet standards track protocol, is 75 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 76 The third version of the message protocol is called SNMPv3 and 77 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 79 o Protocol operations for accessing management information. The 80 first set of protocol operations and associated PDU formats is 81 described in RFC 1157 [8]. A second set of protocol operations 82 and associated PDU formats is described in RFC 1905 [13]. 84 o A set of fundamental applications described in RFC 2573 [14] and 85 the view-based access control mechanism described in RFC 2575 87 [15]. 89 Managed objects are accessed via a virtual information store, termed the 90 Management Information Base or MIB. Objects in the MIB are defined 91 using the mechanisms defined in the SMI. 93 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 94 conforming to the SMIv1 can be produced through the appropriate 95 translations. The resulting translated MIB must be semantically 96 equivalent, except where objects or events are omitted because no 97 translation is possible (use of Counter64). Some machine readable 98 information in SMIv2 will be converted into textual descriptions in 99 SMIv1 during the translation process. However, this loss of machine 100 readable information is not considered to change the semantics of the 101 MIB. 103 4. Message Flow Model 105 A general model of message flow inside an MTA has to be presented before 106 a MIB can be described. Generally speaking, message flow is modelled as 107 occurring in four steps: 109 (1) Messages are received by the MTA from User Agents, Message 110 Stores, other MTAs, and gateways. 112 (2) The "next hop" for the each message is determined. This is simply 113 the destination the message is to be transmitted to; it may or 114 may not be the final destination of the message. Multiple "next 115 hops" may exist for a single message (as a result of either 116 having multiple recipients or distribution list expansion); this 117 may make it necessary to duplicate messages. 119 (3) If necessary messages are converted into the format that's 120 appropriate for the next hop. Conversion operations may be 121 successful or unsuccessful. 123 (4) Messages are transmitted to the appropriate destination, which 124 may be a User Agent, Message Store, another MTA, or gateway. 126 Storage of messages in the MTA occurs at some point during this process. 127 However, it is important to note that storage may occur at different and 128 possibly even multiple points during this process. For example, some 129 MTAs expand messages into multiple copies as they are received. In this 130 case (1), (2), and (3) may all occur prior to storage. Other MTAs store 131 messages precisely as they are received and perform all expansions and 132 conversions during retransmission processing. So here only (1) occurs 133 prior to storage. This leads to situations where, in general, a 134 measurement of messages received may not equal a measurement of messages 135 in store, or a measurement of messages stored may not equal a 136 measurement of messages retransmitted, or both. 138 5. MTA Objects 140 If there are one or more MTAs on the host, the following MIB may be used 141 to monitor them. Any number of the MTAs on a single host or group of 142 hosts may be monitored. Each MTA is dealt with as a separate network 143 service and has its own applTable entry in the Network Services 144 Monitoring MIB. 146 The MIB described in this document covers only the portion which is 147 specific to the monitoring of MTAs. The network service related part of 148 the MIB is covered in RFC XXXX [8]. 150 This MIB defines four tables. The first of these contains per-MTA 151 information that isn't specific to any particular part of MTA. The 152 second breaks each MTA down into a collection of separate components 153 called groups. Groups are described in detail in the comments embedded 154 in the MIB below. The third table provides a means of correlating 155 associations tracked by the network services MIB with specific groups 156 within different MTAs. Finally, the fourth table provides a means of 157 tracking any errors encountered during the operation of the MTA. The 158 first two tables must be implemented to conform with this MIB; the last 159 two are optional. 161 6. Definitions 163 MTA-MIB DEFINITIONS ::= BEGIN 165 IMPORTS 166 OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2 167 FROM SNMPv2-SMI 168 DisplayString, TimeInterval 169 FROM SNMPv2-TC 170 MODULE-COMPLIANCE, OBJECT-GROUP 171 FROM SNMPv2-CONF 172 applIndex, URLString 173 FROM NETWORK-SERVICES-MIB; 175 mta MODULE-IDENTITY 176 LAST-UPDATED "9905120000Z" 177 ORGANIZATION "IETF Mail and Directory Management Working Group" 178 CONTACT-INFO 179 " Ned Freed 181 Postal: Innosoft International, Inc. 182 1050 Lakes Drive 183 West Covina, CA 91790 184 US 186 Tel: +1 626 919 3600 187 Fax: +1 626 919 3614 189 E-Mail: ned.freed@innosoft.com" 190 DESCRIPTION 191 "The MIB module describing Message Transfer Agents (MTAs)" 192 REVISION "9905230000Z" 193 DESCRIPTION 194 "This revision, published in RFC YYYY, fixes a number of 195 technical problems found in previous versions: The 196 conformance groups for different versions of this MIB have 197 been corrected, the recommendation that an empty string be 198 returned if the last operation was successful has been 199 removed from mtaGroupInboundRejectionReason and 200 mtaGroupOutboundConnectFailureReason as it conflicts 201 with the stated purpose of these variables, and the 202 required mtaStatusCode entry has been added to 203 MtaGroupErrorEntry. It should be noted that this last 204 change in no way affects the bits on the wire." 205 REVISION "9708170000Z" 206 DESCRIPTION 207 "This revision, published in RFC 2249, adds the 208 mtaGroupDescription and mtaGroupURL fields, conversion 209 operation counters, a group hierarchy description mechanism, 210 counters for specific errors, oldest message IDs, per-MTA 211 and per-group loop counters, and a new table for tracking 212 any errors an MTA encounters." 213 REVISION "9311280000Z" 214 DESCRIPTION 215 "The original version of this MIB was published in RFC 1566" 216 ::= {mib-2 28} 218 mtaTable OBJECT-TYPE 219 SYNTAX SEQUENCE OF MtaEntry 220 MAX-ACCESS not-accessible 221 STATUS current 222 DESCRIPTION 223 "The table holding information specific to an MTA." 224 ::= {mta 1} 226 mtaEntry OBJECT-TYPE 227 SYNTAX MtaEntry 228 MAX-ACCESS not-accessible 229 STATUS current 230 DESCRIPTION 231 "The entry associated with each MTA." 232 INDEX {applIndex} 233 ::= {mtaTable 1} 235 MtaEntry ::= SEQUENCE { 236 mtaReceivedMessages 237 Counter32, 238 mtaStoredMessages 239 Gauge32, 240 mtaTransmittedMessages 241 Counter32, 242 mtaReceivedVolume 243 Counter32, 244 mtaStoredVolume 245 Gauge32, 246 mtaTransmittedVolume 247 Counter32, 248 mtaReceivedRecipients 249 Counter32, 250 mtaStoredRecipients 251 Gauge32, 252 mtaTransmittedRecipients 253 Counter32, 254 mtaSuccessfulConvertedMessages 255 Counter32, 256 mtaFailedConvertedMessages 257 Counter32, 258 mtaLoopsDetected 259 Counter32 260 } 261 mtaReceivedMessages OBJECT-TYPE 262 SYNTAX Counter32 263 MAX-ACCESS read-only 264 STATUS current 265 DESCRIPTION 266 "The number of messages received since MTA initialization. 267 This includes messages transmitted to this MTA from other 268 MTAs as well as messages that have been submitted to the 269 MTA directly by end-users or applications." 270 ::= {mtaEntry 1} 272 mtaStoredMessages OBJECT-TYPE 273 SYNTAX Gauge32 274 MAX-ACCESS read-only 275 STATUS current 276 DESCRIPTION 277 "The total number of messages currently stored in the MTA. 278 This includes messages that are awaiting transmission to 279 some other MTA or are waiting for delivery to an end-user 280 or application." 281 ::= {mtaEntry 2} 283 mtaTransmittedMessages OBJECT-TYPE 284 SYNTAX Counter32 285 MAX-ACCESS read-only 286 STATUS current 287 DESCRIPTION 288 "The number of messages transmitted since MTA initialization. 289 This includes messages that were transmitted to some other 290 MTA or are waiting for delivery to an end-user or 291 application." 292 ::= {mtaEntry 3} 294 mtaReceivedVolume OBJECT-TYPE 295 SYNTAX Counter32 296 UNITS "K-octets" 297 MAX-ACCESS read-only 298 STATUS current 299 DESCRIPTION 300 "The total volume of messages received since MTA 301 initialization, measured in kilo-octets. This volume should 302 include all transferred data that is logically above the mail 303 transport protocol level. For example, an SMTP-based MTA 304 should use the number of kilo-octets in the message header 305 and body, while an X.400-based MTA should use the number of 306 kilo-octets of P2 data. This includes messages transmitted 307 to this MTA from other MTAs as well as messages that have 308 been submitted to the MTA directly by end-users or 309 applications." 310 ::= {mtaEntry 4} 312 mtaStoredVolume OBJECT-TYPE 313 SYNTAX Gauge32 314 UNITS "K-octets" 315 MAX-ACCESS read-only 316 STATUS current 317 DESCRIPTION 318 "The total volume of messages currently stored in the MTA, 319 measured in kilo-octets. This volume should include all 320 stored data that is logically above the mail transport 321 protocol level. For example, an SMTP-based MTA should 322 use the number of kilo-octets in the message header and 323 body, while an X.400-based MTA would use the number of 324 kilo-octets of P2 data. This includes messages that are 325 awaiting transmission to some other MTA or are waiting 326 for delivery to an end-user or application." 327 ::= {mtaEntry 5} 329 mtaTransmittedVolume OBJECT-TYPE 330 SYNTAX Counter32 331 UNITS "K-octets" 332 MAX-ACCESS read-only 333 STATUS current 334 DESCRIPTION 335 "The total volume of messages transmitted since MTA 336 initialization, measured in kilo-octets. This volume should 337 include all transferred data that is logically above the mail 338 transport protocol level. For example, an SMTP-based MTA 339 should use the number of kilo-octets in the message header 340 and body, while an X.400-based MTA should use the number of 341 kilo-octets of P2 data. This includes messages that were 342 transmitted to some other MTA or are waiting for delivery 343 to an end-user or application." 344 ::= {mtaEntry 6} 346 mtaReceivedRecipients OBJECT-TYPE 347 SYNTAX Counter32 348 MAX-ACCESS read-only 349 STATUS current 350 DESCRIPTION 351 "The total number of recipients specified in all messages 352 received since MTA initialization. Recipients this MTA 353 has no responsibility for, i.e. inactive envelope 354 recipients or ones referred to in message headers, 355 should not be counted even if information about such 356 recipients is available. This includes messages 357 transmitted to this MTA from other MTAs as well as 358 messages that have been submitted to the MTA directly 359 by end-users or applications." 360 ::= {mtaEntry 7} 362 mtaStoredRecipients OBJECT-TYPE 363 SYNTAX Gauge32 364 MAX-ACCESS read-only 365 STATUS current 366 DESCRIPTION 367 "The total number of recipients specified in all messages 368 currently stored in the MTA. Recipients this MTA has no 369 responsibility for, i.e. inactive envelope recipients or 370 ones referred to in message headers, should not be 371 counted. This includes messages that are awaiting 372 transmission to some other MTA or are waiting for 373 delivery to an end-user or application." 374 ::= {mtaEntry 8} 376 mtaTransmittedRecipients OBJECT-TYPE 377 SYNTAX Counter32 378 MAX-ACCESS read-only 379 STATUS current 380 DESCRIPTION 381 "The total number of recipients specified in all messages 382 transmitted since MTA initialization. Recipients this 383 MTA had no responsibility for, i.e. inactive envelope 384 recipients or ones referred to in message headers, 385 should not be counted. This includes messages that were 386 transmitted to some other MTA or are waiting for 387 delivery to an end-user or application." 388 ::= {mtaEntry 9} 390 mtaSuccessfulConvertedMessages OBJECT-TYPE 391 SYNTAX Counter32 392 MAX-ACCESS read-only 393 STATUS current 394 DESCRIPTION 395 "The number of messages that have been successfully 396 converted from one form to another since MTA 397 initialization." 398 ::= {mtaEntry 10} 400 mtaFailedConvertedMessages OBJECT-TYPE 401 SYNTAX Counter32 402 MAX-ACCESS read-only 403 STATUS current 404 DESCRIPTION 405 "The number of messages for which an unsuccessful 406 attempt was made to convert them from one form to 407 another since MTA initialization." 408 ::= {mtaEntry 11} 410 mtaLoopsDetected OBJECT-TYPE 411 SYNTAX Counter32 412 MAX-ACCESS read-only 413 STATUS current 414 DESCRIPTION 415 "A message loop is defined as a situation where the MTA 416 decides that a given message will never be delivered to 417 one or more recipients and instead will continue to 418 loop endlessly through one or more MTAs. This variable 419 counts the number of times the MTA has detected such a 420 situation since MTA initialization. Note that the 421 mechanism MTAs use to detect loops (e.g., trace field 422 counting, count of references to this MTA in a trace 423 field, examination of DNS or other directory information, 424 etc.), the level at which loops are detected (e.g., per 425 message, per recipient, per directory entry, etc.), and 426 the handling of a loop once it is detected (e.g., looping 427 messages are held, looping messages are bounced or sent 428 to the postmaster, messages that the MTA knows will loop 429 won't be accepted, etc.) vary widely from one MTA to the 430 next and cannot be inferred from this variable." 431 ::= {mtaEntry 12} 433 -- MTAs typically group inbound reception, queue storage, and 434 -- outbound transmission in some way, rather than accounting for 435 -- such operations only across the MTA as a whole. In the most 436 -- extreme case separate information will be maintained for each 437 -- different entity that receives messages and for each entity 438 -- the MTA stores messages for and delivers messages to. Other 439 -- MTAs may elect to treat all reception equally, all queue 440 -- storage equally, all deliveries equally, or some combination 441 -- of this. Overlapped groupings are also possible, where an MTA 442 -- decomposes its traffic in different ways for different 443 -- purposes. 445 -- In any case, a grouping abstraction is an extremely useful for 446 -- breaking down the activities of an MTA. For purposes of 447 -- labelling this will be called a "group" in this MIB. 449 -- Each group contains all the variables needed to monitor all 450 -- aspects of an MTA's operation. However, the fact that all 451 -- groups contain all possible variables does not imply that all 452 -- groups must use all possible variables. For example, a single 453 -- group might be used to monitor only one kind of event (inbound 454 -- processing, outbound processing, or storage). In this sort of 455 -- configuration any counters that are unused as a result of a 456 -- given MTA's use of the group construct must be inaccessible; 457 -- e.g., returning either a noSuchName error (for an SNMPv1 get), 458 -- or a noSuchInstance exception (for an SNMPv2 get). 460 -- Groups can be created at any time after MTA initialization. Once 461 -- a group is created it should not be deleted or its mtaGroupIndex 462 -- changed unless the MTA is reinitialized. 464 -- Groups are not necessarily mutually exclusive. A given event may 465 -- be recorded by more than one group, a message may be seen as 466 -- stored by more than one group, and so on. Groups should be all 467 -- inclusive, however: if groups are implemented all aspects of an 468 -- MTA's operation should be registered in at least one group. 469 -- This freedom lets implementors use different sets of groups to 470 -- provide different "views" of an MTA. 472 -- The possibility of overlap between groups means that summing 473 -- variables across groups may not produce values equal to those in 474 -- the mtaTable. mtaTable should always provide accurate information 475 -- about the MTA as a whole. 477 -- The term "channel" is often used in MTA implementations; channels 478 -- are usually, but not always, equivalent to a group. However, 479 -- this MIB does not use the term "channel" because there is no 480 -- requirement that an MTA supporting this MIB has to map its 481 -- "channel" abstraction one-to-one onto the MIB's group abstraction. 483 -- An MTA may create a group or group of groups at any time. Once 484 -- created, however, an MTA cannot delete an entry for a group from 485 -- the group table. Deletion is only allowed when the MTA is 486 -- reinitialized, and is not required even then. This restriction 487 -- is imposed so that monitoring agents can rely on group 488 -- assignments being consistent across multiple query operations. 490 -- Groups may be laid out so as to form a hierarchical arrangement, 491 -- with some groups acting as subgroups for other groups. 492 -- Alternately, disjoint groups of groups may be used to provide 493 -- different sorts of "snapshots" of MTA operation. The 494 -- mtaGroupHierarchy variable provides an indication of how each 495 -- group fits into the overall arrangement being used. 497 -- Note that SNMP also defines and uses term "group". MTA groups are 498 -- NOT the same as SNMP groups. 500 mtaGroupTable OBJECT-TYPE 501 SYNTAX SEQUENCE OF MtaGroupEntry 502 MAX-ACCESS not-accessible 503 STATUS current 504 DESCRIPTION 505 "The table holding information specific to each MTA group." 506 ::= {mta 2} 508 mtaGroupEntry OBJECT-TYPE 509 SYNTAX MtaGroupEntry 510 MAX-ACCESS not-accessible 511 STATUS current 512 DESCRIPTION 513 "The entry associated with each MTA group." 514 INDEX {applIndex, mtaGroupIndex} 515 ::= {mtaGroupTable 1} 517 MtaGroupEntry ::= SEQUENCE { 518 mtaGroupIndex 519 INTEGER, 520 mtaGroupReceivedMessages 521 Counter32, 522 mtaGroupRejectedMessages 523 Counter32, 524 mtaGroupStoredMessages 525 Gauge32, 526 mtaGroupTransmittedMessages 527 Counter32, 528 mtaGroupReceivedVolume 529 Counter32, 530 mtaGroupStoredVolume 531 Gauge32, 532 mtaGroupTransmittedVolume 533 Counter32, 534 mtaGroupReceivedRecipients 535 Counter32, 536 mtaGroupStoredRecipients 537 Gauge32, 538 mtaGroupTransmittedRecipients 539 Counter32, 540 mtaGroupOldestMessageStored 541 TimeInterval, 542 mtaGroupInboundAssociations 543 Gauge32, 544 mtaGroupOutboundAssociations 545 Gauge32, 546 mtaGroupAccumulatedInboundAssociations 547 Counter32, 548 mtaGroupAccumulatedOutboundAssociations 549 Counter32, 550 mtaGroupLastInboundActivity 551 TimeInterval, 552 mtaGroupLastOutboundActivity 553 TimeInterval, 554 mtaGroupLastOutboundAssociationAttempt 555 TimeInterval, 556 mtaGroupRejectedInboundAssociations 557 Counter32, 558 mtaGroupFailedOutboundAssociations 559 Counter32, 560 mtaGroupInboundRejectionReason 561 DisplayString, 562 mtaGroupOutboundConnectFailureReason 563 DisplayString, 564 mtaGroupScheduledRetry 565 TimeInterval, 566 mtaGroupMailProtocol 567 OBJECT IDENTIFIER, 568 mtaGroupName 569 DisplayString, 570 mtaGroupSuccessfulConvertedMessages 571 Counter32, 572 mtaGroupFailedConvertedMessages 573 Counter32, 575 mtaGroupDescription 576 DisplayString, 577 mtaGroupURL 578 URLString, 579 mtaGroupCreationTime 580 TimeInterval, 581 mtaGroupHierarchy 582 INTEGER, 583 mtaGroupOldestMessageId 584 DisplayString, 585 mtaGroupLoopsDetected 586 Counter32 587 } 589 mtaGroupIndex OBJECT-TYPE 590 SYNTAX INTEGER (1..2147483647) 591 MAX-ACCESS not-accessible 592 STATUS current 593 DESCRIPTION 594 "The index associated with a group for a given MTA." 595 ::= {mtaGroupEntry 1} 597 mtaGroupReceivedMessages OBJECT-TYPE 598 SYNTAX Counter32 599 MAX-ACCESS read-only 600 STATUS current 601 DESCRIPTION 602 "The number of messages received to this group since 603 group creation." 604 ::= {mtaGroupEntry 2} 606 mtaGroupRejectedMessages OBJECT-TYPE 607 SYNTAX Counter32 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "The number of messages rejected by this group since 612 group creation." 613 ::= {mtaGroupEntry 3} 615 mtaGroupStoredMessages OBJECT-TYPE 616 SYNTAX Gauge32 617 MAX-ACCESS read-only 618 STATUS current 619 DESCRIPTION 620 "The total number of messages currently stored in this 621 group's queue." 622 ::= {mtaGroupEntry 4} 624 mtaGroupTransmittedMessages OBJECT-TYPE 625 SYNTAX Counter32 626 MAX-ACCESS read-only 627 STATUS current 628 DESCRIPTION 629 "The number of messages transmitted by this group since 630 group creation." 631 ::= {mtaGroupEntry 5} 633 mtaGroupReceivedVolume OBJECT-TYPE 634 SYNTAX Counter32 635 UNITS "K-octets" 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "The total volume of messages received to this group since 640 group creation, measured in kilo-octets. This volume 641 should include all transferred data that is logically above 642 the mail transport protocol level. For example, an 643 SMTP-based MTA should use the number of kilo-octets in the 644 message header and body, while an X.400-based MTA should use 645 the number of kilo-octets of P2 data." 646 ::= {mtaGroupEntry 6} 648 mtaGroupStoredVolume OBJECT-TYPE 649 SYNTAX Gauge32 650 UNITS "K-octets" 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION 654 "The total volume of messages currently stored in this 655 group's queue, measured in kilo-octets. This volume should 656 include all stored data that is logically above the mail 657 transport protocol level. For example, an SMTP-based 658 MTA should use the number of kilo-octets in the message 659 header and body, while an X.400-based MTA would use the 660 number of kilo-octets of P2 data." 661 ::= {mtaGroupEntry 7} 663 mtaGroupTransmittedVolume OBJECT-TYPE 664 SYNTAX Counter32 665 UNITS "K-octets" 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "The total volume of messages transmitted by this group 670 since group creation, measured in kilo-octets. This 671 volume should include all transferred data that is logically 672 above the mail transport protocol level. For example, an 673 SMTP-based MTA should use the number of kilo-octets in the 674 message header and body, while an X.400-based MTA should use 675 the number of kilo-octets of P2 data." 676 ::= {mtaGroupEntry 8} 678 mtaGroupReceivedRecipients OBJECT-TYPE 679 SYNTAX Counter32 680 MAX-ACCESS read-only 681 STATUS current 682 DESCRIPTION 683 "The total number of recipients specified in all messages 684 received to this group since group creation. 685 Recipients this MTA has no responsibility for should not 686 be counted." 687 ::= {mtaGroupEntry 9} 689 mtaGroupStoredRecipients OBJECT-TYPE 690 SYNTAX Gauge32 691 MAX-ACCESS read-only 692 STATUS current 693 DESCRIPTION 694 "The total number of recipients specified in all messages 695 currently stored in this group's queue. Recipients this 696 MTA has no responsibility for should not be counted." 697 ::= {mtaGroupEntry 10} 699 mtaGroupTransmittedRecipients OBJECT-TYPE 700 SYNTAX Counter32 701 MAX-ACCESS read-only 702 STATUS current 703 DESCRIPTION 704 "The total number of recipients specified in all messages 705 transmitted by this group since group creation. 706 Recipients this MTA had no responsibility for should not 707 be counted." 708 ::= {mtaGroupEntry 11} 710 mtaGroupOldestMessageStored OBJECT-TYPE 711 SYNTAX TimeInterval 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "Time since the oldest message in this group's queue was 716 placed in the queue." 717 ::= {mtaGroupEntry 12} 719 mtaGroupInboundAssociations OBJECT-TYPE 720 SYNTAX Gauge32 721 MAX-ACCESS read-only 722 STATUS current 723 DESCRIPTION 724 "The number of current associations to the group, where the 725 group is the responder." 726 ::= {mtaGroupEntry 13} 728 mtaGroupOutboundAssociations OBJECT-TYPE 729 SYNTAX Gauge32 730 MAX-ACCESS read-only 731 STATUS current 732 DESCRIPTION 733 "The number of current associations to the group, where the 734 group is the initiator." 735 ::= {mtaGroupEntry 14} 737 mtaGroupAccumulatedInboundAssociations OBJECT-TYPE 738 SYNTAX Counter32 739 MAX-ACCESS read-only 740 STATUS current 741 DESCRIPTION 742 "The total number of associations to the group since 743 group creation, where the MTA was the responder." 744 ::= {mtaGroupEntry 15} 746 mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE 747 SYNTAX Counter32 748 MAX-ACCESS read-only 749 STATUS current 750 DESCRIPTION 751 "The total number of associations from the group since 752 group creation, where the MTA was the initiator." 753 ::= {mtaGroupEntry 16} 755 mtaGroupLastInboundActivity OBJECT-TYPE 756 SYNTAX TimeInterval 757 MAX-ACCESS read-only 758 STATUS current 759 DESCRIPTION 760 "Time since the last time that this group had an active 761 inbound association for purposes of message reception." 762 ::= {mtaGroupEntry 17} 764 mtaGroupLastOutboundActivity OBJECT-TYPE 765 SYNTAX TimeInterval 766 MAX-ACCESS read-only 767 STATUS current 768 DESCRIPTION 769 "Time since the last time that this group had a 770 successful outbound association for purposes of 771 message delivery." 772 ::= {mtaGroupEntry 18} 774 mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE 775 SYNTAX TimeInterval 776 MAX-ACCESS read-only 777 STATUS current 778 DESCRIPTION 779 "Time since the last time that this group attempted 780 to make an outbound association for purposes of 781 message delivery." 782 ::= {mtaGroupEntry 34} 784 mtaGroupRejectedInboundAssociations OBJECT-TYPE 785 SYNTAX Counter32 786 MAX-ACCESS read-only 787 STATUS current 788 DESCRIPTION 789 "The total number of inbound associations the group has 790 rejected, since group creation. Rejected associations 791 are not counted in the accumulated association totals." 792 ::= {mtaGroupEntry 19} 794 mtaGroupFailedOutboundAssociations OBJECT-TYPE 795 SYNTAX Counter32 796 MAX-ACCESS read-only 797 STATUS current 798 DESCRIPTION 799 "The total number associations where the group was the 800 initiator and association establishment has failed, 801 since group creation. Failed associations are 802 not counted in the accumulated association totals." 803 ::= {mtaGroupEntry 20} 805 mtaGroupInboundRejectionReason OBJECT-TYPE 806 SYNTAX DisplayString 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "The failure reason, if any, for the last association this 811 group refused to respond to. If no association attempt 812 has been made since the MTA was initialized the value 813 should be 'never'." 814 ::= {mtaGroupEntry 21} 816 mtaGroupOutboundConnectFailureReason OBJECT-TYPE 817 SYNTAX DisplayString 818 MAX-ACCESS read-only 819 STATUS current 820 DESCRIPTION 821 "The failure reason, if any, for the last association attempt 822 this group initiated. If no association attempt has been 823 made since the MTA was initialized the value should be 824 'never'." 825 ::= {mtaGroupEntry 22} 827 mtaGroupScheduledRetry OBJECT-TYPE 828 SYNTAX TimeInterval 829 MAX-ACCESS read-only 830 STATUS current 831 DESCRIPTION 832 "The amount of time until this group is next scheduled to 833 attempt to make an association." 834 ::= {mtaGroupEntry 23} 836 mtaGroupMailProtocol OBJECT-TYPE 837 SYNTAX OBJECT IDENTIFIER 838 MAX-ACCESS read-only 839 STATUS current 840 DESCRIPTION 841 "An identification of the protocol being used by this group. 842 For an group employing OSI protocols, this will be the 843 Application Context. For Internet applications, the IANA 844 maintains a registry of the OIDs which correspond to well-known 845 message transfer protocols. If the application protocol is 846 not listed in the registry, an OID value of the form 847 {applTCPProtoID port} or {applUDProtoID port} are used for 848 TCP-based and UDP-based protocols, respectively. In either 849 case 'port' corresponds to the primary port number being 850 used by the group. applTCPProtoID and applUDPProtoID are 851 defined in the NETWORK-SERVICES-MIB, RFC XXXX." 852 ::= {mtaGroupEntry 24} 854 mtaGroupName OBJECT-TYPE 855 SYNTAX DisplayString 856 MAX-ACCESS read-only 857 STATUS current 858 DESCRIPTION 859 "A descriptive name for the group. If this group connects to 860 a single remote MTA this should be the name of that MTA. If 861 this in turn is an Internet MTA this should be the domain 862 name. For an OSI MTA it should be the string encoded 863 distinguished name of the managed object using the format 864 defined in RFC 1779. For X.400(1984) MTAs which do not 865 have a Distinguished Name, the RFC 2156 syntax 866 'mta in globalid' used in X400-Received: fields can be 867 used." 868 ::= {mtaGroupEntry 25} 870 mtaGroupSuccessfulConvertedMessages OBJECT-TYPE 871 SYNTAX Counter32 872 MAX-ACCESS read-only 873 STATUS current 874 DESCRIPTION 875 "The number of messages that have been successfully 876 converted from one form to another in this group 877 since group creation." 878 ::= {mtaGroupEntry 26} 880 mtaGroupFailedConvertedMessages OBJECT-TYPE 881 SYNTAX Counter32 882 MAX-ACCESS read-only 883 STATUS current 884 DESCRIPTION 885 "The number of messages for which an unsuccessful 886 attempt was made to convert them from one form to 887 another in this group since group creation." 888 ::= {mtaGroupEntry 27} 890 mtaGroupDescription OBJECT-TYPE 891 SYNTAX DisplayString 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "A description of the group's purpose. This information is 896 intended to identify the group in a status display." 897 ::= {mtaGroupEntry 28} 899 mtaGroupURL OBJECT-TYPE 900 SYNTAX URLString 901 MAX-ACCESS read-only 902 STATUS current 903 DESCRIPTION 904 "A URL pointing to a description of the group. This 905 information is intended to identify and briefly describe 906 the group in a status display." 907 ::= {mtaGroupEntry 29} 909 mtaGroupCreationTime OBJECT-TYPE 910 SYNTAX TimeInterval 911 MAX-ACCESS read-only 912 STATUS current 913 DESCRIPTION 914 "Time since this group was first created." 915 ::= {mtaGroupEntry 30} 917 mtaGroupHierarchy OBJECT-TYPE 918 SYNTAX INTEGER (-2147483648..2147483647) 919 MAX-ACCESS read-only 920 STATUS current 921 DESCRIPTION 922 "Describes how this group fits into the hierarchy. A 923 positive value is interpreted as an mtaGroupIndex 924 value for some other group whose variables include 925 those of this group (and usually others). A negative 926 value is interpreted as a group collection code: Groups 927 with common negative hierarchy values comprise one 928 particular breakdown of MTA activity as a whole. A 929 zero value means that this MIB implementation doesn't 930 implement hierarchy indicators and thus the overall 931 group hierarchy cannot be determined." 932 ::= {mtaGroupEntry 31} 934 mtaGroupOldestMessageId OBJECT-TYPE 935 SYNTAX DisplayString 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "Message ID of the oldest message in the group's queue. 940 Whenever possible this should be in the form of an 941 RFC 822 msg-id; X.400 may convert X.400 message 942 identifiers to this form by following the rules laid 943 out in RFC2156." 944 ::= {mtaGroupEntry 32} 946 mtaGroupLoopsDetected OBJECT-TYPE 947 SYNTAX Counter32 948 MAX-ACCESS read-only 949 STATUS current 950 DESCRIPTION 951 "A message loop is defined as a situation where the MTA 952 decides that a given message will never be delivered to 953 one or more recipients and instead will continue to 954 loop endlessly through one or more MTAs. This variable 955 counts the number of times the MTA has detected such a 956 situation in conjunction with something associated with 957 this group since group creation. Note that the 958 mechanism MTAs use to detect loops (e.g., trace field 959 counting, count of references to this MTA in a trace 960 field, examination of DNS or other directory information, 961 etc.), the level at which loops are detected (e.g., per 962 message, per recipient, per directory entry, etc.), and 963 the handling of a loop once it is detected (e.g., looping 964 messages are held, looping messages are bounced or sent 965 to the postmaster, messages that the MTA knows will loop 966 won't be accepted, etc.) vary widely from one MTA to the 967 next and cannot be inferred from this variable." 968 ::= {mtaGroupEntry 33} 970 -- The mtaGroupAssociationTable provides a means of correlating 971 -- entries in the network services association table with the 972 -- MTA group responsible for the association. 974 mtaGroupAssociationTable OBJECT-TYPE 975 SYNTAX SEQUENCE OF MtaGroupAssociationEntry 976 MAX-ACCESS not-accessible 977 STATUS current 978 DESCRIPTION 979 "The table holding information regarding the associations 980 for each MTA group." 981 ::= {mta 3} 983 mtaGroupAssociationEntry OBJECT-TYPE 984 SYNTAX MtaGroupAssociationEntry 985 MAX-ACCESS not-accessible 986 STATUS current 987 DESCRIPTION 988 "The entry holding information regarding the associations 989 for each MTA group." 990 INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex} 991 ::= {mtaGroupAssociationTable 1} 993 MtaGroupAssociationEntry ::= SEQUENCE { 994 mtaGroupAssociationIndex 995 INTEGER 996 } 998 mtaGroupAssociationIndex OBJECT-TYPE 999 SYNTAX INTEGER (1..2147483647) 1000 MAX-ACCESS read-only 1001 STATUS current 1002 DESCRIPTION 1003 "Reference into association table to allow correlation of 1004 this group's active associations with the association table." 1005 ::= {mtaGroupAssociationEntry 1} 1007 -- The mtaGroupErrorTable gives each group a way of tallying 1008 -- the specific errors it has encountered. The mechanism 1009 -- defined here uses RFC 1893 status codes to identify 1010 -- various specific errors. There are also classes for generic 1011 -- errors of various sorts, and the entire mechanism is also 1012 -- extensible, in that new error codes can be defined at any 1013 -- time. 1015 mtaGroupErrorTable OBJECT-TYPE 1016 SYNTAX SEQUENCE OF MtaGroupErrorEntry 1017 MAX-ACCESS not-accessible 1018 STATUS current 1019 DESCRIPTION 1020 "The table holding information regarding accumulated errors 1021 for each MTA group." 1022 ::= {mta 5} 1024 mtaGroupErrorEntry OBJECT-TYPE 1025 SYNTAX MtaGroupErrorEntry 1026 MAX-ACCESS not-accessible 1027 STATUS current 1028 DESCRIPTION 1029 "The entry holding information regarding accumulated 1030 errors for each MTA group." 1031 INDEX {applIndex, mtaGroupIndex, mtaStatusCode} 1032 ::= {mtaGroupErrorTable 1} 1034 MtaGroupErrorEntry ::= SEQUENCE { 1035 mtaStatusCode 1036 INTEGER (4000000..5999999), 1037 mtaGroupInboundErrorCount 1038 Counter32, 1039 mtaGroupInternalErrorCount 1040 Counter32, 1041 mtaGroupOutboundErrorCount 1042 Counter32 1043 } 1045 mtaGroupInboundErrorCount OBJECT-TYPE 1046 SYNTAX Counter32 1047 MAX-ACCESS read-only 1048 STATUS current 1049 DESCRIPTION 1050 "Count of the number of errors of a given type that have 1051 been accumulated in association with a particular group 1052 while processing incoming messages. In the case of SMTP 1053 these will typically be errors reporting by an SMTP 1054 server to the remote client; in the case of X.400 1055 these will typically be errors encountered while 1056 processing an incoming message." 1057 ::= {mtaGroupErrorEntry 1} 1059 mtaGroupInternalErrorCount OBJECT-TYPE 1060 SYNTAX Counter32 1061 MAX-ACCESS read-only 1062 STATUS current 1063 DESCRIPTION 1064 "Count of the number of errors of a given type that have 1065 been accumulated in association with a particular group 1066 during internal MTA processing." 1067 ::= {mtaGroupErrorEntry 2} 1069 mtaGroupOutboundErrorCount OBJECT-TYPE 1070 SYNTAX Counter32 1071 MAX-ACCESS read-only 1072 STATUS current 1073 DESCRIPTION 1074 "Count of the number of errors of a given type that have 1075 been accumulated in association with a particular group's 1076 outbound connection activities. In the case of an SMTP 1077 client these will typically be errors reported while 1078 attempting to contact or while communicating with the 1079 remote SMTP server. In the case of X.400 these will 1080 typically be errors encountered while constructing 1081 or attempting to deliver an outgoing message." 1082 ::= {mtaGroupErrorEntry 3} 1084 mtaStatusCode OBJECT-TYPE 1085 SYNTAX INTEGER (4000000..5999999) 1086 MAX-ACCESS not-accessible 1087 STATUS current 1088 DESCRIPTION 1089 "An index capable of representing an Enhanced Mail System 1090 Status Code. Enhanced Mail System Status Codes are 1091 defined in RFC 1893. These codes have the form 1093 class.subject.detail 1095 Here 'class' is either 2, 4, or 5 and both 'subject' and 1096 'detail' are integers in the range 0..999. Given a status 1097 code the corresponding index value is defined to be 1098 ((class * 1000) + subject) * 1000 + detail. Both SMTP 1099 error response codes and X.400 reason and diagnostic codes 1100 can be mapped into these codes, resulting in a namespace 1101 capable of describing most error conditions a mail system 1102 encounters in a generic yet detailed way." 1103 ::= {mtaGroupErrorEntry 4} 1105 -- Conformance information 1107 mtaConformance OBJECT IDENTIFIER ::= {mta 4} 1109 mtaGroups OBJECT IDENTIFIER ::= {mtaConformance 1} 1110 mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2} 1112 -- Compliance statements 1114 mtaCompliance MODULE-COMPLIANCE 1115 STATUS current 1116 DESCRIPTION 1117 "The compliance statement for RFC 1566 implementations 1118 which support the Mail Monitoring MIB for basic 1119 monitoring of MTAs." 1120 MODULE -- this module 1121 MANDATORY-GROUPS {mtaRFC1566Group} 1122 ::= {mtaCompliances 1} 1124 mtaAssocCompliance MODULE-COMPLIANCE 1125 STATUS current 1126 DESCRIPTION 1127 "The compliance statement for RFC 1566 implementations 1128 which support the Mail Monitoring MIB for monitoring 1129 of MTAs and their associations." 1130 MODULE -- this module 1131 MANDATORY-GROUPS {mtaRFC1566Group, mtaRFC1566AssocGroup} 1132 ::= {mtaCompliances 2} 1134 mtaRFC2249Compliance MODULE-COMPLIANCE 1135 STATUS current 1136 DESCRIPTION 1137 "The compliance statement for RFC 2249 implementations 1138 which support the Mail Monitoring MIB for basic 1139 monitoring of MTAs." 1140 MODULE -- this module 1141 MANDATORY-GROUPS {mtaRFC2249Group} 1142 ::= {mtaCompliances 5} 1144 mtaRFC2249AssocCompliance MODULE-COMPLIANCE 1145 STATUS current 1146 DESCRIPTION 1147 "The compliance statement for RFC 2249 implementations 1148 which support the Mail Monitoring MIB for monitoring of 1149 MTAs and their associations." 1150 MODULE -- this module 1151 MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup} 1152 ::= {mtaCompliances 6} 1154 mtaRFC2249ErrorCompliance MODULE-COMPLIANCE 1155 STATUS current 1156 DESCRIPTION 1157 "The compliance statement for RFC 2249 implementations 1158 which support the Mail Monitoring MIB for monitoring of 1159 MTAs and detailed errors." 1160 MODULE -- this module 1161 MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249ErrorGroup} 1162 ::= {mtaCompliances 7} 1164 mtaRFC2249FullCompliance MODULE-COMPLIANCE 1165 STATUS current 1166 DESCRIPTION 1167 "The compliance statement for RFC 2249 implementations 1168 which support the full Mail Monitoring MIB for 1169 monitoring of MTAs, associations, and detailed errors." 1170 MODULE -- this module 1171 MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup, 1172 mtaRFC2249ErrorGroup} 1173 ::= {mtaCompliances 8} 1175 mtaRFCYYYYCompliance MODULE-COMPLIANCE 1176 STATUS current 1177 DESCRIPTION 1178 "The compliance statement for RFC YYYY implementations 1179 which support the Mail Monitoring MIB for basic 1180 monitoring of MTAs." 1181 MODULE -- this module 1182 MANDATORY-GROUPS {mtaRFCYYYYGroup} 1183 ::= {mtaCompliances 9} 1185 mtaRFCYYYYAssocCompliance MODULE-COMPLIANCE 1186 STATUS current 1187 DESCRIPTION 1188 "The compliance statement for RFC YYYY implementations 1189 which support the Mail Monitoring MIB for monitoring of 1190 MTAs and their associations." 1191 MODULE -- this module 1192 MANDATORY-GROUPS {mtaRFCYYYYGroup, mtaRFCYYYYAssocGroup} 1193 ::= {mtaCompliances 10} 1195 mtaRFCYYYYErrorCompliance MODULE-COMPLIANCE 1196 STATUS current 1197 DESCRIPTION 1198 "The compliance statement for RFC YYYY implementations 1199 which support the Mail Monitoring MIB for monitoring of 1200 MTAs and detailed errors." 1201 MODULE -- this module 1202 MANDATORY-GROUPS {mtaRFCYYYYGroup, mtaRFCYYYYErrorGroup} 1203 ::= {mtaCompliances 11} 1205 mtaRFCYYYYFullCompliance MODULE-COMPLIANCE 1206 STATUS current 1207 DESCRIPTION 1208 "The compliance statement for RFC YYYY implementations 1209 which support the full Mail Monitoring MIB for 1210 monitoring of MTAs, associations, and detailed errors." 1211 MODULE -- this module 1212 MANDATORY-GROUPS {mtaRFCYYYYGroup, mtaRFCYYYYAssocGroup, 1213 mtaRFCYYYYErrorGroup} 1214 ::= {mtaCompliances 12} 1216 -- Units of conformance 1218 mtaRFC1566Group OBJECT-GROUP 1219 OBJECTS { 1220 mtaReceivedMessages, mtaStoredMessages, 1221 mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, 1222 mtaTransmittedVolume, mtaReceivedRecipients, 1223 mtaStoredRecipients, mtaTransmittedRecipients, 1224 mtaGroupReceivedMessages, mtaGroupRejectedMessages, 1225 mtaGroupStoredMessages, mtaGroupTransmittedMessages, 1226 mtaGroupReceivedVolume, mtaGroupStoredVolume, 1227 mtaGroupTransmittedVolume, mtaGroupReceivedRecipients, 1228 mtaGroupStoredRecipients, mtaGroupTransmittedRecipients, 1229 mtaGroupOldestMessageStored, mtaGroupInboundAssociations, 1230 mtaGroupOutboundAssociations, 1231 mtaGroupAccumulatedInboundAssociations, 1232 mtaGroupAccumulatedOutboundAssociations, 1233 mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity, 1234 mtaGroupRejectedInboundAssociations, 1235 mtaGroupFailedOutboundAssociations, 1236 mtaGroupInboundRejectionReason, 1237 mtaGroupOutboundConnectFailureReason, 1238 mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName} 1239 STATUS current 1240 DESCRIPTION 1241 "A collection of objects providing basic monitoring of MTAs. 1242 This is the original set of such objects defined in RFC 1243 1566." 1244 ::= {mtaGroups 10} 1246 mtaRFC1566AssocGroup OBJECT-GROUP 1247 OBJECTS { 1248 mtaGroupAssociationIndex} 1249 STATUS current 1250 DESCRIPTION 1251 "A collection of objects providing monitoring of MTA 1252 associations. This is the original set of such objects 1253 defined in RFC 1566." 1254 ::= {mtaGroups 11} 1256 mtaRFC2249Group OBJECT-GROUP 1257 OBJECTS { 1258 mtaReceivedMessages, mtaStoredMessages, 1259 mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, 1260 mtaTransmittedVolume, mtaReceivedRecipients, 1261 mtaStoredRecipients, mtaTransmittedRecipients, 1262 mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages, 1263 mtaGroupReceivedMessages, mtaGroupRejectedMessages, 1264 mtaGroupStoredMessages, mtaGroupTransmittedMessages, 1265 mtaGroupReceivedVolume, mtaGroupStoredVolume, 1266 mtaGroupTransmittedVolume, mtaGroupReceivedRecipients, 1267 mtaGroupStoredRecipients, mtaGroupTransmittedRecipients, 1268 mtaGroupOldestMessageStored, mtaGroupInboundAssociations, 1269 mtaGroupOutboundAssociations, mtaLoopsDetected, 1270 mtaGroupAccumulatedInboundAssociations, 1271 mtaGroupAccumulatedOutboundAssociations, 1272 mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity, 1273 mtaGroupLastOutboundAssociationAttempt, 1274 mtaGroupRejectedInboundAssociations, 1275 mtaGroupFailedOutboundAssociations, 1276 mtaGroupInboundRejectionReason, 1277 mtaGroupOutboundConnectFailureReason, 1278 mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName, 1279 mtaGroupSuccessfulConvertedMessages, 1280 mtaGroupFailedConvertedMessages, mtaGroupDescription, 1281 mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy, 1282 mtaGroupOldestMessageId, mtaGroupLoopsDetected} 1283 STATUS current 1284 DESCRIPTION 1285 "A collection of objects providing basic monitoring of MTAs. 1286 This group was originally defined in RFC 2249." 1287 ::= {mtaGroups 4} 1289 mtaRFC2249AssocGroup OBJECT-GROUP 1290 OBJECTS { 1291 mtaGroupAssociationIndex} 1292 STATUS current 1293 DESCRIPTION 1294 "A collection of objects providing monitoring of MTA 1295 associations. This group was originally defined in RFC 1296 2249." 1297 ::= {mtaGroups 5} 1299 mtaRFC2249ErrorGroup OBJECT-GROUP 1300 OBJECTS { 1301 mtaGroupInboundErrorCount, mtaGroupInternalErrorCount, 1302 mtaGroupOutboundErrorCount} 1303 STATUS current 1304 DESCRIPTION 1305 "A collection of objects providing monitoring of 1306 detailed MTA errors. This group was originally defined 1307 in RFC 2249." 1308 ::= {mtaGroups 6} 1310 mtaRFCYYYYGroup OBJECT-GROUP 1311 OBJECTS { 1312 mtaReceivedMessages, mtaStoredMessages, 1313 mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, 1314 mtaTransmittedVolume, mtaReceivedRecipients, 1315 mtaStoredRecipients, mtaTransmittedRecipients, 1316 mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages, 1317 mtaGroupReceivedMessages, mtaGroupRejectedMessages, 1318 mtaGroupStoredMessages, mtaGroupTransmittedMessages, 1319 mtaGroupReceivedVolume, mtaGroupStoredVolume, 1320 mtaGroupTransmittedVolume, mtaGroupReceivedRecipients, 1321 mtaGroupStoredRecipients, mtaGroupTransmittedRecipients, 1322 mtaGroupOldestMessageStored, mtaGroupInboundAssociations, 1323 mtaGroupOutboundAssociations, mtaLoopsDetected, 1324 mtaGroupAccumulatedInboundAssociations, 1325 mtaGroupAccumulatedOutboundAssociations, 1326 mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity, 1327 mtaGroupLastOutboundAssociationAttempt, 1328 mtaGroupRejectedInboundAssociations, 1329 mtaGroupFailedOutboundAssociations, 1330 mtaGroupInboundRejectionReason, 1331 mtaGroupOutboundConnectFailureReason, 1332 mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName, 1333 mtaGroupSuccessfulConvertedMessages, 1334 mtaGroupFailedConvertedMessages, mtaGroupDescription, 1335 mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy, 1336 mtaGroupOldestMessageId, mtaGroupLoopsDetected} 1337 STATUS current 1338 DESCRIPTION 1339 "A collection of objects providing basic monitoring of MTAs. 1340 This is the appropriate group for RFC YYYY." 1341 ::= {mtaGroups 7} 1343 mtaRFCYYYYAssocGroup OBJECT-GROUP 1344 OBJECTS { 1345 mtaGroupAssociationIndex} 1346 STATUS current 1347 DESCRIPTION 1348 "A collection of objects providing monitoring of MTA 1349 associations. This is the appropriate group for RFC 1350 YYYY association monitoring." 1351 ::= {mtaGroups 8} 1353 mtaRFCYYYYErrorGroup OBJECT-GROUP 1354 OBJECTS { 1355 mtaGroupInboundErrorCount, mtaGroupInternalErrorCount, 1356 mtaGroupOutboundErrorCount} 1357 STATUS current 1358 DESCRIPTION 1359 "A collection of objects providing monitoring of 1360 detailed MTA errors. This is the appropriate group 1361 for RFC YYYY error monitoring." 1362 ::= {mtaGroups 9} 1364 END 1366 7. Changes made since RFC 2249 1368 This revision corrects a number of minor technical errors in the 1369 construction of the mail monitoring MIB in RFC 2249 [18]: 1371 (1) The conformance groups for different versions of this MIB have 1372 been corrected, 1374 (2) the required mtaStatusCode entry has been added to 1375 MtaGroupErrorEntry (which does not affect the bits on the wire in 1376 any way), and 1378 (3) the recommendation that an empty string be returned if the last 1379 operation was successful has been removed from 1380 mtaGroupInboundRejectionReason and 1381 mtaGroupOutboundConnectFailureReason as it conflicts with the 1382 stated purpose of these variables. 1384 8. Acknowledgements 1386 This document is a work product of the Mail and Directory Management 1387 (MADMAN) Working Group of the IETF. It is based on an earlier MIB 1388 designed by S. Kille, T. Lenggenhager, D. Partain, and W. Yeong. The 1389 Electronic Mail Association's TSC committee was instrumental in 1390 providing feedback on and suggesting enhancements to RFC 1566 [19] that 1391 have led to the present document. 1393 9. References 1395 [1] Harrington, D., Presuhn, R., and Wijnen, B., "An Architecture for 1396 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1398 [2] Rose, M. and McCloghrie, K., "Structure and Identification of 1399 Management Information for TCP/IP-based Internets", RFC 1155, May 1400 1990. 1402 [3] Rose, M. and McCloghrie, K., "Concise MIB Definitions", RFC 1212, 1403 March 1991. 1405 [4] Rose, M., "A Convention for Defining Traps for use with the SNMP", 1406 RFC 1215, March 1991. 1408 [5] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Structure of 1409 Management Information Version 2 (SMIv2)", RFC 2578, April 1999. 1411 [6] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Textual 1412 Conventions for SMIv2", RFC 2579, April 1999. 1414 [7] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Conformance 1415 Statements for SMIv2", RFC 2580, April 1999. 1417 [8] Case, J., Fedor, M., Schoffstall, M., and Davin, J., "Simple 1418 Network Management Protocol", RFC 1157, May 1990. 1420 [9] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 1421 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 1423 [10] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport 1424 Mappings for Version 2 of the Simple Network Management Protocol 1425 (SNMPv2)", RFC 1906, January 1996. 1427 [11] Case, J., Harrington D., Presuhn R., and Wijnen, B., "Message 1428 Processing and Dispatching for the Simple Network Management 1429 Protocol (SNMP)", RFC 2572, April 1999. 1431 [12] Blumenthal, U., and Wijnen, B., "User-based Security Model (USM) 1432 for version 3 of the Simple Network Management Protocol (SNMPv3)", 1433 RFC 2574, April 1999. 1435 [13] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 1436 Operations for Version 2 of the Simple Network Management Protocol 1437 (SNMPv2)", RFC 1905, January 1996. 1439 [14] Levi, D., Meyer, P., and Stewart, B., "SNMPv3 Applications", RFC 1440 2573, April 1999. 1442 [15] Wijnen, B., Presuhn, R., and McCloghrie, K., "View-based Access 1443 Control Model (VACM) for the Simple Network Management Protocol 1444 (SNMP)", RFC 2575, April 1999. 1446 [16] Freed, N. and Kille, S., "The Network Services Monitoring MIB", 1447 Internet Draft, May 1999. 1449 [17] Kille, S., "A String Representation of Distinguished Names", RFC 1450 1779, March 1995. 1452 [18] Freed, N. and Kille, S., "Mail Monitoring MIB", RFC 2249, January 1453 1998. 1455 [19] Freed, N. and Kille, S., "Mail Monitoring MIB", RFC 1566, January 1456 1994. 1458 [20] Kille, S., "Mapping between X.400(1988) and RFC 822/MIME", RFC 1459 2156, January 1998. 1461 [21] Crocker, D., "Standard for the Format of ARPA Internet Text 1462 Message", STD 11, RFC 822, August 1982. 1464 [22] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893, 1465 January 1996. 1467 10. Security Considerations 1469 There are no management objects defined in this MIB that have a MAX- 1470 ACCESS clause of read-write and/or read-create. So, if this MIB is 1471 implemented correctly, then there is no risk that an intruder can alter 1472 or create any management objects of this MIB via direct SNMP SET 1473 operations. 1475 However, this MIB does provide passive information about the existence, 1476 type, and configuration of applications on a given host that could 1477 potentially indicate some sort of vulnerability. Finally, the 1478 information MIB provides about network usage could be used to analyze 1479 network traffic patterns. 1481 SNMPv1 by itself is not a secure environment. Even if the network 1482 itself is secure (for example by using IPSec), even then, there is no 1483 control as to who on the secure network is allowed to access and GET/SET 1484 (read/change/create/delete) the objects in this MIB. 1486 It is recommended that the implementers consider the security features 1487 as provided by the SNMPv3 framework. Specifically, the use of the 1488 User-based Security Model RFC 2574 [12] and the View-based Access 1489 Control Model RFC 2575 [15] is recommended. 1491 It is then a customer/user responsibility to ensure that the SNMP entity 1492 giving access to an instance of this MIB, is properly configured to give 1493 access to the objects only to those principals (users) that have 1494 legitimate rights to indeed GET or SET (change/create/delete) them. 1496 11. Author and Chair Addresses 1498 Ned Freed 1499 Innosoft International, Inc. 1500 1050 Lakes Drive 1501 West Covina, CA 91790 1502 USA 1503 tel: +1 626 919 3600 1504 fax: +1 626 919 3614 1505 email: ned.freed@innosoft.com 1507 Steve Kille, MADMAN WG Chair ISODE Consortium The Dome, The Square 1508 Richmond TW9 1DT UK 1509 tel: +44 181 332 9091 1510 email: S.Kille@isode.com 1512 12. Full Copyright Statement 1514 Copyright (C) The Internet Society (1999). All Rights Reserved. 1516 This document and translations of it may be copied and furnished to 1517 others, and derivative works that comment on or otherwise explain it or 1518 assist in its implementation may be prepared, copied, published and 1519 distributed, in whole or in part, without restriction of any kind, 1520 provided that the above copyright notice and this paragraph are included 1521 on all such copies and derivative works. However, this document itself 1522 may not be modified in any way, such as by removing the copyright notice 1523 or references to the Internet Society or other Internet organizations, 1524 except as needed for the purpose of developing Internet standards in 1525 which case the procedures for copyrights defined in the Internet 1526 Standards process must be followed, or as required to translate it into 1527 languages other than English. 1529 The limited permissions granted above are perpetual and will not be 1530 revoked by the Internet Society or its successors or assigns. 1532 This document and the information contained herein is provided on an "AS 1533 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1534 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1535 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1536 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1537 FITNESS FOR A PARTICULAR PURPOSE.