idnits 2.17.1 draft-ietf-madman-email-mib-02.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 37 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 9113 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 1448, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 1457, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 1460, but no explicit reference was found in the text == Unused Reference: '22' is defined on line 1463, 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 ..................................... 33 51 8 Acknowledgements ................................................ 34 52 9 References ...................................................... 34 53 10 Security Considerations ........................................ 36 54 11 Author and Chair Addresses ..................................... 37 55 12 Full Copyright Statement ....................................... 37 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 "9905120000Z" 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." 204 REVISION "9708170000Z" 205 DESCRIPTION 206 "This revision, published in RFC 2249, adds the 207 mtaGroupDescription and mtaGroupURL fields, conversion 208 operation counters, a group hierarchy description mechanism, 209 counters for specific errors, oldest message IDs, per-MTA 210 and per-group loop counters, and a new table for tracking 211 any errors an MTA encounters." 212 REVISION "9311280000Z" 213 DESCRIPTION 214 "The original version of this MIB was published in RFC 1566" 215 ::= {mib-2 28} 217 mtaTable OBJECT-TYPE 218 SYNTAX SEQUENCE OF MtaEntry 219 MAX-ACCESS not-accessible 220 STATUS current 221 DESCRIPTION 222 "The table holding information specific to an MTA." 223 ::= {mta 1} 225 mtaStatusCode OBJECT-TYPE 226 SYNTAX INTEGER (4000000..5999999) 227 MAX-ACCESS not-accessible 228 STATUS current 229 DESCRIPTION 230 "An index capable of representing an Enhanced Mail System 231 Status Code. Enhanced Mail System Status Codes are 232 defined in RFC 1893. These codes have the form 234 class.subject.detail 236 Here 'class' is either 2, 4, or 5 and both 'subject' and 237 'detail' are integers in the range 0..999. Given a status 238 code the corresponding index value is defined to be 239 ((class * 1000) + subject) * 1000 + detail. Both SMTP 240 error response codes and X.400 reason and diagnostic codes 241 can be mapped into these codes, resulting in a namespace 242 capable of describing most error conditions a mail system 243 encounters in a generic yet detailed way." 244 ::= {mta 6} 246 mtaEntry OBJECT-TYPE 247 SYNTAX MtaEntry 248 MAX-ACCESS not-accessible 249 STATUS current 250 DESCRIPTION 251 "The entry associated with each MTA." 252 INDEX {applIndex} 253 ::= {mtaTable 1} 255 MtaEntry ::= SEQUENCE { 256 mtaReceivedMessages 257 Counter32, 258 mtaStoredMessages 259 Gauge32, 260 mtaTransmittedMessages 261 Counter32, 262 mtaReceivedVolume 263 Counter32, 264 mtaStoredVolume 265 Gauge32, 266 mtaTransmittedVolume 267 Counter32, 268 mtaReceivedRecipients 269 Counter32, 270 mtaStoredRecipients 271 Gauge32, 272 mtaTransmittedRecipients 273 Counter32, 274 mtaSuccessfulConvertedMessages 275 Counter32, 276 mtaFailedConvertedMessages 277 Counter32, 278 mtaLoopsDetected 279 Counter32 280 } 282 mtaReceivedMessages OBJECT-TYPE 283 SYNTAX Counter32 284 MAX-ACCESS read-only 285 STATUS current 286 DESCRIPTION 287 "The number of messages received since MTA initialization. 288 This includes messages transmitted to this MTA from other 289 MTAs as well as messages that have been submitted to the 290 MTA directly by end-users or applications." 291 ::= {mtaEntry 1} 293 mtaStoredMessages OBJECT-TYPE 294 SYNTAX Gauge32 295 MAX-ACCESS read-only 296 STATUS current 297 DESCRIPTION 298 "The total number of messages currently stored in the MTA. 299 This includes messages that are awaiting transmission to 300 some other MTA or are waiting for delivery to an end-user 301 or application." 302 ::= {mtaEntry 2} 304 mtaTransmittedMessages OBJECT-TYPE 305 SYNTAX Counter32 306 MAX-ACCESS read-only 307 STATUS current 308 DESCRIPTION 309 "The number of messages transmitted since MTA initialization. 310 This includes messages that were transmitted to some other 311 MTA or are waiting for delivery to an end-user or 312 application." 313 ::= {mtaEntry 3} 315 mtaReceivedVolume OBJECT-TYPE 316 SYNTAX Counter32 317 UNITS "K-octets" 318 MAX-ACCESS read-only 319 STATUS current 320 DESCRIPTION 321 "The total volume of messages received since MTA 322 initialization, measured in kilo-octets. This volume should 323 include all transferred data that is logically above the mail 324 transport protocol level. For example, an SMTP-based MTA 325 should use the number of kilo-octets in the message header 326 and body, while an X.400-based MTA should use the number of 327 kilo-octets of P2 data. This includes messages transmitted 328 to this MTA from other MTAs as well as messages that have 329 been submitted to the MTA directly by end-users or 330 applications." 331 ::= {mtaEntry 4} 333 mtaStoredVolume OBJECT-TYPE 334 SYNTAX Gauge32 335 UNITS "K-octets" 336 MAX-ACCESS read-only 337 STATUS current 338 DESCRIPTION 339 "The total volume of messages currently stored in the MTA, 340 measured in kilo-octets. This volume should include all 341 stored data that is logically above the mail transport 342 protocol level. For example, an SMTP-based MTA should 343 use the number of kilo-octets in the message header and 344 body, while an X.400-based MTA would use the number of 345 kilo-octets of P2 data. This includes messages that are 346 awaiting transmission to some other MTA or are waiting 347 for delivery to an end-user or application." 348 ::= {mtaEntry 5} 350 mtaTransmittedVolume OBJECT-TYPE 351 SYNTAX Counter32 352 UNITS "K-octets" 353 MAX-ACCESS read-only 354 STATUS current 355 DESCRIPTION 356 "The total volume of messages transmitted since MTA 357 initialization, measured in kilo-octets. This volume should 358 include all transferred data that is logically above the mail 359 transport protocol level. For example, an SMTP-based MTA 360 should use the number of kilo-octets in the message header 361 and body, while an X.400-based MTA should use the number of 362 kilo-octets of P2 data. This includes messages that were 363 transmitted to some other MTA or are waiting for delivery 364 to an end-user or application." 365 ::= {mtaEntry 6} 367 mtaReceivedRecipients OBJECT-TYPE 368 SYNTAX Counter32 369 MAX-ACCESS read-only 370 STATUS current 371 DESCRIPTION 372 "The total number of recipients specified in all messages 373 received since MTA initialization. Recipients this MTA 374 has no responsibility for, i.e. inactive envelope 375 recipients or ones referred to in message headers, 376 should not be counted even if information about such 377 recipients is available. This includes messages 378 transmitted to this MTA from other MTAs as well as 379 messages that have been submitted to the MTA directly 380 by end-users or applications." 381 ::= {mtaEntry 7} 383 mtaStoredRecipients OBJECT-TYPE 384 SYNTAX Gauge32 385 MAX-ACCESS read-only 386 STATUS current 387 DESCRIPTION 388 "The total number of recipients specified in all messages 389 currently stored in the MTA. Recipients this MTA has no 390 responsibility for, i.e. inactive envelope recipients or 391 ones referred to in message headers, should not be 392 counted. This includes messages that are awaiting 393 transmission to some other MTA or are waiting for 394 delivery to an end-user or application." 395 ::= {mtaEntry 8} 397 mtaTransmittedRecipients OBJECT-TYPE 398 SYNTAX Counter32 399 MAX-ACCESS read-only 400 STATUS current 401 DESCRIPTION 402 "The total number of recipients specified in all messages 403 transmitted since MTA initialization. Recipients this 404 MTA had no responsibility for, i.e. inactive envelope 405 recipients or ones referred to in message headers, 406 should not be counted. This includes messages that were 407 transmitted to some other MTA or are waiting for 408 delivery to an end-user or application." 409 ::= {mtaEntry 9} 411 mtaSuccessfulConvertedMessages OBJECT-TYPE 412 SYNTAX Counter32 413 MAX-ACCESS read-only 414 STATUS current 415 DESCRIPTION 416 "The number of messages that have been successfully 417 converted from one form to another since MTA 418 initialization." 419 ::= {mtaEntry 10} 421 mtaFailedConvertedMessages OBJECT-TYPE 422 SYNTAX Counter32 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "The number of messages for which an unsuccessful 427 attempt was made to convert them from one form to 428 another since MTA initialization." 429 ::= {mtaEntry 11} 431 mtaLoopsDetected OBJECT-TYPE 432 SYNTAX Counter32 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "A message loop is defined as a situation where the MTA 437 decides that a given message will never be delivered to 438 one or more recipients and instead will continue to 439 loop endlessly through one or more MTAs. This variable 440 counts the number of times the MTA has detected such a 441 situation since MTA initialization. Note that the 442 mechanism MTAs use to detect loops (e.g., trace field 443 counting, count of references to this MTA in a trace 444 field, examination of DNS or other directory information, 445 etc.), the level at which loops are detected (e.g., per 446 message, per recipient, per directory entry, etc.), and 447 the handling of a loop once it is detected (e.g., looping 448 messages are held, looping messages are bounced or sent 449 to the postmaster, messages that the MTA knows will loop 450 won't be accepted, etc.) vary widely from one MTA to the 451 next and cannot be inferred from this variable." 452 ::= {mtaEntry 12} 454 -- MTAs typically group inbound reception, queue storage, and 455 -- outbound transmission in some way, rather than accounting for 456 -- such operations only across the MTA as a whole. In the most 457 -- extreme case separate information will be maintained for each 458 -- different entity that receives messages and for each entity 459 -- the MTA stores messages for and delivers messages to. Other 460 -- MTAs may elect to treat all reception equally, all queue 461 -- storage equally, all deliveries equally, or some combination 462 -- of this. Overlapped groupings are also possible, where an MTA 463 -- decomposes its traffic in different ways for different 464 -- purposes. 466 -- In any case, a grouping abstraction is an extremely useful for 467 -- breaking down the activities of an MTA. For purposes of 468 -- labelling this will be called a "group" in this MIB. 470 -- Each group contains all the variables needed to monitor all 471 -- aspects of an MTA's operation. However, the fact that all 472 -- groups contain all possible variables does not imply that all 473 -- groups must use all possible variables. For example, a single 474 -- group might be used to monitor only one kind of event (inbound 475 -- processing, outbound processing, or storage). In this sort of 476 -- configuration any counters that are unused as a result of a 477 -- given MTA's use of the group construct must be inaccessible; 478 -- e.g., returning either a noSuchName error (for an SNMPv1 get), 479 -- or a noSuchInstance exception (for an SNMPv2 get). 481 -- Groups can be created at any time after MTA initialization. Once 482 -- a group is created it should not be deleted or its mtaGroupIndex 483 -- changed unless the MTA is reinitialized. 485 -- Groups are not necessarily mutually exclusive. A given event may 486 -- be recorded by more than one group, a message may be seen as 487 -- stored by more than one group, and so on. Groups should be all 488 -- inclusive, however: if groups are implemented all aspects of an 489 -- MTA's operation should be registered in at least one group. 490 -- This freedom lets implementors use different sets of groups to 491 -- provide different "views" of an MTA. 493 -- The possibility of overlap between groups means that summing 494 -- variables across groups may not produce values equal to those in 495 -- the mtaTable. mtaTable should always provide accurate information 496 -- about the MTA as a whole. 498 -- The term "channel" is often used in MTA implementations; channels 499 -- are usually, but not always, equivalent to a group. However, 500 -- this MIB does not use the term "channel" because there is no 501 -- requirement that an MTA supporting this MIB has to map its 502 -- "channel" abstraction one-to-one onto the MIB's group abstraction. 504 -- An MTA may create a group or group of groups at any time. Once 505 -- created, however, an MTA cannot delete an entry for a group from 506 -- the group table. Deletion is only allowed when the MTA is 507 -- reinitialized, and is not required even then. This restriction 508 -- is imposed so that monitoring agents can rely on group 509 -- assignments being consistent across multiple query operations. 511 -- Groups may be laid out so as to form a hierarchical arrangement, 512 -- with some groups acting as subgroups for other groups. 513 -- Alternately, disjoint groups of groups may be used to provide 514 -- different sorts of "snapshots" of MTA operation. The 515 -- mtaGroupHierarchy variable provides an indication of how each 516 -- group fits into the overall arrangement being used. 518 -- Note that SNMP also defines and uses term "group". MTA groups are 519 -- NOT the same as SNMP groups. 521 mtaGroupTable OBJECT-TYPE 522 SYNTAX SEQUENCE OF MtaGroupEntry 523 MAX-ACCESS not-accessible 524 STATUS current 525 DESCRIPTION 526 "The table holding information specific to each MTA group." 527 ::= {mta 2} 529 mtaGroupEntry OBJECT-TYPE 530 SYNTAX MtaGroupEntry 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "The entry associated with each MTA group." 535 INDEX {applIndex, mtaGroupIndex} 536 ::= {mtaGroupTable 1} 538 MtaGroupEntry ::= SEQUENCE { 539 mtaGroupIndex 540 INTEGER, 541 mtaGroupReceivedMessages 542 Counter32, 543 mtaGroupRejectedMessages 544 Counter32, 545 mtaGroupStoredMessages 546 Gauge32, 547 mtaGroupTransmittedMessages 548 Counter32, 549 mtaGroupReceivedVolume 550 Counter32, 551 mtaGroupStoredVolume 552 Gauge32, 553 mtaGroupTransmittedVolume 554 Counter32, 555 mtaGroupReceivedRecipients 556 Counter32, 557 mtaGroupStoredRecipients 558 Gauge32, 559 mtaGroupTransmittedRecipients 560 Counter32, 561 mtaGroupOldestMessageStored 562 TimeInterval, 563 mtaGroupInboundAssociations 564 Gauge32, 565 mtaGroupOutboundAssociations 566 Gauge32, 567 mtaGroupAccumulatedInboundAssociations 568 Counter32, 569 mtaGroupAccumulatedOutboundAssociations 570 Counter32, 571 mtaGroupLastInboundActivity 572 TimeInterval, 573 mtaGroupLastOutboundActivity 574 TimeInterval, 575 mtaGroupLastOutboundAssociationAttempt 576 TimeInterval, 577 mtaGroupRejectedInboundAssociations 578 Counter32, 579 mtaGroupFailedOutboundAssociations 580 Counter32, 581 mtaGroupInboundRejectionReason 582 DisplayString, 584 mtaGroupOutboundConnectFailureReason 585 DisplayString, 586 mtaGroupScheduledRetry 587 TimeInterval, 588 mtaGroupMailProtocol 589 OBJECT IDENTIFIER, 590 mtaGroupName 591 DisplayString, 592 mtaGroupSuccessfulConvertedMessages 593 Counter32, 594 mtaGroupFailedConvertedMessages 595 Counter32, 596 mtaGroupDescription 597 DisplayString, 598 mtaGroupURL 599 URLString, 600 mtaGroupCreationTime 601 TimeInterval, 602 mtaGroupHierarchy 603 INTEGER, 604 mtaGroupOldestMessageId 605 DisplayString, 606 mtaGroupLoopsDetected 607 Counter32 608 } 610 mtaGroupIndex OBJECT-TYPE 611 SYNTAX INTEGER (1..2147483647) 612 MAX-ACCESS not-accessible 613 STATUS current 614 DESCRIPTION 615 "The index associated with a group for a given MTA." 616 ::= {mtaGroupEntry 1} 618 mtaGroupReceivedMessages OBJECT-TYPE 619 SYNTAX Counter32 620 MAX-ACCESS read-only 621 STATUS current 622 DESCRIPTION 623 "The number of messages received to this group since 624 group creation." 625 ::= {mtaGroupEntry 2} 627 mtaGroupRejectedMessages OBJECT-TYPE 628 SYNTAX Counter32 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "The number of messages rejected by this group since 633 group creation." 634 ::= {mtaGroupEntry 3} 636 mtaGroupStoredMessages OBJECT-TYPE 637 SYNTAX Gauge32 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "The total number of messages currently stored in this 642 group's queue." 643 ::= {mtaGroupEntry 4} 645 mtaGroupTransmittedMessages OBJECT-TYPE 646 SYNTAX Counter32 647 MAX-ACCESS read-only 648 STATUS current 649 DESCRIPTION 650 "The number of messages transmitted by this group since 651 group creation." 652 ::= {mtaGroupEntry 5} 654 mtaGroupReceivedVolume OBJECT-TYPE 655 SYNTAX Counter32 656 UNITS "K-octets" 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "The total volume of messages received to this group since 661 group creation, measured in kilo-octets. This volume 662 should include all transferred data that is logically above 663 the mail transport protocol level. For example, an 664 SMTP-based MTA should use the number of kilo-octets in the 665 message header and body, while an X.400-based MTA should use 666 the number of kilo-octets of P2 data." 667 ::= {mtaGroupEntry 6} 669 mtaGroupStoredVolume OBJECT-TYPE 670 SYNTAX Gauge32 671 UNITS "K-octets" 672 MAX-ACCESS read-only 673 STATUS current 674 DESCRIPTION 675 "The total volume of messages currently stored in this 676 group's queue, measured in kilo-octets. This volume should 677 include all stored data that is logically above the mail 678 transport protocol level. For example, an SMTP-based 679 MTA should use the number of kilo-octets in the message 680 header and body, while an X.400-based MTA would use the 681 number of kilo-octets of P2 data." 682 ::= {mtaGroupEntry 7} 684 mtaGroupTransmittedVolume OBJECT-TYPE 685 SYNTAX Counter32 686 UNITS "K-octets" 687 MAX-ACCESS read-only 688 STATUS current 689 DESCRIPTION 690 "The total volume of messages transmitted by this group 691 since group creation, measured in kilo-octets. This 692 volume should include all transferred data that is logically 693 above the mail transport protocol level. For example, an 694 SMTP-based MTA should use the number of kilo-octets in the 695 message header and body, while an X.400-based MTA should use 696 the number of kilo-octets of P2 data." 697 ::= {mtaGroupEntry 8} 699 mtaGroupReceivedRecipients 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 received to this group since group creation. 706 Recipients this MTA has no responsibility for should not 707 be counted." 708 ::= {mtaGroupEntry 9} 710 mtaGroupStoredRecipients OBJECT-TYPE 711 SYNTAX Gauge32 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "The total number of recipients specified in all messages 716 currently stored in this group's queue. Recipients this 717 MTA has no responsibility for should not be counted." 718 ::= {mtaGroupEntry 10} 720 mtaGroupTransmittedRecipients OBJECT-TYPE 721 SYNTAX Counter32 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 "The total number of recipients specified in all messages 726 transmitted by this group since group creation. 727 Recipients this MTA had no responsibility for should not 728 be counted." 729 ::= {mtaGroupEntry 11} 731 mtaGroupOldestMessageStored OBJECT-TYPE 732 SYNTAX TimeInterval 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "Time since the oldest message in this group's queue was 737 placed in the queue." 738 ::= {mtaGroupEntry 12} 740 mtaGroupInboundAssociations OBJECT-TYPE 741 SYNTAX Gauge32 742 MAX-ACCESS read-only 743 STATUS current 744 DESCRIPTION 745 "The number of current associations to the group, where the 746 group is the responder." 747 ::= {mtaGroupEntry 13} 749 mtaGroupOutboundAssociations OBJECT-TYPE 750 SYNTAX Gauge32 751 MAX-ACCESS read-only 752 STATUS current 753 DESCRIPTION 754 "The number of current associations to the group, where the 755 group is the initiator." 756 ::= {mtaGroupEntry 14} 758 mtaGroupAccumulatedInboundAssociations OBJECT-TYPE 759 SYNTAX Counter32 760 MAX-ACCESS read-only 761 STATUS current 762 DESCRIPTION 763 "The total number of associations to the group since 764 group creation, where the MTA was the responder." 765 ::= {mtaGroupEntry 15} 767 mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE 768 SYNTAX Counter32 769 MAX-ACCESS read-only 770 STATUS current 771 DESCRIPTION 772 "The total number of associations from the group since 773 group creation, where the MTA was the initiator." 774 ::= {mtaGroupEntry 16} 776 mtaGroupLastInboundActivity OBJECT-TYPE 777 SYNTAX TimeInterval 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION 781 "Time since the last time that this group had an active 782 inbound association for purposes of message reception." 783 ::= {mtaGroupEntry 17} 785 mtaGroupLastOutboundActivity OBJECT-TYPE 786 SYNTAX TimeInterval 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "Time since the last time that this group had a 791 successful outbound association for purposes of 792 message delivery." 793 ::= {mtaGroupEntry 18} 795 mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE 796 SYNTAX TimeInterval 797 MAX-ACCESS read-only 798 STATUS current 799 DESCRIPTION 800 "Time since the last time that this group attempted 801 to make an outbound association for purposes of 802 message delivery." 803 ::= {mtaGroupEntry 34} 805 mtaGroupRejectedInboundAssociations OBJECT-TYPE 806 SYNTAX Counter32 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "The total number of inbound associations the group has 811 rejected, since group creation. Rejected associations 812 are not counted in the accumulated association totals." 813 ::= {mtaGroupEntry 19} 815 mtaGroupFailedOutboundAssociations OBJECT-TYPE 816 SYNTAX Counter32 817 MAX-ACCESS read-only 818 STATUS current 819 DESCRIPTION 820 "The total number associations where the group was the 821 initiator and association establishment has failed, 822 since group creation. Failed associations are 823 not counted in the accumulated association totals." 824 ::= {mtaGroupEntry 20} 826 mtaGroupInboundRejectionReason OBJECT-TYPE 827 SYNTAX DisplayString 828 MAX-ACCESS read-only 829 STATUS current 830 DESCRIPTION 831 "The failure reason, if any, for the last association this 832 group refused to respond to. If no association attempt 833 has been made since the MTA was initialized the value 834 should be 'never'." 835 ::= {mtaGroupEntry 21} 837 mtaGroupOutboundConnectFailureReason OBJECT-TYPE 838 SYNTAX DisplayString 839 MAX-ACCESS read-only 840 STATUS current 841 DESCRIPTION 842 "The failure reason, if any, for the last association attempt 843 this group initiated. If no association attempt has been 844 made since the MTA was initialized the value should be 845 'never'." 846 ::= {mtaGroupEntry 22} 848 mtaGroupScheduledRetry OBJECT-TYPE 849 SYNTAX TimeInterval 850 MAX-ACCESS read-only 851 STATUS current 852 DESCRIPTION 853 "The amount of time until this group is next scheduled to 854 attempt to make an association." 855 ::= {mtaGroupEntry 23} 857 mtaGroupMailProtocol OBJECT-TYPE 858 SYNTAX OBJECT IDENTIFIER 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "An identification of the protocol being used by this group. 863 For an group employing OSI protocols, this will be the 864 Application Context. For Internet applications, the IANA 865 maintains a registry of the OIDs which correspond to well-known 866 message transfer protocols. If the application protocol is 867 not listed in the registry, an OID value of the form 868 {applTCPProtoID port} or {applUDProtoID port} are used for 869 TCP-based and UDP-based protocols, respectively. In either 870 case 'port' corresponds to the primary port number being 871 used by the group. applTCPProtoID and applUDPProtoID are 872 defined in the NETWORK-SERVICES-MIB, RFC XXXX." 873 ::= {mtaGroupEntry 24} 875 mtaGroupName OBJECT-TYPE 876 SYNTAX DisplayString 877 MAX-ACCESS read-only 878 STATUS current 879 DESCRIPTION 880 "A descriptive name for the group. If this group connects to 881 a single remote MTA this should be the name of that MTA. If 882 this in turn is an Internet MTA this should be the domain 883 name. For an OSI MTA it should be the string encoded 884 distinguished name of the managed object using the format 885 defined in RFC 1779. For X.400(1984) MTAs which do not 886 have a Distinguished Name, the RFC 2156 syntax 887 'mta in globalid' used in X400-Received: fields can be 888 used." 889 ::= {mtaGroupEntry 25} 891 mtaGroupSuccessfulConvertedMessages OBJECT-TYPE 892 SYNTAX Counter32 893 MAX-ACCESS read-only 894 STATUS current 895 DESCRIPTION 896 "The number of messages that have been successfully 897 converted from one form to another in this group 898 since group creation." 899 ::= {mtaGroupEntry 26} 901 mtaGroupFailedConvertedMessages OBJECT-TYPE 902 SYNTAX Counter32 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "The number of messages for which an unsuccessful 907 attempt was made to convert them from one form to 908 another in this group since group creation." 909 ::= {mtaGroupEntry 27} 911 mtaGroupDescription OBJECT-TYPE 912 SYNTAX DisplayString 913 MAX-ACCESS read-only 914 STATUS current 915 DESCRIPTION 916 "A description of the group's purpose. This information is 917 intended to identify the group in a status display." 918 ::= {mtaGroupEntry 28} 920 mtaGroupURL OBJECT-TYPE 921 SYNTAX URLString 922 MAX-ACCESS read-only 923 STATUS current 924 DESCRIPTION 925 "A URL pointing to a description of the group. This 926 information is intended to identify and briefly describe 927 the group in a status display." 928 ::= {mtaGroupEntry 29} 930 mtaGroupCreationTime OBJECT-TYPE 931 SYNTAX TimeInterval 932 MAX-ACCESS read-only 933 STATUS current 934 DESCRIPTION 935 "Time since this group was first created." 936 ::= {mtaGroupEntry 30} 938 mtaGroupHierarchy OBJECT-TYPE 939 SYNTAX INTEGER (-2147483648..2147483647) 940 MAX-ACCESS read-only 941 STATUS current 942 DESCRIPTION 943 "Describes how this group fits into the hierarchy. A 944 positive value is interpreted as an mtaGroupIndex 945 value for some other group whose variables include 946 those of this group (and usually others). A negative 947 value is interpreted as a group collection code: Groups 948 with common negative hierarchy values comprise one 949 particular breakdown of MTA activity as a whole. A 950 zero value means that this MIB implementation doesn't 951 implement hierarchy indicators and thus the overall 952 group hierarchy cannot be determined." 953 ::= {mtaGroupEntry 31} 955 mtaGroupOldestMessageId OBJECT-TYPE 956 SYNTAX DisplayString 957 MAX-ACCESS read-only 958 STATUS current 959 DESCRIPTION 960 "Message ID of the oldest message in the group's queue. 961 Whenever possible this should be in the form of an 962 RFC 822 msg-id; X.400 may convert X.400 message 963 identifiers to this form by following the rules laid 964 out in RFC2156." 965 ::= {mtaGroupEntry 32} 967 mtaGroupLoopsDetected OBJECT-TYPE 968 SYNTAX Counter32 969 MAX-ACCESS read-only 970 STATUS current 971 DESCRIPTION 972 "A message loop is defined as a situation where the MTA 973 decides that a given message will never be delivered to 974 one or more recipients and instead will continue to 975 loop endlessly through one or more MTAs. This variable 976 counts the number of times the MTA has detected such a 977 situation in conjunction with something associated with 978 this group since group creation. Note that the 979 mechanism MTAs use to detect loops (e.g., trace field 980 counting, count of references to this MTA in a trace 981 field, examination of DNS or other directory information, 982 etc.), the level at which loops are detected (e.g., per 983 message, per recipient, per directory entry, etc.), and 984 the handling of a loop once it is detected (e.g., looping 985 messages are held, looping messages are bounced or sent 986 to the postmaster, messages that the MTA knows will loop 987 won't be accepted, etc.) vary widely from one MTA to the 988 next and cannot be inferred from this variable." 989 ::= {mtaGroupEntry 33} 991 -- The mtaGroupAssociationTable provides a means of correlating 992 -- entries in the network services association table with the 993 -- MTA group responsible for the association. 995 mtaGroupAssociationTable OBJECT-TYPE 996 SYNTAX SEQUENCE OF MtaGroupAssociationEntry 997 MAX-ACCESS not-accessible 998 STATUS current 999 DESCRIPTION 1000 "The table holding information regarding the associations 1001 for each MTA group." 1002 ::= {mta 3} 1004 mtaGroupAssociationEntry OBJECT-TYPE 1005 SYNTAX MtaGroupAssociationEntry 1006 MAX-ACCESS not-accessible 1007 STATUS current 1008 DESCRIPTION 1009 "The entry holding information regarding the associations 1010 for each MTA group." 1011 INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex} 1012 ::= {mtaGroupAssociationTable 1} 1014 MtaGroupAssociationEntry ::= SEQUENCE { 1015 mtaGroupAssociationIndex 1016 INTEGER 1017 } 1019 mtaGroupAssociationIndex OBJECT-TYPE 1020 SYNTAX INTEGER (1..2147483647) 1021 MAX-ACCESS read-only 1022 STATUS current 1023 DESCRIPTION 1024 "Reference into association table to allow correlation of 1025 this group's active associations with the association table." 1026 ::= {mtaGroupAssociationEntry 1} 1028 -- The mtaGroupErrorTable gives each group a way of tallying 1029 -- the specific errors it has encountered. The mechanism 1030 -- defined here uses RFC 1893 status codes to identify 1031 -- various specific errors. There are also classes for generic 1032 -- errors of various sorts, and the entire mechanism is also 1033 -- extensible, in that new error codes can be defined at any 1034 -- time. 1036 mtaGroupErrorTable OBJECT-TYPE 1037 SYNTAX SEQUENCE OF MtaGroupErrorEntry 1038 MAX-ACCESS not-accessible 1039 STATUS current 1040 DESCRIPTION 1041 "The table holding information regarding accumulated errors 1042 for each MTA group." 1043 ::= {mta 5} 1045 mtaGroupErrorEntry OBJECT-TYPE 1046 SYNTAX MtaGroupErrorEntry 1047 MAX-ACCESS not-accessible 1048 STATUS current 1049 DESCRIPTION 1050 "The entry holding information regarding accumulated 1051 errors for each MTA group." 1052 INDEX {applIndex, mtaGroupIndex, mtaStatusCode} 1053 ::= {mtaGroupErrorTable 1} 1055 MtaGroupErrorEntry ::= SEQUENCE { 1056 mtaStatusCode 1057 INTEGER (4000000..5999999), 1058 mtaGroupInboundErrorCount 1059 Counter32, 1060 mtaGroupInternalErrorCount 1061 Counter32, 1062 mtaGroupOutboundErrorCount 1063 Counter32 1064 } 1066 mtaGroupInboundErrorCount OBJECT-TYPE 1067 SYNTAX Counter32 1068 MAX-ACCESS read-only 1069 STATUS current 1070 DESCRIPTION 1071 "Count of the number of errors of a given type that have 1072 been accumulated in association with a particular group 1073 while processing incoming messages. In the case of SMTP 1074 these will typically be errors reporting by an SMTP 1075 server to the remote client; in the case of X.400 1076 these will typically be errors encountered while 1077 processing an incoming message." 1078 ::= {mtaGroupErrorEntry 1} 1080 mtaGroupInternalErrorCount OBJECT-TYPE 1081 SYNTAX Counter32 1082 MAX-ACCESS read-only 1083 STATUS current 1084 DESCRIPTION 1085 "Count of the number of errors of a given type that have 1086 been accumulated in association with a particular group 1087 during internal MTA processing." 1088 ::= {mtaGroupErrorEntry 2} 1090 mtaGroupOutboundErrorCount OBJECT-TYPE 1091 SYNTAX Counter32 1092 MAX-ACCESS read-only 1093 STATUS current 1094 DESCRIPTION 1095 "Count of the number of errors of a given type that have 1096 been accumulated in association with a particular group's 1097 outbound connection activities. In the case of an SMTP 1098 client these will typically be errors reported while 1099 attempting to contact or while communicating with the 1100 remote SMTP server. In the case of X.400 these will 1101 typically be errors encountered while constructing 1102 or attempting to deliver an outgoing message." 1103 ::= {mtaGroupErrorEntry 3} 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, and 1377 (3) the recommendation that an empty string be returned if the last 1378 operation was successful has been removed from 1379 mtaGroupInboundRejectionReason and 1380 mtaGroupOutboundConnectFailureReason as it conflicts with the 1381 stated purpose of these variables. 1383 8. Acknowledgements 1385 This document is a work product of the Mail and Directory Management 1386 (MADMAN) Working Group of the IETF. It is based on an earlier MIB 1387 designed by S. Kille, T. Lenggenhager, D. Partain, and W. Yeong. The 1388 Electronic Mail Association's TSC committee was instrumental in 1389 providing feedback on and suggesting enhancements to RFC 1566 [19] that 1390 have led to the present document. 1392 9. References 1394 [1] Harrington, D., Presuhn, R., and Wijnen, B., "An Architecture for 1395 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1397 [2] Rose, M. and McCloghrie, K., "Structure and Identification of 1398 Management Information for TCP/IP-based Internets", RFC 1155, May 1399 1990. 1401 [3] Rose, M. and McCloghrie, K., "Concise MIB Definitions", RFC 1212, 1402 March 1991. 1404 [4] Rose, M., "A Convention for Defining Traps for use with the SNMP", 1405 RFC 1215, March 1991. 1407 [5] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Structure of 1408 Management Information Version 2 (SMIv2)", RFC 2578, April 1999. 1410 [6] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Textual 1411 Conventions for SMIv2", RFC 2579, April 1999. 1413 [7] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Conformance 1414 Statements for SMIv2", RFC 2580, April 1999. 1416 [8] Case, J., Fedor, M., Schoffstall, M., and Davin, J., "Simple 1417 Network Management Protocol", RFC 1157, May 1990. 1419 [9] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 1420 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 1422 [10] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport 1423 Mappings for Version 2 of the Simple Network Management Protocol 1424 (SNMPv2)", RFC 1906, January 1996. 1426 [11] Case, J., Harrington D., Presuhn R., and Wijnen, B., "Message 1427 Processing and Dispatching for the Simple Network Management 1428 Protocol (SNMP)", RFC 2572, April 1999. 1430 [12] Blumenthal, U., and Wijnen, B., "User-based Security Model (USM) 1431 for version 3 of the Simple Network Management Protocol (SNMPv3)", 1432 RFC 2574, April 1999. 1434 [13] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 1435 Operations for Version 2 of the Simple Network Management Protocol 1436 (SNMPv2)", RFC 1905, January 1996. 1438 [14] Levi, D., Meyer, P., and Stewart, B., "SNMPv3 Applications", RFC 1439 2573, April 1999. 1441 [15] Wijnen, B., Presuhn, R., and McCloghrie, K., "View-based Access 1442 Control Model (VACM) for the Simple Network Management Protocol 1443 (SNMP)", RFC 2575, April 1999. 1445 [16] Freed, N. and Kille, S., "The Network Services Monitoring MIB", 1446 Internet Draft, May 1999. 1448 [17] Kille, S., "A String Representation of Distinguished Names", RFC 1449 1779, March 1995. 1451 [18] Freed, N. and Kille, S., "Mail Monitoring MIB", RFC 2249, January 1452 1998. 1454 [19] Freed, N. and Kille, S., "Mail Monitoring MIB", RFC 1566, January 1455 1994. 1457 [20] Kille, S., "Mapping between X.400(1988) and RFC 822/MIME", RFC 1458 2156, January 1998. 1460 [21] Crocker, D., "Standard for the Format of ARPA Internet Text 1461 Message", STD 11, RFC 822, August 1982. 1463 [22] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893, 1464 January 1996. 1466 10. Security Considerations 1468 There are no management objects defined in this MIB that have a MAX- 1469 ACCESS clause of read-write and/or read-create. So, if this MIB is 1470 implemented correctly, then there is no risk that an intruder can alter 1471 or create any management objects of this MIB via direct SNMP SET 1472 operations. 1474 However, this MIB does provide passive information about the existence, 1475 type, and configuration of applications on a given host that could 1476 potentially indicate some sort of vulnerability. Finally, the 1477 information MIB provides about network usage could be used to analyze 1478 network traffic patterns. 1480 SNMPv1 by itself is not a secure environment. Even if the network 1481 itself is secure (for example by using IPSec), even then, there is no 1482 control as to who on the secure network is allowed to access and GET/SET 1483 (read/change/create/delete) the objects in this MIB. 1485 It is recommended that the implementers consider the security features 1486 as provided by the SNMPv3 framework. Specifically, the use of the 1487 User-based Security Model RFC 2574 [12] and the View-based Access 1488 Control Model RFC 2575 [15] is recommended. 1490 It is then a customer/user responsibility to ensure that the SNMP entity 1491 giving access to an instance of this MIB, is properly configured to give 1492 access to the objects only to those principals (users) that have 1493 legitimate rights to indeed GET or SET (change/create/delete) them. 1495 11. Author and Chair Addresses 1497 Ned Freed 1498 Innosoft International, Inc. 1499 1050 Lakes Drive 1500 West Covina, CA 91790 1501 USA 1502 tel: +1 626 919 3600 1503 fax: +1 626 919 3614 1504 email: ned.freed@innosoft.com 1506 Steve Kille, MADMAN WG Chair 1507 ISODE Consortium 1508 The Dome, The Square 1509 Richmond TW9 1DT 1510 UK 1511 tel: +44 181 332 9091 1512 email: S.Kille@isode.com 1514 12. Full Copyright Statement 1516 Copyright (C) The Internet Society (1999). All Rights Reserved. 1518 This document and translations of it may be copied and furnished to 1519 others, and derivative works that comment on or otherwise explain it or 1520 assist in its implementation may be prepared, copied, published and 1521 distributed, in whole or in part, without restriction of any kind, 1522 provided that the above copyright notice and this paragraph are included 1523 on all such copies and derivative works. However, this document itself 1524 may not be modified in any way, such as by removing the copyright notice 1525 or references to the Internet Society or other Internet organizations, 1526 except as needed for the purpose of developing Internet standards in 1527 which case the procedures for copyrights defined in the Internet 1528 Standards process must be followed, or as required to translate it into 1529 languages other than English. 1531 The limited permissions granted above are perpetual and will not be 1532 revoked by the Internet Society or its successors or assigns. 1534 This document and the information contained herein is provided on an "AS 1535 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1536 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1537 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1538 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1539 FITNESS FOR A PARTICULAR PURPOSE.