idnits 2.17.1 draft-ietf-madman-email-mib-04.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 37 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 38 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. -- The draft header indicates that this document obsoletes RFC1566, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document obsoletes RFC2249, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 1999) is 8892 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 1462, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 1471, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 1474, but no explicit reference was found in the text == Unused Reference: '22' is defined on line 1477, 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 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 "9912010000Z" 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 "9912010000Z" 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. Howevr, 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." 202 REVISION "9905120000Z" 203 DESCRIPTION 204 "This revision fixes a number of technical problems found in 205 previous versions: The conformance groups for different 206 versions of this MIB have been corrected, the recommendation 207 that an empty string be returned if the last operation was 208 successful has been removed from 209 mtaGroupInboundRejectionReason and 210 mtaGroupOutboundConnectFailureReason as it conflicts 211 with the stated purpose of these variables, and the 212 required mtaStatusCode entry has been added to 213 MtaGroupErrorEntry. It should be noted that this last 214 change in no way affects the bits on the wire." 215 REVISION "9708170000Z" 216 DESCRIPTION 217 "This revision, published in RFC 2249, adds the 218 mtaGroupDescription and mtaGroupURL fields, conversion 219 operation counters, a group hierarchy description mechanism, 220 counters for specific errors, oldest message IDs, per-MTA 221 and per-group loop counters, and a new table for tracking 222 any errors an MTA encounters." 223 REVISION "9311280000Z" 224 DESCRIPTION 225 "The original version of this MIB was published in RFC 1566" 226 ::= {mib-2 28} 228 mtaTable OBJECT-TYPE 229 SYNTAX SEQUENCE OF MtaEntry 230 MAX-ACCESS not-accessible 231 STATUS current 232 DESCRIPTION 233 "The table holding information specific to an MTA." 234 ::= {mta 1} 236 mtaEntry OBJECT-TYPE 237 SYNTAX MtaEntry 238 MAX-ACCESS not-accessible 239 STATUS current 240 DESCRIPTION 241 "The entry associated with each MTA." 242 INDEX {applIndex} 243 ::= {mtaTable 1} 245 MtaEntry ::= SEQUENCE { 246 mtaReceivedMessages 247 Counter32, 248 mtaStoredMessages 249 Gauge32, 250 mtaTransmittedMessages 251 Counter32, 252 mtaReceivedVolume 253 Counter32, 254 mtaStoredVolume 255 Gauge32, 256 mtaTransmittedVolume 257 Counter32, 258 mtaReceivedRecipients 259 Counter32, 260 mtaStoredRecipients 261 Gauge32, 262 mtaTransmittedRecipients 263 Counter32, 264 mtaSuccessfulConvertedMessages 265 Counter32, 266 mtaFailedConvertedMessages 267 Counter32, 268 mtaLoopsDetected 269 Counter32 270 } 272 mtaReceivedMessages OBJECT-TYPE 273 SYNTAX Counter32 274 MAX-ACCESS read-only 275 STATUS current 276 DESCRIPTION 277 "The number of messages received since MTA initialization. 278 This includes messages transmitted to this MTA from other 279 MTAs as well as messages that have been submitted to the 280 MTA directly by end-users or applications." 281 ::= {mtaEntry 1} 283 mtaStoredMessages OBJECT-TYPE 284 SYNTAX Gauge32 285 MAX-ACCESS read-only 286 STATUS current 287 DESCRIPTION 288 "The total number of messages currently stored in the MTA. 289 This includes messages that are awaiting transmission to 290 some other MTA or are waiting for delivery to an end-user 291 or application." 292 ::= {mtaEntry 2} 294 mtaTransmittedMessages OBJECT-TYPE 295 SYNTAX Counter32 296 MAX-ACCESS read-only 297 STATUS current 298 DESCRIPTION 299 "The number of messages transmitted since MTA initialization. 300 This includes messages that were transmitted to some other 301 MTA or are waiting for delivery to an end-user or 302 application." 303 ::= {mtaEntry 3} 305 mtaReceivedVolume OBJECT-TYPE 306 SYNTAX Counter32 307 UNITS "K-octets" 308 MAX-ACCESS read-only 309 STATUS current 310 DESCRIPTION 311 "The total volume of messages received since MTA 312 initialization, measured in kilo-octets. This volume should 313 include all transferred data that is logically above the mail 314 transport protocol level. For example, an SMTP-based MTA 315 should use the number of kilo-octets in the message header 316 and body, while an X.400-based MTA should use the number of 317 kilo-octets of P2 data. This includes messages transmitted 318 to this MTA from other MTAs as well as messages that have 319 been submitted to the MTA directly by end-users or 320 applications." 321 ::= {mtaEntry 4} 323 mtaStoredVolume OBJECT-TYPE 324 SYNTAX Gauge32 325 UNITS "K-octets" 326 MAX-ACCESS read-only 327 STATUS current 328 DESCRIPTION 329 "The total volume of messages currently stored in the MTA, 330 measured in kilo-octets. This volume should include all 331 stored data that is logically above the mail transport 332 protocol level. For example, an SMTP-based MTA should 333 use the number of kilo-octets in the message header and 334 body, while an X.400-based MTA would use the number of 335 kilo-octets of P2 data. This includes messages that are 336 awaiting transmission to some other MTA or are waiting 337 for delivery to an end-user or application." 338 ::= {mtaEntry 5} 340 mtaTransmittedVolume OBJECT-TYPE 341 SYNTAX Counter32 342 UNITS "K-octets" 343 MAX-ACCESS read-only 344 STATUS current 345 DESCRIPTION 346 "The total volume of messages transmitted since MTA 347 initialization, measured in kilo-octets. This volume should 348 include all transferred data that is logically above the mail 349 transport protocol level. For example, an SMTP-based MTA 350 should use the number of kilo-octets in the message header 351 and body, while an X.400-based MTA should use the number of 352 kilo-octets of P2 data. This includes messages that were 353 transmitted to some other MTA or are waiting for delivery 354 to an end-user or application." 355 ::= {mtaEntry 6} 357 mtaReceivedRecipients OBJECT-TYPE 358 SYNTAX Counter32 359 MAX-ACCESS read-only 360 STATUS current 361 DESCRIPTION 362 "The total number of recipients specified in all messages 363 received since MTA initialization. Recipients this MTA 364 has no responsibility for, i.e. inactive envelope 365 recipients or ones referred to in message headers, 366 should not be counted even if information about such 367 recipients is available. This includes messages 368 transmitted to this MTA from other MTAs as well as 369 messages that have been submitted to the MTA directly 370 by end-users or applications." 371 ::= {mtaEntry 7} 373 mtaStoredRecipients OBJECT-TYPE 374 SYNTAX Gauge32 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "The total number of recipients specified in all messages 379 currently stored in the MTA. Recipients this MTA has no 380 responsibility for, i.e. inactive envelope recipients or 381 ones referred to in message headers, should not be 382 counted. This includes messages that are awaiting 383 transmission to some other MTA or are waiting for 384 delivery to an end-user or application." 385 ::= {mtaEntry 8} 387 mtaTransmittedRecipients OBJECT-TYPE 388 SYNTAX Counter32 389 MAX-ACCESS read-only 390 STATUS current 391 DESCRIPTION 392 "The total number of recipients specified in all messages 393 transmitted since MTA initialization. Recipients this 394 MTA had no responsibility for, i.e. inactive envelope 395 recipients or ones referred to in message headers, 396 should not be counted. This includes messages that were 397 transmitted to some other MTA or are waiting for 398 delivery to an end-user or application." 399 ::= {mtaEntry 9} 401 mtaSuccessfulConvertedMessages OBJECT-TYPE 402 SYNTAX Counter32 403 MAX-ACCESS read-only 404 STATUS current 405 DESCRIPTION 406 "The number of messages that have been successfully 407 converted from one form to another since MTA 408 initialization." 409 ::= {mtaEntry 10} 411 mtaFailedConvertedMessages OBJECT-TYPE 412 SYNTAX Counter32 413 MAX-ACCESS read-only 414 STATUS current 415 DESCRIPTION 416 "The number of messages for which an unsuccessful 417 attempt was made to convert them from one form to 418 another since MTA initialization." 419 ::= {mtaEntry 11} 421 mtaLoopsDetected OBJECT-TYPE 422 SYNTAX Counter32 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "A message loop is defined as a situation where the MTA 427 decides that a given message will never be delivered to 428 one or more recipients and instead will continue to 429 loop endlessly through one or more MTAs. This variable 430 counts the number of times the MTA has detected such a 431 situation since MTA initialization. Note that the 432 mechanism MTAs use to detect loops (e.g., trace field 433 counting, count of references to this MTA in a trace 434 field, examination of DNS or other directory information, 435 etc.), the level at which loops are detected (e.g., per 436 message, per recipient, per directory entry, etc.), and 437 the handling of a loop once it is detected (e.g., looping 438 messages are held, looping messages are bounced or sent 439 to the postmaster, messages that the MTA knows will loop 440 won't be accepted, etc.) vary widely from one MTA to the 441 next and cannot be inferred from this variable." 442 ::= {mtaEntry 12} 444 -- MTAs typically group inbound reception, queue storage, and 445 -- outbound transmission in some way, rather than accounting for 446 -- such operations only across the MTA as a whole. In the most 447 -- extreme case separate information will be maintained for each 448 -- different entity that receives messages and for each entity 449 -- the MTA stores messages for and delivers messages to. Other 450 -- MTAs may elect to treat all reception equally, all queue 451 -- storage equally, all deliveries equally, or some combination 452 -- of this. Overlapped groupings are also possible, where an MTA 453 -- decomposes its traffic in different ways for different 454 -- purposes. 456 -- In any case, a grouping abstraction is an extremely useful for 457 -- breaking down the activities of an MTA. For purposes of 458 -- labelling this will be called a "group" in this MIB. 460 -- Each group contains all the variables needed to monitor all 461 -- aspects of an MTA's operation. However, the fact that all 462 -- groups contain all possible variables does not imply that all 463 -- groups must use all possible variables. For example, a single 464 -- group might be used to monitor only one kind of event (inbound 465 -- processing, outbound processing, or storage). In this sort of 466 -- configuration any counters that are unused as a result of a 467 -- given MTA's use of the group construct must be inaccessible; 468 -- e.g., returning either a noSuchName error (for an SNMPv1 get), 469 -- or a noSuchInstance exception (for an SNMPv2 get). 471 -- Groups can be created at any time after MTA initialization. Once 472 -- a group is created it should not be deleted or its mtaGroupIndex 473 -- changed unless the MTA is reinitialized. 475 -- Groups are not necessarily mutually exclusive. A given event may 476 -- be recorded by more than one group, a message may be seen as 477 -- stored by more than one group, and so on. Groups should be all 478 -- inclusive, however: if groups are implemented all aspects of an 479 -- MTA's operation should be registered in at least one group. 480 -- This freedom lets implementors use different sets of groups to 481 -- provide different "views" of an MTA. 483 -- The possibility of overlap between groups means that summing 484 -- variables across groups may not produce values equal to those in 485 -- the mtaTable. mtaTable should always provide accurate information 486 -- about the MTA as a whole. 488 -- The term "channel" is often used in MTA implementations; channels 489 -- are usually, but not always, equivalent to a group. However, 490 -- this MIB does not use the term "channel" because there is no 491 -- requirement that an MTA supporting this MIB has to map its 492 -- "channel" abstraction one-to-one onto the MIB's group abstraction. 494 -- An MTA may create a group or group of groups at any time. Once 495 -- created, however, an MTA cannot delete an entry for a group from 496 -- the group table. Deletion is only allowed when the MTA is 497 -- reinitialized, and is not required even then. This restriction 498 -- is imposed so that monitoring agents can rely on group 499 -- assignments being consistent across multiple query operations. 501 -- Groups may be laid out so as to form a hierarchical arrangement, 502 -- with some groups acting as subgroups for other groups. 503 -- Alternately, disjoint groups of groups may be used to provide 504 -- different sorts of "snapshots" of MTA operation. The 505 -- mtaGroupHierarchy variable provides an indication of how each 506 -- group fits into the overall arrangement being used. 508 -- Note that SNMP also defines and uses term "group". MTA groups are 509 -- NOT the same as SNMP groups. 511 mtaGroupTable OBJECT-TYPE 512 SYNTAX SEQUENCE OF MtaGroupEntry 513 MAX-ACCESS not-accessible 514 STATUS current 515 DESCRIPTION 516 "The table holding information specific to each MTA group." 517 ::= {mta 2} 519 mtaGroupEntry OBJECT-TYPE 520 SYNTAX MtaGroupEntry 521 MAX-ACCESS not-accessible 522 STATUS current 523 DESCRIPTION 524 "The entry associated with each MTA group." 525 INDEX {applIndex, mtaGroupIndex} 526 ::= {mtaGroupTable 1} 528 MtaGroupEntry ::= SEQUENCE { 529 mtaGroupIndex 530 INTEGER, 531 mtaGroupReceivedMessages 532 Counter32, 533 mtaGroupRejectedMessages 534 Counter32, 535 mtaGroupStoredMessages 536 Gauge32, 537 mtaGroupTransmittedMessages 538 Counter32, 539 mtaGroupReceivedVolume 540 Counter32, 541 mtaGroupStoredVolume 542 Gauge32, 543 mtaGroupTransmittedVolume 544 Counter32, 545 mtaGroupReceivedRecipients 546 Counter32, 547 mtaGroupStoredRecipients 548 Gauge32, 549 mtaGroupTransmittedRecipients 550 Counter32, 551 mtaGroupOldestMessageStored 552 TimeInterval, 553 mtaGroupInboundAssociations 554 Gauge32, 555 mtaGroupOutboundAssociations 556 Gauge32, 557 mtaGroupAccumulatedInboundAssociations 558 Counter32, 559 mtaGroupAccumulatedOutboundAssociations 560 Counter32, 561 mtaGroupLastInboundActivity 562 TimeInterval, 563 mtaGroupLastOutboundActivity 564 TimeInterval, 565 mtaGroupLastOutboundAssociationAttempt 566 TimeInterval, 567 mtaGroupRejectedInboundAssociations 568 Counter32, 569 mtaGroupFailedOutboundAssociations 570 Counter32, 571 mtaGroupInboundRejectionReason 572 SnmpAdminString, 574 mtaGroupOutboundConnectFailureReason 575 SnmpAdminString, 576 mtaGroupScheduledRetry 577 TimeInterval, 578 mtaGroupMailProtocol 579 OBJECT IDENTIFIER, 580 mtaGroupName 581 SnmpAdminString, 582 mtaGroupSuccessfulConvertedMessages 583 Counter32, 584 mtaGroupFailedConvertedMessages 585 Counter32, 586 mtaGroupDescription 587 SnmpAdminString, 588 mtaGroupURL 589 URLString, 590 mtaGroupCreationTime 591 TimeInterval, 592 mtaGroupHierarchy 593 INTEGER, 594 mtaGroupOldestMessageId 595 SnmpAdminString, 596 mtaGroupLoopsDetected 597 Counter32 598 } 600 mtaGroupIndex OBJECT-TYPE 601 SYNTAX INTEGER (1..2147483647) 602 MAX-ACCESS not-accessible 603 STATUS current 604 DESCRIPTION 605 "The index associated with a group for a given MTA." 606 ::= {mtaGroupEntry 1} 608 mtaGroupReceivedMessages OBJECT-TYPE 609 SYNTAX Counter32 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The number of messages received to this group since 614 group creation." 615 ::= {mtaGroupEntry 2} 617 mtaGroupRejectedMessages OBJECT-TYPE 618 SYNTAX Counter32 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "The number of messages rejected by this group since 623 group creation." 624 ::= {mtaGroupEntry 3} 626 mtaGroupStoredMessages OBJECT-TYPE 627 SYNTAX Gauge32 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "The total number of messages currently stored in this 632 group's queue." 633 ::= {mtaGroupEntry 4} 635 mtaGroupTransmittedMessages OBJECT-TYPE 636 SYNTAX Counter32 637 MAX-ACCESS read-only 638 STATUS current 639 DESCRIPTION 640 "The number of messages transmitted by this group since 641 group creation." 642 ::= {mtaGroupEntry 5} 644 mtaGroupReceivedVolume OBJECT-TYPE 645 SYNTAX Counter32 646 UNITS "K-octets" 647 MAX-ACCESS read-only 648 STATUS current 649 DESCRIPTION 650 "The total volume of messages received to this group since 651 group creation, measured in kilo-octets. This volume 652 should include all transferred data that is logically above 653 the mail transport protocol level. For example, an 654 SMTP-based MTA should use the number of kilo-octets in the 655 message header and body, while an X.400-based MTA should use 656 the number of kilo-octets of P2 data." 657 ::= {mtaGroupEntry 6} 659 mtaGroupStoredVolume OBJECT-TYPE 660 SYNTAX Gauge32 661 UNITS "K-octets" 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 665 "The total volume of messages currently stored in this 666 group's queue, measured in kilo-octets. This volume should 667 include all stored data that is logically above the mail 668 transport protocol level. For example, an SMTP-based 669 MTA should use the number of kilo-octets in the message 670 header and body, while an X.400-based MTA would use the 671 number of kilo-octets of P2 data." 672 ::= {mtaGroupEntry 7} 674 mtaGroupTransmittedVolume OBJECT-TYPE 675 SYNTAX Counter32 676 UNITS "K-octets" 677 MAX-ACCESS read-only 678 STATUS current 679 DESCRIPTION 680 "The total volume of messages transmitted by this group 681 since group creation, measured in kilo-octets. This 682 volume should include all transferred data that is logically 683 above the mail transport protocol level. For example, an 684 SMTP-based MTA should use the number of kilo-octets in the 685 message header and body, while an X.400-based MTA should use 686 the number of kilo-octets of P2 data." 687 ::= {mtaGroupEntry 8} 689 mtaGroupReceivedRecipients OBJECT-TYPE 690 SYNTAX Counter32 691 MAX-ACCESS read-only 692 STATUS current 693 DESCRIPTION 694 "The total number of recipients specified in all messages 695 received to this group since group creation. 696 Recipients this MTA has no responsibility for should not 697 be counted." 698 ::= {mtaGroupEntry 9} 700 mtaGroupStoredRecipients OBJECT-TYPE 701 SYNTAX Gauge32 702 MAX-ACCESS read-only 703 STATUS current 704 DESCRIPTION 705 "The total number of recipients specified in all messages 706 currently stored in this group's queue. Recipients this 707 MTA has no responsibility for should not be counted." 708 ::= {mtaGroupEntry 10} 710 mtaGroupTransmittedRecipients OBJECT-TYPE 711 SYNTAX Counter32 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "The total number of recipients specified in all messages 716 transmitted by this group since group creation. 717 Recipients this MTA had no responsibility for should not 718 be counted." 719 ::= {mtaGroupEntry 11} 721 mtaGroupOldestMessageStored OBJECT-TYPE 722 SYNTAX TimeInterval 723 MAX-ACCESS read-only 724 STATUS current 725 DESCRIPTION 726 "Time since the oldest message in this group's queue was 727 placed in the queue." 728 ::= {mtaGroupEntry 12} 730 mtaGroupInboundAssociations OBJECT-TYPE 731 SYNTAX Gauge32 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION 735 "The number of current associations to the group, where the 736 group is the responder." 737 ::= {mtaGroupEntry 13} 739 mtaGroupOutboundAssociations OBJECT-TYPE 740 SYNTAX Gauge32 741 MAX-ACCESS read-only 742 STATUS current 743 DESCRIPTION 744 "The number of current associations to the group, where the 745 group is the initiator." 746 ::= {mtaGroupEntry 14} 748 mtaGroupAccumulatedInboundAssociations OBJECT-TYPE 749 SYNTAX Counter32 750 MAX-ACCESS read-only 751 STATUS current 752 DESCRIPTION 753 "The total number of associations to the group since 754 group creation, where the MTA was the responder." 755 ::= {mtaGroupEntry 15} 757 mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE 758 SYNTAX Counter32 759 MAX-ACCESS read-only 760 STATUS current 761 DESCRIPTION 762 "The total number of associations from the group since 763 group creation, where the MTA was the initiator." 764 ::= {mtaGroupEntry 16} 766 mtaGroupLastInboundActivity OBJECT-TYPE 767 SYNTAX TimeInterval 768 MAX-ACCESS read-only 769 STATUS current 770 DESCRIPTION 771 "Time since the last time that this group had an active 772 inbound association for purposes of message reception." 773 ::= {mtaGroupEntry 17} 775 mtaGroupLastOutboundActivity OBJECT-TYPE 776 SYNTAX TimeInterval 777 MAX-ACCESS read-only 778 STATUS current 779 DESCRIPTION 780 "Time since the last time that this group had a 781 successful outbound association for purposes of 782 message delivery." 783 ::= {mtaGroupEntry 18} 785 mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE 786 SYNTAX TimeInterval 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "Time since the last time that this group attempted 791 to make an outbound association for purposes of 792 message delivery." 793 ::= {mtaGroupEntry 34} 795 mtaGroupRejectedInboundAssociations OBJECT-TYPE 796 SYNTAX Counter32 797 MAX-ACCESS read-only 798 STATUS current 799 DESCRIPTION 800 "The total number of inbound associations the group has 801 rejected, since group creation. Rejected associations 802 are not counted in the accumulated association totals." 803 ::= {mtaGroupEntry 19} 805 mtaGroupFailedOutboundAssociations OBJECT-TYPE 806 SYNTAX Counter32 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "The total number associations where the group was the 811 initiator and association establishment has failed, 812 since group creation. Failed associations are 813 not counted in the accumulated association totals." 814 ::= {mtaGroupEntry 20} 816 mtaGroupInboundRejectionReason OBJECT-TYPE 817 SYNTAX SnmpAdminString 818 MAX-ACCESS read-only 819 STATUS current 820 DESCRIPTION 821 "The failure reason, if any, for the last association this 822 group refused to respond to. If no association attempt 823 has been made since the MTA was initialized the value 824 should be 'never'." 825 ::= {mtaGroupEntry 21} 827 mtaGroupOutboundConnectFailureReason OBJECT-TYPE 828 SYNTAX SnmpAdminString 829 MAX-ACCESS read-only 830 STATUS current 831 DESCRIPTION 832 "The failure reason, if any, for the last association attempt 833 this group initiated. If no association attempt has been 834 made since the MTA was initialized the value should be 835 'never'." 836 ::= {mtaGroupEntry 22} 838 mtaGroupScheduledRetry OBJECT-TYPE 839 SYNTAX TimeInterval 840 MAX-ACCESS read-only 841 STATUS current 842 DESCRIPTION 843 "The amount of time until this group is next scheduled to 844 attempt to make an association." 845 ::= {mtaGroupEntry 23} 847 mtaGroupMailProtocol OBJECT-TYPE 848 SYNTAX OBJECT IDENTIFIER 849 MAX-ACCESS read-only 850 STATUS current 851 DESCRIPTION 852 "An identification of the protocol being used by this group. 853 For an group employing OSI protocols, this will be the 854 Application Context. For Internet applications, the IANA 855 maintains a registry of the OIDs which correspond to well-known 856 message transfer protocols. If the application protocol is 857 not listed in the registry, an OID value of the form 858 {applTCPProtoID port} or {applUDProtoID port} are used for 859 TCP-based and UDP-based protocols, respectively. In either 860 case 'port' corresponds to the primary port number being 861 used by the group. applTCPProtoID and applUDPProtoID are 862 defined in the NETWORK-SERVICES-MIB, RFC XXXX." 863 ::= {mtaGroupEntry 24} 865 mtaGroupName OBJECT-TYPE 866 SYNTAX SnmpAdminString 867 MAX-ACCESS read-only 868 STATUS current 869 DESCRIPTION 870 "A descriptive name for the group. If this group connects to 871 a single remote MTA this should be the name of that MTA. If 872 this in turn is an Internet MTA this should be the domain 873 name. For an OSI MTA it should be the string encoded 874 distinguished name of the managed object using the format 875 defined in RFC 1779. For X.400(1984) MTAs which do not 876 have a Distinguished Name, the RFC 2156 syntax 877 'mta in globalid' used in X400-Received: fields can be 878 used." 879 ::= {mtaGroupEntry 25} 881 mtaGroupSuccessfulConvertedMessages OBJECT-TYPE 882 SYNTAX Counter32 883 MAX-ACCESS read-only 884 STATUS current 885 DESCRIPTION 886 "The number of messages that have been successfully 887 converted from one form to another in this group 888 since group creation." 889 ::= {mtaGroupEntry 26} 891 mtaGroupFailedConvertedMessages OBJECT-TYPE 892 SYNTAX Counter32 893 MAX-ACCESS read-only 894 STATUS current 895 DESCRIPTION 896 "The number of messages for which an unsuccessful 897 attempt was made to convert them from one form to 898 another in this group since group creation." 899 ::= {mtaGroupEntry 27} 901 mtaGroupDescription OBJECT-TYPE 902 SYNTAX SnmpAdminString 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "A description of the group's purpose. This information is 907 intended to identify the group in a status display." 908 ::= {mtaGroupEntry 28} 910 mtaGroupURL OBJECT-TYPE 911 SYNTAX URLString 912 MAX-ACCESS read-only 913 STATUS current 914 DESCRIPTION 915 "A URL pointing to a description of the group. This 916 information is intended to identify and briefly describe 917 the group in a status display." 918 ::= {mtaGroupEntry 29} 920 mtaGroupCreationTime OBJECT-TYPE 921 SYNTAX TimeInterval 922 MAX-ACCESS read-only 923 STATUS current 924 DESCRIPTION 925 "Time since this group was first created." 926 ::= {mtaGroupEntry 30} 928 mtaGroupHierarchy OBJECT-TYPE 929 SYNTAX INTEGER (-2147483648..2147483647) 930 MAX-ACCESS read-only 931 STATUS current 932 DESCRIPTION 933 "Describes how this group fits into the hierarchy. A 934 positive value is interpreted as an mtaGroupIndex 935 value for some other group whose variables include 936 those of this group (and usually others). A negative 937 value is interpreted as a group collection code: Groups 938 with common negative hierarchy values comprise one 939 particular breakdown of MTA activity as a whole. A 940 zero value means that this MIB implementation doesn't 941 implement hierarchy indicators and thus the overall 942 group hierarchy cannot be determined." 943 ::= {mtaGroupEntry 31} 945 mtaGroupOldestMessageId OBJECT-TYPE 946 SYNTAX SnmpAdminString 947 MAX-ACCESS read-only 948 STATUS current 949 DESCRIPTION 950 "Message ID of the oldest message in the group's queue. 951 Whenever possible this should be in the form of an 952 RFC 822 msg-id; X.400 may convert X.400 message 953 identifiers to this form by following the rules laid 954 out in RFC2156." 955 ::= {mtaGroupEntry 32} 957 mtaGroupLoopsDetected OBJECT-TYPE 958 SYNTAX Counter32 959 MAX-ACCESS read-only 960 STATUS current 961 DESCRIPTION 962 "A message loop is defined as a situation where the MTA 963 decides that a given message will never be delivered to 964 one or more recipients and instead will continue to 965 loop endlessly through one or more MTAs. This variable 966 counts the number of times the MTA has detected such a 967 situation in conjunction with something associated with 968 this group since group creation. Note that the 969 mechanism MTAs use to detect loops (e.g., trace field 970 counting, count of references to this MTA in a trace 971 field, examination of DNS or other directory information, 972 etc.), the level at which loops are detected (e.g., per 973 message, per recipient, per directory entry, etc.), and 974 the handling of a loop once it is detected (e.g., looping 975 messages are held, looping messages are bounced or sent 976 to the postmaster, messages that the MTA knows will loop 977 won't be accepted, etc.) vary widely from one MTA to the 978 next and cannot be inferred from this variable." 979 ::= {mtaGroupEntry 33} 981 -- The mtaGroupAssociationTable provides a means of correlating 982 -- entries in the network services association table with the 983 -- MTA group responsible for the association. 985 mtaGroupAssociationTable OBJECT-TYPE 986 SYNTAX SEQUENCE OF MtaGroupAssociationEntry 987 MAX-ACCESS not-accessible 988 STATUS current 989 DESCRIPTION 990 "The table holding information regarding the associations 991 for each MTA group." 992 ::= {mta 3} 994 mtaGroupAssociationEntry OBJECT-TYPE 995 SYNTAX MtaGroupAssociationEntry 996 MAX-ACCESS not-accessible 997 STATUS current 998 DESCRIPTION 999 "The entry holding information regarding the associations 1000 for each MTA group." 1001 INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex} 1002 ::= {mtaGroupAssociationTable 1} 1004 MtaGroupAssociationEntry ::= SEQUENCE { 1005 mtaGroupAssociationIndex 1006 INTEGER 1007 } 1009 mtaGroupAssociationIndex OBJECT-TYPE 1010 SYNTAX INTEGER (1..2147483647) 1011 MAX-ACCESS read-only 1012 STATUS current 1013 DESCRIPTION 1014 "Reference into association table to allow correlation of 1015 this group's active associations with the association table." 1016 ::= {mtaGroupAssociationEntry 1} 1018 -- The mtaGroupErrorTable gives each group a way of tallying 1019 -- the specific errors it has encountered. The mechanism 1020 -- defined here uses RFC 1893 status codes to identify 1021 -- various specific errors. There are also classes for generic 1022 -- errors of various sorts, and the entire mechanism is also 1023 -- extensible, in that new error codes can be defined at any 1024 -- time. 1026 mtaGroupErrorTable OBJECT-TYPE 1027 SYNTAX SEQUENCE OF MtaGroupErrorEntry 1028 MAX-ACCESS not-accessible 1029 STATUS current 1030 DESCRIPTION 1031 "The table holding information regarding accumulated errors 1032 for each MTA group." 1033 ::= {mta 5} 1035 mtaGroupErrorEntry OBJECT-TYPE 1036 SYNTAX MtaGroupErrorEntry 1037 MAX-ACCESS not-accessible 1038 STATUS current 1039 DESCRIPTION 1040 "The entry holding information regarding accumulated 1041 errors for each MTA group." 1042 INDEX {applIndex, mtaGroupIndex, mtaStatusCode} 1043 ::= {mtaGroupErrorTable 1} 1045 MtaGroupErrorEntry ::= SEQUENCE { 1046 mtaStatusCode 1047 INTEGER (4000000..5999999), 1048 mtaGroupInboundErrorCount 1049 Counter32, 1050 mtaGroupInternalErrorCount 1051 Counter32, 1052 mtaGroupOutboundErrorCount 1053 Counter32 1054 } 1056 mtaGroupInboundErrorCount OBJECT-TYPE 1057 SYNTAX Counter32 1058 MAX-ACCESS read-only 1059 STATUS current 1060 DESCRIPTION 1061 "Count of the number of errors of a given type that have 1062 been accumulated in association with a particular group 1063 while processing incoming messages. In the case of SMTP 1064 these will typically be errors reporting by an SMTP 1065 server to the remote client; in the case of X.400 1066 these will typically be errors encountered while 1067 processing an incoming message." 1068 ::= {mtaGroupErrorEntry 1} 1070 mtaGroupInternalErrorCount OBJECT-TYPE 1071 SYNTAX Counter32 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "Count of the number of errors of a given type that have 1076 been accumulated in association with a particular group 1077 during internal MTA processing." 1078 ::= {mtaGroupErrorEntry 2} 1080 mtaGroupOutboundErrorCount 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's 1087 outbound connection activities. In the case of an SMTP 1088 client these will typically be errors reported while 1089 attempting to contact or while communicating with the 1090 remote SMTP server. In the case of X.400 these will 1091 typically be errors encountered while constructing 1092 or attempting to deliver an outgoing message." 1093 ::= {mtaGroupErrorEntry 3} 1095 mtaStatusCode OBJECT-TYPE 1096 SYNTAX INTEGER (4000000..5999999) 1097 MAX-ACCESS not-accessible 1098 STATUS current 1099 DESCRIPTION 1100 "An index capable of representing an Enhanced Mail System 1101 Status Code. Enhanced Mail System Status Codes are 1102 defined in RFC 1893. These codes have the form 1104 class.subject.detail 1106 Here 'class' is either 2, 4, or 5 and both 'subject' and 1107 'detail' are integers in the range 0..999. Given a status 1108 code the corresponding index value is defined to be 1109 ((class * 1000) + subject) * 1000 + detail. Both SMTP 1110 error response codes and X.400 reason and diagnostic codes 1111 can be mapped into these codes, resulting in a namespace 1112 capable of describing most error conditions a mail system 1113 encounters in a generic yet detailed way." 1114 ::= {mtaGroupErrorEntry 4} 1116 -- Conformance information 1118 mtaConformance OBJECT IDENTIFIER ::= {mta 4} 1120 mtaGroups OBJECT IDENTIFIER ::= {mtaConformance 1} 1121 mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2} 1123 -- Compliance statements 1125 mtaCompliance MODULE-COMPLIANCE 1126 STATUS current 1127 DESCRIPTION 1128 "The compliance statement for RFC 1566 implementations 1129 which support the Mail Monitoring MIB for basic 1130 monitoring of MTAs." 1131 MODULE -- this module 1132 MANDATORY-GROUPS {mtaRFC1566Group} 1133 ::= {mtaCompliances 1} 1135 mtaAssocCompliance MODULE-COMPLIANCE 1136 STATUS current 1137 DESCRIPTION 1138 "The compliance statement for RFC 1566 implementations 1139 which support the Mail Monitoring MIB for monitoring 1140 of MTAs and their associations." 1141 MODULE -- this module 1142 MANDATORY-GROUPS {mtaRFC1566Group, mtaRFC1566AssocGroup} 1143 ::= {mtaCompliances 2} 1145 mtaRFC2249Compliance MODULE-COMPLIANCE 1146 STATUS current 1147 DESCRIPTION 1148 "The compliance statement for RFC 2249 implementations 1149 which support the Mail Monitoring MIB for basic 1150 monitoring of MTAs." 1151 MODULE -- this module 1152 MANDATORY-GROUPS {mtaRFC2249Group} 1153 ::= {mtaCompliances 5} 1155 mtaRFC2249AssocCompliance MODULE-COMPLIANCE 1156 STATUS current 1157 DESCRIPTION 1158 "The compliance statement for RFC 2249 implementations 1159 which support the Mail Monitoring MIB for monitoring of 1160 MTAs and their associations." 1161 MODULE -- this module 1162 MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup} 1163 ::= {mtaCompliances 6} 1165 mtaRFC2249ErrorCompliance MODULE-COMPLIANCE 1166 STATUS current 1167 DESCRIPTION 1168 "The compliance statement for RFC 2249 implementations 1169 which support the Mail Monitoring MIB for monitoring of 1170 MTAs and detailed errors." 1171 MODULE -- this module 1172 MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249ErrorGroup} 1173 ::= {mtaCompliances 7} 1175 mtaRFC2249FullCompliance MODULE-COMPLIANCE 1176 STATUS current 1177 DESCRIPTION 1178 "The compliance statement for RFC 2249 implementations 1179 which support the full Mail Monitoring MIB for 1180 monitoring of MTAs, associations, and detailed errors." 1181 MODULE -- this module 1182 MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup, 1183 mtaRFC2249ErrorGroup} 1184 ::= {mtaCompliances 8} 1186 mtaRFCYYYYCompliance MODULE-COMPLIANCE 1187 STATUS current 1188 DESCRIPTION 1189 "The compliance statement for RFC YYYY implementations 1190 which support the Mail Monitoring MIB for basic 1191 monitoring of MTAs." 1192 MODULE -- this module 1193 MANDATORY-GROUPS {mtaRFCYYYYGroup} 1194 ::= {mtaCompliances 9} 1196 mtaRFCYYYYAssocCompliance MODULE-COMPLIANCE 1197 STATUS current 1198 DESCRIPTION 1199 "The compliance statement for RFC YYYY implementations 1200 which support the Mail Monitoring MIB for monitoring of 1201 MTAs and their associations." 1202 MODULE -- this module 1203 MANDATORY-GROUPS {mtaRFCYYYYGroup, mtaRFCYYYYAssocGroup} 1204 ::= {mtaCompliances 10} 1206 mtaRFCYYYYErrorCompliance MODULE-COMPLIANCE 1207 STATUS current 1208 DESCRIPTION 1209 "The compliance statement for RFC YYYY implementations 1210 which support the Mail Monitoring MIB for monitoring of 1211 MTAs and detailed errors." 1212 MODULE -- this module 1213 MANDATORY-GROUPS {mtaRFCYYYYGroup, mtaRFCYYYYErrorGroup} 1214 ::= {mtaCompliances 11} 1216 mtaRFCYYYYFullCompliance MODULE-COMPLIANCE 1217 STATUS current 1218 DESCRIPTION 1219 "The compliance statement for RFC YYYY implementations 1220 which support the full Mail Monitoring MIB for 1221 monitoring of MTAs, associations, and detailed errors." 1222 MODULE -- this module 1223 MANDATORY-GROUPS {mtaRFCYYYYGroup, mtaRFCYYYYAssocGroup, 1224 mtaRFCYYYYErrorGroup} 1225 ::= {mtaCompliances 12} 1227 -- Units of conformance 1229 mtaRFC1566Group OBJECT-GROUP 1230 OBJECTS { 1231 mtaReceivedMessages, mtaStoredMessages, 1232 mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, 1233 mtaTransmittedVolume, mtaReceivedRecipients, 1234 mtaStoredRecipients, mtaTransmittedRecipients, 1235 mtaGroupReceivedMessages, mtaGroupRejectedMessages, 1236 mtaGroupStoredMessages, mtaGroupTransmittedMessages, 1237 mtaGroupReceivedVolume, mtaGroupStoredVolume, 1238 mtaGroupTransmittedVolume, mtaGroupReceivedRecipients, 1239 mtaGroupStoredRecipients, mtaGroupTransmittedRecipients, 1240 mtaGroupOldestMessageStored, mtaGroupInboundAssociations, 1241 mtaGroupOutboundAssociations, 1242 mtaGroupAccumulatedInboundAssociations, 1243 mtaGroupAccumulatedOutboundAssociations, 1244 mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity, 1245 mtaGroupRejectedInboundAssociations, 1246 mtaGroupFailedOutboundAssociations, 1247 mtaGroupInboundRejectionReason, 1248 mtaGroupOutboundConnectFailureReason, 1249 mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName} 1250 STATUS current 1251 DESCRIPTION 1252 "A collection of objects providing basic monitoring of MTAs. 1253 This is the original set of such objects defined in RFC 1254 1566." 1255 ::= {mtaGroups 10} 1257 mtaRFC1566AssocGroup OBJECT-GROUP 1258 OBJECTS { 1259 mtaGroupAssociationIndex} 1260 STATUS current 1261 DESCRIPTION 1262 "A collection of objects providing monitoring of MTA 1263 associations. This is the original set of such objects 1264 defined in RFC 1566." 1265 ::= {mtaGroups 11} 1267 mtaRFC2249Group OBJECT-GROUP 1268 OBJECTS { 1269 mtaReceivedMessages, mtaStoredMessages, 1270 mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, 1271 mtaTransmittedVolume, mtaReceivedRecipients, 1272 mtaStoredRecipients, mtaTransmittedRecipients, 1273 mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages, 1274 mtaGroupReceivedMessages, mtaGroupRejectedMessages, 1275 mtaGroupStoredMessages, mtaGroupTransmittedMessages, 1276 mtaGroupReceivedVolume, mtaGroupStoredVolume, 1277 mtaGroupTransmittedVolume, mtaGroupReceivedRecipients, 1278 mtaGroupStoredRecipients, mtaGroupTransmittedRecipients, 1279 mtaGroupOldestMessageStored, mtaGroupInboundAssociations, 1280 mtaGroupOutboundAssociations, mtaLoopsDetected, 1281 mtaGroupAccumulatedInboundAssociations, 1282 mtaGroupAccumulatedOutboundAssociations, 1283 mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity, 1284 mtaGroupLastOutboundAssociationAttempt, 1285 mtaGroupRejectedInboundAssociations, 1286 mtaGroupFailedOutboundAssociations, 1287 mtaGroupInboundRejectionReason, 1288 mtaGroupOutboundConnectFailureReason, 1289 mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName, 1290 mtaGroupSuccessfulConvertedMessages, 1291 mtaGroupFailedConvertedMessages, mtaGroupDescription, 1292 mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy, 1293 mtaGroupOldestMessageId, mtaGroupLoopsDetected} 1294 STATUS current 1295 DESCRIPTION 1296 "A collection of objects providing basic monitoring of MTAs. 1297 This group was originally defined in RFC 2249." 1298 ::= {mtaGroups 4} 1300 mtaRFC2249AssocGroup OBJECT-GROUP 1301 OBJECTS { 1302 mtaGroupAssociationIndex} 1303 STATUS current 1304 DESCRIPTION 1305 "A collection of objects providing monitoring of MTA 1306 associations. This group was originally defined in RFC 1307 2249." 1308 ::= {mtaGroups 5} 1310 mtaRFC2249ErrorGroup OBJECT-GROUP 1311 OBJECTS { 1312 mtaGroupInboundErrorCount, mtaGroupInternalErrorCount, 1313 mtaGroupOutboundErrorCount} 1314 STATUS current 1315 DESCRIPTION 1316 "A collection of objects providing monitoring of 1317 detailed MTA errors. This group was originally defined 1318 in RFC 2249." 1319 ::= {mtaGroups 6} 1321 mtaRFCYYYYGroup OBJECT-GROUP 1322 OBJECTS { 1323 mtaReceivedMessages, mtaStoredMessages, 1324 mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, 1325 mtaTransmittedVolume, mtaReceivedRecipients, 1326 mtaStoredRecipients, mtaTransmittedRecipients, 1327 mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages, 1328 mtaGroupReceivedMessages, mtaGroupRejectedMessages, 1329 mtaGroupStoredMessages, mtaGroupTransmittedMessages, 1330 mtaGroupReceivedVolume, mtaGroupStoredVolume, 1331 mtaGroupTransmittedVolume, mtaGroupReceivedRecipients, 1332 mtaGroupStoredRecipients, mtaGroupTransmittedRecipients, 1333 mtaGroupOldestMessageStored, mtaGroupInboundAssociations, 1334 mtaGroupOutboundAssociations, mtaLoopsDetected, 1335 mtaGroupAccumulatedInboundAssociations, 1336 mtaGroupAccumulatedOutboundAssociations, 1337 mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity, 1338 mtaGroupLastOutboundAssociationAttempt, 1339 mtaGroupRejectedInboundAssociations, 1340 mtaGroupFailedOutboundAssociations, 1341 mtaGroupInboundRejectionReason, 1342 mtaGroupOutboundConnectFailureReason, 1343 mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName, 1344 mtaGroupSuccessfulConvertedMessages, 1345 mtaGroupFailedConvertedMessages, mtaGroupDescription, 1346 mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy, 1347 mtaGroupOldestMessageId, mtaGroupLoopsDetected} 1348 STATUS current 1349 DESCRIPTION 1350 "A collection of objects providing basic monitoring of MTAs. 1351 This is the appropriate group for RFC YYYY." 1352 ::= {mtaGroups 7} 1354 mtaRFCYYYYAssocGroup OBJECT-GROUP 1355 OBJECTS { 1356 mtaGroupAssociationIndex} 1357 STATUS current 1358 DESCRIPTION 1359 "A collection of objects providing monitoring of MTA 1360 associations. This is the appropriate group for RFC 1361 YYYY association monitoring." 1362 ::= {mtaGroups 8} 1364 mtaRFCYYYYErrorGroup OBJECT-GROUP 1365 OBJECTS { 1366 mtaGroupInboundErrorCount, mtaGroupInternalErrorCount, 1367 mtaGroupOutboundErrorCount} 1368 STATUS current 1369 DESCRIPTION 1370 "A collection of objects providing monitoring of 1371 detailed MTA errors. This is the appropriate group 1372 for RFC YYYY error monitoring." 1373 ::= {mtaGroups 9} 1375 END 1377 7. Changes made since RFC 2249 1379 This revision corrects a number of minor technical errors in the 1380 construction of the mail monitoring MIB in RFC 2249 [18]: 1382 (1) All DisplayStrings have been changed to SnmpAdminStrings, 1384 (2) the conformance groups for different versions of this MIB have 1385 been corrected, 1387 (3) the required mtaStatusCode entry has been added to 1388 MtaGroupErrorEntry (which does not affect the bits on the wire in 1389 any way), and 1391 (4) the recommendation that an empty string be returned if the last 1392 operation was successful has been removed from 1393 mtaGroupInboundRejectionReason and 1394 mtaGroupOutboundConnectFailureReason as it conflicts with the 1395 stated purpose of these variables. 1397 8. Acknowledgements 1399 This document is a work product of the Mail and Directory Management 1400 (MADMAN) Working Group of the IETF. It is based on an earlier MIB 1401 designed by S. Kille, T. Lenggenhager, D. Partain, and W. Yeong. The 1402 Electronic Mail Association's TSC committee was instrumental in 1403 providing feedback on and suggesting enhancements to RFC 1566 [19] that 1404 have led to the present document. 1406 9. References 1408 [1] Harrington, D., Presuhn, R., and Wijnen, B., "An Architecture for 1409 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1411 [2] Rose, M. and McCloghrie, K., "Structure and Identification of 1412 Management Information for TCP/IP-based Internets", RFC 1155, May 1413 1990. 1415 [3] Rose, M. and McCloghrie, K., "Concise MIB Definitions", RFC 1212, 1416 March 1991. 1418 [4] Rose, M., "A Convention for Defining Traps for use with the SNMP", 1419 RFC 1215, March 1991. 1421 [5] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Structure of 1422 Management Information Version 2 (SMIv2)", RFC 2578, April 1999. 1424 [6] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Textual 1425 Conventions for SMIv2", RFC 2579, April 1999. 1427 [7] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Conformance 1428 Statements for SMIv2", RFC 2580, April 1999. 1430 [8] Case, J., Fedor, M., Schoffstall, M., and Davin, J., "Simple 1431 Network Management Protocol", RFC 1157, May 1990. 1433 [9] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 1434 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 1436 [10] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport 1437 Mappings for Version 2 of the Simple Network Management Protocol 1438 (SNMPv2)", RFC 1906, January 1996. 1440 [11] Case, J., Harrington D., Presuhn R., and Wijnen, B., "Message 1441 Processing and Dispatching for the Simple Network Management 1442 Protocol (SNMP)", RFC 2572, April 1999. 1444 [12] Blumenthal, U., and Wijnen, B., "User-based Security Model (USM) 1445 for version 3 of the Simple Network Management Protocol (SNMPv3)", 1446 RFC 2574, April 1999. 1448 [13] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 1449 Operations for Version 2 of the Simple Network Management Protocol 1450 (SNMPv2)", RFC 1905, January 1996. 1452 [14] Levi, D., Meyer, P., and Stewart, B., "SNMPv3 Applications", RFC 1453 2573, April 1999. 1455 [15] Wijnen, B., Presuhn, R., and McCloghrie, K., "View-based Access 1456 Control Model (VACM) for the Simple Network Management Protocol 1457 (SNMP)", RFC 2575, April 1999. 1459 [16] Freed, N. and Kille, S., "The Network Services Monitoring MIB", 1460 Internet Draft, May 1999. 1462 [17] Kille, S., "A String Representation of Distinguished Names", RFC 1463 1779, March 1995. 1465 [18] Freed, N. and Kille, S., "Mail Monitoring MIB", RFC 2249, January 1466 1998. 1468 [19] Freed, N. and Kille, S., "Mail Monitoring MIB", RFC 1566, January 1469 1994. 1471 [20] Kille, S., "Mapping between X.400(1988) and RFC 822/MIME", RFC 1472 2156, January 1998. 1474 [21] Crocker, D., "Standard for the Format of ARPA Internet Text 1475 Message", STD 11, RFC 822, August 1982. 1477 [22] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893, 1478 January 1996. 1480 10. Security Considerations 1482 There are no management objects defined in this MIB that have a MAX- 1483 ACCESS clause of read-write and/or read-create. So, if this MIB is 1484 implemented correctly, then there is no risk that an intruder can alter 1485 or create any management objects of this MIB via direct SNMP SET 1486 operations. 1488 However, this MIB does provide passive information about the existence, 1489 type, and configuration of applications on a given host that could 1490 potentially indicate some sort of vulnerability. Finally, the 1491 information MIB provides about network usage could be used to analyze 1492 network traffic patterns. 1494 SNMPv1 by itself is not a secure environment. Even if the network 1495 itself is secure (for example by using IPSec), even then, there is no 1496 control as to who on the secure network is allowed to access and GET/SET 1497 (read/change/create/delete) the objects in this MIB. 1499 It is recommended that the implementers consider the security features 1500 as provided by the SNMPv3 framework. Specifically, the use of the 1501 User-based Security Model RFC 2574 [12] and the View-based Access 1502 Control Model RFC 2575 [15] is recommended. 1504 It is then a customer/user responsibility to ensure that the SNMP entity 1505 giving access to an instance of this MIB, is properly configured to give 1506 access to the objects only to those principals (users) that have 1507 legitimate rights to indeed GET or SET (change/create/delete) them. 1509 11. Author and Chair Addresses 1511 Ned Freed 1512 Innosoft International, Inc. 1513 1050 Lakes Drive 1514 West Covina, CA 91790 1515 USA 1516 tel: +1 626 919 3600 1517 fax: +1 626 919 3614 1518 email: ned.freed@innosoft.com 1520 Steve Kille, MADMAN WG Chair 1521 ISODE Consortium 1522 The Dome, The Square 1523 Richmond TW9 1DT 1524 UK 1525 tel: +44 181 332 9091 1526 email: S.Kille@isode.com 1528 12. Full Copyright Statement 1530 Copyright (C) The Internet Society (1999). All Rights Reserved. 1532 This document and translations of it may be copied and furnished to 1533 others, and derivative works that comment on or otherwise explain it or 1534 assist in its implementation may be prepared, copied, published and 1535 distributed, in whole or in part, without restriction of any kind, 1536 provided that the above copyright notice and this paragraph are included 1537 on all such copies and derivative works. However, this document itself 1538 may not be modified in any way, such as by removing the copyright notice 1539 or references to the Internet Society or other Internet organizations, 1540 except as needed for the purpose of developing Internet standards in 1541 which case the procedures for copyrights defined in the Internet 1542 Standards process must be followed, or as required to translate it into 1543 languages other than English. 1545 The limited permissions granted above are perpetual and will not be 1546 revoked by the Internet Society or its successors or assigns. 1548 This document and the information contained herein is provided on an "AS 1549 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1550 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1551 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1552 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1553 FITNESS FOR A PARTICULAR PURPOSE.