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