Debian Codegraph @

rfc2249.html

raw
1 <pre>Network Working Group N. Freed
2 Request for Comments: 2249 Innosoft
3 Obsoletes: <a href="./rfc1566">1566</a> S. Kille
4 Category: Standards Track ISODE Consortium
5 January 1998
6
7
8 <span class="h1">Mail Monitoring MIB</span>
9
10
11 Status of this Memo
12
13 This document specifies an Internet standards track protocol for the
14 Internet community, and requests discussion and suggestions for
15 improvements. Please refer to the current edition of the "Internet
16 Official Protocol Standards" (STD 1) for the standardization state
17 and status of this protocol. Distribution of this memo is unlimited.
18
19 Copyright Notice
20
21 Copyright (C) The Internet Society (1998). All Rights Reserved.
22
23 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
24
25 This memo defines a portion of the Management Information Base (MIB)
26 for use with network management protocols in the Internet community.
27 Specifically, this memo extends the basic Network Services Monitoring
28 MIB [<a href="#ref-8" title="&quot;The Network Services Monitoring MIB&quot;">8</a>] to allow monitoring of Message Transfer Agents (MTAs). It may
29 also be used to monitor MTA components within gateways.
30
31 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Table of Contents</span>
32
33 <a href="#section-1">1</a> Introduction ............................................. <a href="#page-1">1</a>
34 <a href="#section-2">2</a> Table of Contents ........................................ <a href="#page-1">1</a>
35 <a href="#section-3">3</a> The SNMPv2 Network Management Framework .................. <a href="#page-2">2</a>
36 <a href="#section-3.1">3.1</a> Object Definitions ..................................... <a href="#page-2">2</a>
37 <a href="#section-4">4</a> Message Flow Model ....................................... <a href="#page-2">2</a>
38 <a href="#section-5">5</a> MTA Objects .............................................. <a href="#page-3">3</a>
39 <a href="#section-6">6</a> Definitions .............................................. <a href="#page-4">4</a>
40 <a href="#section-7">7</a> Changes made since <a href="./rfc1566">RFC 1566</a> .............................. <a href="#page-25">25</a>
41 <a href="#section-8">8</a> Acknowledgements ......................................... <a href="#page-26">26</a>
42 <a href="#section-9">9</a> References ............................................... <a href="#page-26">26</a>
43 <a href="#section-10">10</a> Security Considerations ................................. <a href="#page-27">27</a>
44 <a href="#section-11">11</a> Author and Chair Addresses .............................. <a href="#page-27">27</a>
45 <a href="#section-12">12</a> Full Copyright Statement ................................ <a href="#page-28">28</a>
46
47
48
49
50
51
52 <span class="grey">Freed &amp; Kille Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
55
56
57 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The SNMPv2 Network Management Framework</span>
58
59 The SNMPv2 Network Management Framework consists of seven major
60 components. They are:
61
62 o <a href="./rfc1902">RFC 1902</a> [<a href="#ref-1" title="&quot;Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">1</a>] which defines the SMI, the mechanisms used for
63 describing and naming objects for the purpose of management.
64
65 o <a href="./rfc1903">RFC 1903</a> [<a href="#ref-2" title="&quot;Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">2</a>] defines textual conventions for SNMPv2.
66
67 o <a href="./rfc1904">RFC 1904</a> [<a href="#ref-3" title="&quot;Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">3</a>] defines conformance statements for SNMPv2.
68
69 o <a href="./rfc1905">RFC 1905</a> [<a href="#ref-4" title="&quot;Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">4</a>] defines transport mappings for SNMPv2.
70
71 o <a href="./rfc1906">RFC 1906</a> [<a href="#ref-5" title="&quot;Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">5</a>] defines the protocol operations used for network
72 access to managed objects.
73
74 o <a href="./rfc1907">RFC 1907</a> [<a href="#ref-6" title="&quot;Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">6</a>] defines the Management Information Base for SNMPv2.
75
76 o <a href="./rfc1908">RFC 1908</a> [<a href="#ref-7" title="&quot;Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework&quot;">7</a>] specifies coexistance between SNMP and SNMPv2.
77
78 The Framework permits new objects to be defined for the purpose of
79 experimentation and evaluation.
80
81 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Object Definitions</span>
82
83 Managed objects are accessed via a virtual information store, termed
84 the Management Information Base or MIB. Objects in the MIB are
85 defined using the subset of Abstract Syntax Notation One (ASN.1)
86 defined in the SMI. In particular, each object type is named by an
87 OBJECT IDENTIFIER, an administratively assigned name. The object type
88 together with an object instance serves to uniquely identify a
89 specific instantiation of the object. For human convenience, we
90 often use a textual string, termed the descriptor, to refer to the
91 object type.
92
93 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Message Flow Model</span>
94
95 A general model of message flow inside an MTA has to be presented
96 before a MIB can be described. Generally speaking, message flow is
97 modelled as occuring in four steps:
98
99 (1) Messages are received by the MTA from User Agents, Message
100 Stores, other MTAs, and gateways.
101
102 (2) The "next hop" for the each message is determined. This is
103 simply the destination the message is to be transmitted to; it
104 may or may not be the final destination of the message.
105
106
107
108 <span class="grey">Freed &amp; Kille Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
111
112
113 Multiple "next hops" may exist for a single message (as a
114 result of either having multiple recipients or distribution
115 list expansion); this may make it necessary to duplicate
116 messages.
117
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.
121
122 (4) Messages are transmitted to the appropriate destination, which
123 may be a User Agent, Message Store, another MTA, or gateway.
124
125 Storage of messages in the MTA occurs at some point during this
126 process. However, it is important to note that storage may occur at
127 different and possibly even multiple points during this process. For
128 example, some MTAs expand messages into multiple copies as they are
129 received. In this case (1), (2), and (3) may all occur prior to
130 storage. Other MTAs store messages precisely as they are received and
131 perform all expansions and conversions during retransmission
132 processing. So here only (1) occurs prior to storage. This leads to
133 situations where, in general, a measurement of messages received may
134 not equal a measurement of messages in store, or a measurement of
135 messages stored may not equal a measurement of messages
136 retransmitted, or both.
137
138 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. MTA Objects</span>
139
140 If there are one or more MTAs on the host, the following MIB may be
141 used to monitor them. Any number of the MTAs on a single host or
142 group of hosts may be monitored. Each MTA is dealt with as a separate
143 network service and has its own applTable entry in the Network
144 Services Monitoring MIB.
145
146 The MIB described in this document covers only the portion which is
147 specific to the monitoring of MTAs. The network service related part
148 of the MIB is covered in a separate document [<a href="#ref-8" title="&quot;The Network Services Monitoring MIB&quot;">8</a>].
149
150 This MIB defines four tables. The first of these contains per-MTA
151 information that isn't specific to any particular part of MTA. The
152 second breaks each MTA down into a collection of separate components
153 called groups. Groups are described in detail in the comments
154 embedded in the MIB below. The third table provides a means of
155 correlating associations tracked by the network services MIB with
156 specific groups within different MTAs. Finally, the fourth table
157 provides a means of tracking any errors encountered during the
158 operation of the MTA. The first two tables must be implemented to
159 conform with this MIB; the last two are optional.
160
161
162
163
164 <span class="grey">Freed &amp; Kille Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
167
168
169 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Definitions</span>
170
171 MTA-MIB DEFINITIONS ::= BEGIN
172
173 IMPORTS
174 OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2
175 FROM SNMPv2-SMI
176 DisplayString, TimeInterval
177 FROM SNMPv2-TC
178 MODULE-COMPLIANCE, OBJECT-GROUP
179 FROM SNMPv2-CONF
180 applIndex, URLString
181 FROM NETWORK-SERVICES-MIB;
182
183 mta MODULE-IDENTITY
184 LAST-UPDATED "9708170000Z"
185 ORGANIZATION "IETF Mail and Directory Management Working Group"
186 CONTACT-INFO
187 " Ned Freed
188
189 Postal: Innosoft International, Inc.
190 1050 Lakes Drive
191 West Covina, CA 91790
192 US
193
194 Tel: +1 626 919 3600
195 Fax: +1 626 919 3614
196
197 E-Mail: [email protected]"
198 DESCRIPTION
199 "The MIB module describing Message Transfer Agents (MTAs)"
200 REVISION "9311280000Z"
201 DESCRIPTION
202 "The original version of this MIB was published in <a href="./rfc1566">RFC 1566</a>"
203 ::= {mib-2 28}
204
205 mtaTable OBJECT-TYPE
206 SYNTAX SEQUENCE OF MtaEntry
207 MAX-ACCESS not-accessible
208 STATUS current
209 DESCRIPTION
210 "The table holding information specific to an MTA."
211 ::= {mta 1}
212
213 mtaStatusCode OBJECT-TYPE
214 SYNTAX INTEGER (4000000..5999999)
215 MAX-ACCESS not-accessible
216 STATUS current
217
218
219
220 <span class="grey">Freed &amp; Kille Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
223
224
225 DESCRIPTION
226 "An index capable of representing an Enhanced Mail System
227 Status Code. Enhanced Mail System Status Codes are
228 defined in <a href="./rfc1893">RFC 1893</a> [<a href="#ref-14" title="&quot;Enhanced Mail System Status Codes&quot;">14</a>]. These codes have the form
229
230 class.subject.detail
231
232 Here 'class' is either 2, 4, or 5 and both 'subject' and
233 'detail' are integers in the range 0..999. Given a status
234 code the corresponding index value is defined to be
235 ((class * 1000) + subject) * 1000 + detail. Both SMTP
236 error response codes and X.400 reason and diagnostic codes
237 can be mapped into these codes, resulting in a namespace
238 capable of describing most error conditions a mail system
239 encounters in a generic yet detailed way."
240 ::= {mta 6}
241
242 mtaEntry OBJECT-TYPE
243 SYNTAX MtaEntry
244 MAX-ACCESS not-accessible
245 STATUS current
246 DESCRIPTION
247 "The entry associated with each MTA."
248 INDEX {applIndex}
249 ::= {mtaTable 1}
250
251 MtaEntry ::= SEQUENCE {
252 mtaReceivedMessages
253 Counter32,
254 mtaStoredMessages
255 Gauge32,
256 mtaTransmittedMessages
257 Counter32,
258 mtaReceivedVolume
259 Counter32,
260 mtaStoredVolume
261 Gauge32,
262 mtaTransmittedVolume
263 Counter32,
264 mtaReceivedRecipients
265 Counter32,
266 mtaStoredRecipients
267 Gauge32,
268 mtaTransmittedRecipients
269 Counter32,
270 mtaSuccessfulConvertedMessages
271 Counter32,
272 mtaFailedConvertedMessages
273
274
275
276 <span class="grey">Freed &amp; Kille Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
279
280
281 Counter32,
282 mtaLoopsDetected
283 Counter32
284 }
285
286 mtaReceivedMessages OBJECT-TYPE
287 SYNTAX Counter32
288 MAX-ACCESS read-only
289 STATUS current
290 DESCRIPTION
291 "The number of messages received since MTA initialization.
292 This includes messages transmitted to this MTA from other
293 MTAs as well as messages that have been submitted to the
294 MTA directly by end-users or applications."
295 ::= {mtaEntry 1}
296
297 mtaStoredMessages OBJECT-TYPE
298 SYNTAX Gauge32
299 MAX-ACCESS read-only
300 STATUS current
301 DESCRIPTION
302 "The total number of messages currently stored in the MTA.
303 This includes messages that are awaiting transmission to
304 some other MTA or are waiting for delivery to an end-user
305 or application."
306 ::= {mtaEntry 2}
307
308 mtaTransmittedMessages OBJECT-TYPE
309 SYNTAX Counter32
310 MAX-ACCESS read-only
311 STATUS current
312 DESCRIPTION
313 "The number of messages transmitted since MTA initialization.
314 This includes messages that were transmitted to some other
315 MTA or are waiting for delivery to an end-user or
316 application."
317 ::= {mtaEntry 3}
318
319 mtaReceivedVolume OBJECT-TYPE
320 SYNTAX Counter32
321 UNITS "K-octets"
322 MAX-ACCESS read-only
323 STATUS current
324 DESCRIPTION
325 "The total volume of messages received since MTA
326 initialization, measured in kilo-octets. This volume should
327 include all transferred data that is logically above the mail
328 transport protocol level. For example, an SMTP-based MTA
329
330
331
332 <span class="grey">Freed &amp; Kille Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
335
336
337 should use the number of kilo-octets in the message header
338 and body, while an X.400-based MTA should use the number of
339 kilo-octets of P2 data. This includes messages transmitted
340 to this MTA from other MTAs as well as messages that have
341 been submitted to the MTA directly by end-users or
342 applications."
343 ::= {mtaEntry 4}
344
345 mtaStoredVolume OBJECT-TYPE
346 SYNTAX Gauge32
347 UNITS "K-octets"
348 MAX-ACCESS read-only
349 STATUS current
350 DESCRIPTION
351 "The total volume of messages currently stored in the MTA,
352 measured in kilo-octets. This volume should include all
353 stored data that is logically above the mail transport
354 protocol level. For example, an SMTP-based MTA should
355 use the number of kilo-octets in the message header and
356 body, while an X.400-based MTA would use the number of
357 kilo-octets of P2 data. This includes messages that are
358 awaiting transmission to some other MTA or are waiting
359 for delivery to an end-user or application."
360 ::= {mtaEntry 5}
361
362 mtaTransmittedVolume OBJECT-TYPE
363 SYNTAX Counter32
364 UNITS "K-octets"
365 MAX-ACCESS read-only
366 STATUS current
367 DESCRIPTION
368 "The total volume of messages transmitted since MTA
369 initialization, measured in kilo-octets. This volume should
370 include all transferred data that is logically above the mail
371 transport protocol level. For example, an SMTP-based MTA
372 should use the number of kilo-octets in the message header
373 and body, while an X.400-based MTA should use the number of
374 kilo-octets of P2 data. This includes messages that were
375 transmitted to some other MTA or are waiting for delivery
376 to an end-user or application."
377 ::= {mtaEntry 6}
378
379 mtaReceivedRecipients OBJECT-TYPE
380 SYNTAX Counter32
381 MAX-ACCESS read-only
382 STATUS current
383 DESCRIPTION
384 "The total number of recipients specified in all messages
385
386
387
388 <span class="grey">Freed &amp; Kille Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
391
392
393 received since MTA initialization. Recipients this MTA
394 has no responsibility for, i.e. inactive envelope
395 recipients or ones referred to in message headers,
396 should not be counted even if information about such
397 recipients is available. This includes messages
398 transmitted to this MTA from other MTAs as well as
399 messages that have been submitted to the MTA directly
400 by end-users or applications."
401 ::= {mtaEntry 7}
402
403 mtaStoredRecipients OBJECT-TYPE
404 SYNTAX Gauge32
405 MAX-ACCESS read-only
406 STATUS current
407 DESCRIPTION
408 "The total number of recipients specified in all messages
409 currently stored in the MTA. Recipients this MTA has no
410 responsibility for, i.e. inactive envelope recipients or
411 ones referred to in message headers, should not be
412 counted. This includes messages that are awaiting
413 transmission to some other MTA or are waiting for
414 delivery to an end-user or application."
415 ::= {mtaEntry 8}
416
417 mtaTransmittedRecipients OBJECT-TYPE
418 SYNTAX Counter32
419 MAX-ACCESS read-only
420 STATUS current
421 DESCRIPTION
422 "The total number of recipients specified in all messages
423 transmitted since MTA initialization. Recipients this
424 MTA had no responsibility for, i.e. inactive envelope
425 recipients or ones referred to in message headers,
426 should not be counted. This includes messages that were
427 transmitted to some other MTA or are waiting for
428 delivery to an end-user or application."
429 ::= {mtaEntry 9}
430
431 mtaSuccessfulConvertedMessages OBJECT-TYPE
432 SYNTAX Counter32
433 MAX-ACCESS read-only
434 STATUS current
435 DESCRIPTION
436 "The number of messages that have been successfully
437 converted from one form to another since MTA
438 initialization."
439 ::= {mtaEntry 10}
440
441
442
443
444 <span class="grey">Freed &amp; Kille Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
447
448
449 mtaFailedConvertedMessages OBJECT-TYPE
450 SYNTAX Counter32
451 MAX-ACCESS read-only
452 STATUS current
453 DESCRIPTION
454 "The number of messages for which an unsuccessful
455 attempt was made to convert them from one form to
456 another since MTA initialization."
457 ::= {mtaEntry 11}
458
459 mtaLoopsDetected OBJECT-TYPE
460 SYNTAX Counter32
461 MAX-ACCESS read-only
462 STATUS current
463 DESCRIPTION
464 "A message loop is defined as a situation where the MTA
465 decides that a given message will never be delivered to
466 one or more recipients and instead will continue to
467 loop endlessly through one or more MTAs. This variable
468 counts the number of times the MTA has detected such a
469 situation since MTA initialization. Note that the
470 mechanism MTAs use to detect loops (e.g. trace field
471 counting, count of references to this MTA in a trace
472 field, examination of DNS or other directory information,
473 etc.), the level at which loops are detected (e.g. per
474 message, per recipient, per directory entry, etc.), and
475 the handling of a loop once it is detected (e.g. looping
476 messages are held, looping messages are bounced or sent
477 to the postmaster, messages that the MTA knows will loop
478 won't be accepted, etc.) vary widely from one MTA to the
479 next and cannot be inferred from this variable."
480 ::= {mtaEntry 12}
481
482 -- MTAs typically group inbound reception, queue storage, and
483 -- outbound transmission in some way, rather than accounting for
484 -- such operations only across the MTA as a whole. In the most
485 -- extreme case separate information will be maintained for each
486 -- different entity that receives messages and for each entity
487 -- the MTA stores messages for and delivers messages to. Other
488 -- MTAs may elect to treat all reception equally, all queue
489 -- storage equally, all deliveries equally, or some combination
490 -- of this. Overlapped groupings are also possible, where an MTA
491 -- decomposes its traffic in different ways for different
492 -- purposes.
493
494 -- In any case, a grouping abstraction is an extremely useful for
495 -- breaking down the activities of an MTA. For purposes of
496 -- labelling this will be called a "group" in this MIB.
497
498
499
500 <span class="grey">Freed &amp; Kille Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
503
504
505 -- Each group contains all the variables needed to monitor all
506 -- aspects of an MTA's operation. However, the fact that all
507 -- groups contain all possible variables does not imply that all
508 -- groups must use all possible variables. For example, a single
509 -- group might be used to monitor only one kind of event (inbound
510 -- processing, outbound processing, or storage). In this sort of
511 -- configuration all unused counters would be inaccessible; e.g.,
512 -- returning either a noSuchName error (for an SNMPv1 get), or a
513 -- noSuchInstance exception (for an SNMPv2 get).
514
515 -- Groups can be created at any time after MTA initialization. Once
516 -- a group is created it should not be deleted or its mtaGroupIndex
517 -- changed unless the MTA is reinitialized.
518
519 -- Groups are not necessarily mutually exclusive. A given event may
520 -- be recorded by more than one group, a message may be seen as
521 -- stored by more than one group, and so on. Groups should be all
522 -- inclusive, however: if groups are implemented all aspects of an
523 -- MTA's operation should be registered in at least one group. This
524 -- freedom lets implementors use different sets of groups to
525 -- provide differents "views" of an MTA.
526
527 -- The possibility of overlap between groups means that summing
528 -- variables across groups may not produce values equal to those in
529 -- the mtaTable. mtaTable should always provide accurate information
530 -- about the MTA as a whole.
531
532 -- The term "channel" is often used in MTA implementations; channels
533 -- are usually, but not always, equivalent to a group. However,
534 -- this MIB does not use the term "channel" because there is no
535 -- requirement that an MTA supporting this MIB has to map its
536 -- "channel" abstraction one-to-one onto the MIB's group abstration.
537
538 -- An MTA may create a group or group of groups at any time. Once
539 -- created, however, an MTA cannot delete an entry for a group from
540 -- the group table. Deletation is only allowed when the MTA is
541 -- reinitialized, and is not required even then. This restriction
542 -- is imposed so that monitoring agents can rely on group
543 -- assignments being consistent across multiple query operations.
544
545 -- Groups may be laid out so as to form a hierarchical arrangement,
546 -- with some groups acting as subgroups for other groups.
547 -- Alternately, disjoint groups of groups may be used to provide
548 -- different sorts of "snapshots" of MTA operation. The
549 -- mtaGroupHierarchy variable provides an indication of how each
550 -- group fits into the overall arrangement being used.
551
552 mtaGroupTable OBJECT-TYPE
553
554
555
556 <span class="grey">Freed &amp; Kille Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
559
560
561 SYNTAX SEQUENCE OF MtaGroupEntry
562 MAX-ACCESS not-accessible
563 STATUS current
564 DESCRIPTION
565 "The table holding information specific to each MTA group."
566 ::= {mta 2}
567
568 mtaGroupEntry OBJECT-TYPE
569 SYNTAX MtaGroupEntry
570 MAX-ACCESS not-accessible
571 STATUS current
572 DESCRIPTION
573 "The entry associated with each MTA group."
574 INDEX {applIndex, mtaGroupIndex}
575 ::= {mtaGroupTable 1}
576
577 MtaGroupEntry ::= SEQUENCE {
578 mtaGroupIndex
579 INTEGER,
580 mtaGroupReceivedMessages
581 Counter32,
582 mtaGroupRejectedMessages
583 Counter32,
584 mtaGroupStoredMessages
585 Gauge32,
586 mtaGroupTransmittedMessages
587 Counter32,
588 mtaGroupReceivedVolume
589 Counter32,
590 mtaGroupStoredVolume
591 Gauge32,
592 mtaGroupTransmittedVolume
593 Counter32,
594 mtaGroupReceivedRecipients
595 Counter32,
596 mtaGroupStoredRecipients
597 Gauge32,
598 mtaGroupTransmittedRecipients
599 Counter32,
600 mtaGroupOldestMessageStored
601 TimeInterval,
602 mtaGroupInboundAssociations
603 Gauge32,
604 mtaGroupOutboundAssociations
605 Gauge32,
606 mtaGroupAccumulatedInboundAssociations
607 Counter32,
608 mtaGroupAccumulatedOutboundAssociations
609
610
611
612 <span class="grey">Freed &amp; Kille Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
615
616
617 Counter32,
618 mtaGroupLastInboundActivity
619 TimeInterval,
620 mtaGroupLastOutboundActivity
621 TimeInterval,
622 mtaGroupLastOutboundAssociationAttempt
623 TimeInterval,
624 mtaGroupRejectedInboundAssociations
625 Counter32,
626 mtaGroupFailedOutboundAssociations
627 Counter32,
628 mtaGroupInboundRejectionReason
629 DisplayString,
630 mtaGroupOutboundConnectFailureReason
631 DisplayString,
632 mtaGroupScheduledRetry
633 TimeInterval,
634 mtaGroupMailProtocol
635 OBJECT IDENTIFIER,
636 mtaGroupName
637 DisplayString,
638 mtaGroupSuccessfulConvertedMessages
639 Counter32,
640 mtaGroupFailedConvertedMessages
641 Counter32,
642 mtaGroupDescription
643 DisplayString,
644 mtaGroupURL
645 URLString,
646 mtaGroupCreationTime
647 TimeInterval,
648 mtaGroupHierarchy
649 INTEGER,
650 mtaGroupOldestMessageId
651 DisplayString,
652 mtaGroupLoopsDetected
653 Counter32
654 }
655
656 mtaGroupIndex OBJECT-TYPE
657 SYNTAX INTEGER (1..2147483647)
658 MAX-ACCESS not-accessible
659 STATUS current
660 DESCRIPTION
661 "The index associated with a group for a given MTA."
662 ::= {mtaGroupEntry 1}
663
664 mtaGroupReceivedMessages OBJECT-TYPE
665
666
667
668 <span class="grey">Freed &amp; Kille Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
671
672
673 SYNTAX Counter32
674 MAX-ACCESS read-only
675 STATUS current
676 DESCRIPTION
677 "The number of messages received to this group since
678 group creation."
679 ::= {mtaGroupEntry 2}
680
681 mtaGroupRejectedMessages OBJECT-TYPE
682 SYNTAX Counter32
683 MAX-ACCESS read-only
684 STATUS current
685 DESCRIPTION
686 "The number of messages rejected by this group since
687 group creation."
688 ::= {mtaGroupEntry 3}
689
690 mtaGroupStoredMessages OBJECT-TYPE
691 SYNTAX Gauge32
692 MAX-ACCESS read-only
693 STATUS current
694 DESCRIPTION
695 "The total number of messages currently stored in this
696 group's queue."
697 ::= {mtaGroupEntry 4}
698
699 mtaGroupTransmittedMessages OBJECT-TYPE
700 SYNTAX Counter32
701 MAX-ACCESS read-only
702 STATUS current
703 DESCRIPTION
704 "The number of messages transmitted by this group since
705 group creation."
706 ::= {mtaGroupEntry 5}
707
708 mtaGroupReceivedVolume OBJECT-TYPE
709 SYNTAX Counter32
710 UNITS "K-octets"
711 MAX-ACCESS read-only
712 STATUS current
713 DESCRIPTION
714 "The total volume of messages received to this group since
715 group creation, measured in kilo-octets. This volume
716 should include all transferred data that is logically above
717 the mail transport protocol level. For example, an
718 SMTP-based MTA should use the number of kilo-octets in the
719 message header and body, while an X.400-based MTA should use
720 the number of kilo-octets of P2 data."
721
722
723
724 <span class="grey">Freed &amp; Kille Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
727
728
729 ::= {mtaGroupEntry 6}
730
731 mtaGroupStoredVolume OBJECT-TYPE
732 SYNTAX Gauge32
733 UNITS "K-octets"
734 MAX-ACCESS read-only
735 STATUS current
736 DESCRIPTION
737 "The total volume of messages currently stored in this
738 group's queue, measured in kilo-octets. This volume should
739 include all stored data that is logically above the mail
740 transport protocol level. For example, an SMTP-based
741 MTA should use the number of kilo-octets in the message
742 header and body, while an X.400-based MTA would use the
743 number of kilo-octets of P2 data."
744 ::= {mtaGroupEntry 7}
745
746 mtaGroupTransmittedVolume OBJECT-TYPE
747 SYNTAX Counter32
748 UNITS "K-octets"
749 MAX-ACCESS read-only
750 STATUS current
751 DESCRIPTION
752 "The total volume of messages transmitted by this group
753 since group creation, measured in kilo-octets. This
754 volume should include all transferred data that is logically
755 above the mail transport protocol level. For example, an
756 SMTP-based MTA should use the number of kilo-octets in the
757 message header and body, while an X.400-based MTA should use
758 the number of kilo-octets of P2 data."
759 ::= {mtaGroupEntry 8}
760
761 mtaGroupReceivedRecipients OBJECT-TYPE
762 SYNTAX Counter32
763 MAX-ACCESS read-only
764 STATUS current
765 DESCRIPTION
766 "The total number of recipients specified in all messages
767 received to this group since group creation.
768 Recipients this MTA has no responsibility for should not
769 be counted."
770 ::= {mtaGroupEntry 9}
771
772 mtaGroupStoredRecipients OBJECT-TYPE
773 SYNTAX Gauge32
774 MAX-ACCESS read-only
775 STATUS current
776 DESCRIPTION
777
778
779
780 <span class="grey">Freed &amp; Kille Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
783
784
785 "The total number of recipients specified in all messages
786 currently stored in this group's queue. Recipients this
787 MTA has no responsibility for should not be counted."
788 ::= {mtaGroupEntry 10}
789
790 mtaGroupTransmittedRecipients OBJECT-TYPE
791 SYNTAX Counter32
792 MAX-ACCESS read-only
793 STATUS current
794 DESCRIPTION
795 "The total number of recipients specified in all messages
796 transmitted by this group since group creation.
797 Recipients this MTA had no responsibility for should not
798 be counted."
799 ::= {mtaGroupEntry 11}
800
801 mtaGroupOldestMessageStored OBJECT-TYPE
802 SYNTAX TimeInterval
803 MAX-ACCESS read-only
804 STATUS current
805 DESCRIPTION
806 "Time since the oldest message in this group's queue was
807 placed in the queue."
808 ::= {mtaGroupEntry 12}
809
810 mtaGroupInboundAssociations OBJECT-TYPE
811 SYNTAX Gauge32
812 MAX-ACCESS read-only
813 STATUS current
814 DESCRIPTION
815 "The number of current associations to the group, where the
816 group is the responder."
817 ::= {mtaGroupEntry 13}
818
819 mtaGroupOutboundAssociations OBJECT-TYPE
820 SYNTAX Gauge32
821 MAX-ACCESS read-only
822 STATUS current
823 DESCRIPTION
824 "The number of current associations to the group, where the
825 group is the initiator."
826 ::= {mtaGroupEntry 14}
827
828 mtaGroupAccumulatedInboundAssociations OBJECT-TYPE
829 SYNTAX Counter32
830 MAX-ACCESS read-only
831 STATUS current
832 DESCRIPTION
833
834
835
836 <span class="grey">Freed &amp; Kille Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
839
840
841 "The total number of associations to the group since
842 group creation, where the MTA was the responder."
843 ::= {mtaGroupEntry 15}
844
845 mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE
846 SYNTAX Counter32
847 MAX-ACCESS read-only
848 STATUS current
849 DESCRIPTION
850 "The total number of associations from the group since
851 group creation, where the MTA was the initiator."
852 ::= {mtaGroupEntry 16}
853
854 mtaGroupLastInboundActivity OBJECT-TYPE
855 SYNTAX TimeInterval
856 MAX-ACCESS read-only
857 STATUS current
858 DESCRIPTION
859 "Time since the last time that this group had an active
860 inbound association for purposes of message reception."
861 ::= {mtaGroupEntry 17}
862
863 mtaGroupLastOutboundActivity OBJECT-TYPE
864 SYNTAX TimeInterval
865 MAX-ACCESS read-only
866 STATUS current
867 DESCRIPTION
868 "Time since the last time that this group had a
869 successful outbound association for purposes of
870 message delivery."
871 ::= {mtaGroupEntry 18}
872
873 mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE
874 SYNTAX TimeInterval
875 MAX-ACCESS read-only
876 STATUS current
877 DESCRIPTION
878 "Time since the last time that this group attempted
879 to make an outbound association for purposes of
880 message delivery."
881 ::= {mtaGroupEntry 34}
882
883 mtaGroupRejectedInboundAssociations OBJECT-TYPE
884 SYNTAX Counter32
885 MAX-ACCESS read-only
886 STATUS current
887 DESCRIPTION
888 "The total number of inbound associations the group has
889
890
891
892 <span class="grey">Freed &amp; Kille Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
895
896
897 rejected, since group creation. Rejected associations
898 are not counted in the accumulated association totals."
899 ::= {mtaGroupEntry 19}
900
901 mtaGroupFailedOutboundAssociations OBJECT-TYPE
902 SYNTAX Counter32
903 MAX-ACCESS read-only
904 STATUS current
905 DESCRIPTION
906 "The total number associations where the group was the
907 initiator and association establishment has failed,
908 since group creation. Failed associations are
909 not counted in the accumulated association totals."
910 ::= {mtaGroupEntry 20}
911
912 mtaGroupInboundRejectionReason OBJECT-TYPE
913 SYNTAX DisplayString
914 MAX-ACCESS read-only
915 STATUS current
916 DESCRIPTION
917 "The failure reason, if any, for the last association this
918 group refused to respond to. An empty string indicates that
919 the last attempt was successful. If no association attempt
920 has been made since the MTA was initialized the value
921 should be 'never'."
922 ::= {mtaGroupEntry 21}
923
924 mtaGroupOutboundConnectFailureReason OBJECT-TYPE
925 SYNTAX DisplayString
926 MAX-ACCESS read-only
927 STATUS current
928 DESCRIPTION
929 "The failure reason, if any, for the last association attempt
930 this group initiated. An empty string indicates that the last
931 attempt was successful. If no association attempt has been
932 made since the MTA was initialized the value should be
933 'never'."
934 ::= {mtaGroupEntry 22}
935
936 mtaGroupScheduledRetry OBJECT-TYPE
937 SYNTAX TimeInterval
938 MAX-ACCESS read-only
939 STATUS current
940 DESCRIPTION
941 "The time when this group is scheduled to next attempt to
942 make an association."
943 ::= {mtaGroupEntry 23}
944
945
946
947
948 <span class="grey">Freed &amp; Kille Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
951
952
953 mtaGroupMailProtocol OBJECT-TYPE
954 SYNTAX OBJECT IDENTIFIER
955 MAX-ACCESS read-only
956 STATUS current
957 DESCRIPTION
958 "An identification of the protocol being used by this group.
959 For an group employing OSI protocols, this will be the
960 Application Context. For Internet applications, the IANA
961 maintains a registry of the OIDs which correspond to well-known
962 message transfer protocols. If the application protocol is
963 not listed in the registry, an OID value of the form
964 {applTCPProtoID port} or {applUDProtoID port} are used for
965 TCP-based and UDP-based protocols, respectively. In either
966 case 'port' corresponds to the primary port number being
967 used by the group. applTCPProtoID and applUDPProtoID are
968 defined in [<a href="#ref-8" title="&quot;The Network Services Monitoring MIB&quot;">8</a>]."
969 ::= {mtaGroupEntry 24}
970
971 mtaGroupName OBJECT-TYPE
972 SYNTAX DisplayString
973 MAX-ACCESS read-only
974 STATUS current
975 DESCRIPTION
976 "A descriptive name for the group. If this group connects to
977 a single remote MTA this should be the name of that MTA. If
978 this in turn is an Internet MTA this should be the domain
979 name. For an OSI MTA it should be the string encoded
980 distinguished name of the managed object using the format
981 defined in <a href="./rfc1779">RFC 1779</a> [<a href="#ref-9" title="&quot;A String Representation of Distinguished Names&quot;">9</a>]. For X.400(1984) MTAs which do not
982 have a Distinguished Name, the <a href="./rfc1327">RFC 1327</a> [<a href="#ref-12" title="&quot;Mapping between X.400(1988) / ISO 10021 and RFC 822&quot;">12</a>] syntax
983 'mta in globalid' should be used."
984 ::= {mtaGroupEntry 25}
985
986 mtaGroupSuccessfulConvertedMessages OBJECT-TYPE
987 SYNTAX Counter32
988 MAX-ACCESS read-only
989 STATUS current
990 DESCRIPTION
991 "The number of messages that have been successfully
992 converted from one form to another in this group
993 since group creation."
994 ::= {mtaGroupEntry 26}
995
996 mtaGroupFailedConvertedMessages OBJECT-TYPE
997 SYNTAX Counter32
998 MAX-ACCESS read-only
999 STATUS current
1000 DESCRIPTION
1001
1002
1003
1004 <span class="grey">Freed &amp; Kille Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
1007
1008
1009 "The number of messages for which an unsuccessful
1010 attempt was made to convert them from one form to
1011 another in this group since group creation."
1012 ::= {mtaGroupEntry 27}
1013
1014 mtaGroupDescription OBJECT-TYPE
1015 SYNTAX DisplayString
1016 MAX-ACCESS read-only
1017 STATUS current
1018 DESCRIPTION
1019 "A description of the group's purpose. This information is
1020 intended to identify the group in a status display."
1021 ::= {mtaGroupEntry 28}
1022
1023 mtaGroupURL OBJECT-TYPE
1024 SYNTAX URLString
1025 MAX-ACCESS read-only
1026 STATUS current
1027 DESCRIPTION
1028 "A URL pointing to a description of the group. This
1029 information is intended to identify and briefly describe
1030 the group in a status display."
1031 ::= {mtaGroupEntry 29}
1032
1033 mtaGroupCreationTime OBJECT-TYPE
1034 SYNTAX TimeInterval
1035 MAX-ACCESS read-only
1036 STATUS current
1037 DESCRIPTION
1038 "Time since this group was first created."
1039 ::= {mtaGroupEntry 30}
1040
1041 mtaGroupHierarchy OBJECT-TYPE
1042 SYNTAX INTEGER (-2147483648..2147483647)
1043 MAX-ACCESS read-only
1044 STATUS current
1045 DESCRIPTION
1046 "Describes how this group fits into the hierarchy. A
1047 positive value is interpreted as an mtaGroupIndex
1048 value for some other group whose variables include
1049 those of this group (and usually others). A negative
1050 value is interpreted as a group collection code: Groups
1051 with common negative hierarchy values comprise one
1052 particular breakdown of MTA activity as a whole. A
1053 zero value means that this MIB implementation doesn't
1054 implement hierarchy indicators and thus the overall
1055 group hierarchy cannot be determined."
1056 ::= {mtaGroupEntry 31}
1057
1058
1059
1060 <span class="grey">Freed &amp; Kille Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
1063
1064
1065 mtaGroupOldestMessageId OBJECT-TYPE
1066 SYNTAX DisplayString
1067 MAX-ACCESS read-only
1068 STATUS current
1069 DESCRIPTION
1070 "Message ID of the oldest message in the group's queue.
1071 Whenever possible this should be in the form of an
1072 <a href="./rfc822">RFC 822</a> [<a href="#ref-13" title="&quot;Standard for the Format of ARPA Internet Text Message&quot;">13</a>] msg-id; X.400 may convert X.400 message
1073 identifiers to this form by following the rules laid
1074 out in <a href="./rfc1327">RFC1327</a> [<a href="#ref-12" title="&quot;Mapping between X.400(1988) / ISO 10021 and RFC 822&quot;">12</a>]."
1075 ::= {mtaGroupEntry 32}
1076
1077 mtaGroupLoopsDetected OBJECT-TYPE
1078 SYNTAX Counter32
1079 MAX-ACCESS read-only
1080 STATUS current
1081 DESCRIPTION
1082 "A message loop is defined as a situation where the MTA
1083 decides that a given message will never be delivered to
1084 one or more recipients and instead will continue to
1085 loop endlessly through one or more MTAs. This variable
1086 counts the number of times the MTA has detected such a
1087 situation in conjunction with something associated with
1088 this group since group creation. Note that the
1089 mechanism MTAs use to detect loops (e.g. trace field
1090 counting, count of references to this MTA in a trace
1091 field, examination of DNS or other directory information,
1092 etc.), the level at which loops are detected (e.g. per
1093 message, per recipient, per directory entry, etc.), and
1094 the handling of a loop once it is detected (e.g. looping
1095 messages are held, looping messages are bounced or sent
1096 to the postmaster, messages that the MTA knows will loop
1097 won't be accepted, etc.) vary widely from one MTA to the
1098 next and cannot be inferred from this variable."
1099 ::= {mtaGroupEntry 33}
1100
1101 -- The mtaGroupAssociationTable provides a means of correlating
1102 -- entries in the network services association table with the
1103 -- MTA group responsible for the association.
1104
1105
1106 mtaGroupAssociationTable OBJECT-TYPE
1107 SYNTAX SEQUENCE OF MtaGroupAssociationEntry
1108 MAX-ACCESS not-accessible
1109 STATUS current
1110 DESCRIPTION
1111 "The table holding information regarding the associations
1112 for each MTA group."
1113
1114
1115
1116 <span class="grey">Freed &amp; Kille Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
1119
1120
1121 ::= {mta 3}
1122
1123 mtaGroupAssociationEntry OBJECT-TYPE
1124 SYNTAX MtaGroupAssociationEntry
1125 MAX-ACCESS not-accessible
1126 STATUS current
1127 DESCRIPTION
1128 "The entry holding information regarding the associations
1129 for each MTA group."
1130 INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex}
1131 ::= {mtaGroupAssociationTable 1}
1132
1133 MtaGroupAssociationEntry ::= SEQUENCE {
1134 mtaGroupAssociationIndex
1135 INTEGER
1136 }
1137
1138 mtaGroupAssociationIndex OBJECT-TYPE
1139 SYNTAX INTEGER (1..2147483647)
1140 MAX-ACCESS read-only
1141 STATUS current
1142 DESCRIPTION
1143 "Reference into association table to allow correlation of
1144 this group's active associations with the association table."
1145 ::= {mtaGroupAssociationEntry 1}
1146
1147 -- The mtaGroupErrorTable gives each group a way of tallying
1148 -- the specific errors it has encountered. The mechanism
1149 -- defined here uses <a href="./rfc1893">RFC 1893</a> [<a href="#ref-14" title="&quot;Enhanced Mail System Status Codes&quot;">14</a>] status codes to identify
1150 -- various specific errors. There are also classes for generic
1151 -- errors of various sorts, and the entire mechanism is also
1152 -- extensible, in that new error codes can be defined at any
1153 -- time.
1154
1155 mtaGroupErrorTable OBJECT-TYPE
1156 SYNTAX SEQUENCE OF MtaGroupErrorEntry
1157 MAX-ACCESS not-accessible
1158 STATUS current
1159 DESCRIPTION
1160 "The table holding information regarding accumulated errors
1161 for each MTA group."
1162 ::= {mta 5}
1163
1164 mtaGroupErrorEntry OBJECT-TYPE
1165 SYNTAX MtaGroupErrorEntry
1166 MAX-ACCESS not-accessible
1167 STATUS current
1168 DESCRIPTION
1169
1170
1171
1172 <span class="grey">Freed &amp; Kille Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
1175
1176
1177 "The entry holding information regarding accumulated
1178 errors for each MTA group."
1179 INDEX {applIndex, mtaGroupIndex, mtaStatusCode}
1180 ::= {mtaGroupErrorTable 1}
1181
1182 MtaGroupErrorEntry ::= SEQUENCE {
1183 mtaGroupInboundErrorCount
1184 Counter32,
1185 mtaGroupInternalErrorCount
1186 Counter32,
1187 mtaGroupOutboundErrorCount
1188 Counter32
1189 }
1190
1191 mtaGroupInboundErrorCount OBJECT-TYPE
1192 SYNTAX Counter32
1193 MAX-ACCESS read-only
1194 STATUS current
1195 DESCRIPTION
1196 "Count of the number of errors of a given type that have
1197 been accumulated in assocation with a particular group
1198 while processing incoming messages. In the case of SMTP
1199 these will typically be errors reporting by an SMTP
1200 server to the remote client; in the case of X.400
1201 these will typically be errors encountered while
1202 processing an incoming message."
1203 ::= {mtaGroupErrorEntry 1}
1204
1205
1206 mtaGroupInternalErrorCount OBJECT-TYPE
1207 SYNTAX Counter32
1208 MAX-ACCESS read-only
1209 STATUS current
1210 DESCRIPTION
1211 "Count of the number of errors of a given type that have
1212 been accumulated in assocation with a particular group
1213 during internal MTA processing."
1214 ::= {mtaGroupErrorEntry 2}
1215
1216 mtaGroupOutboundErrorCount OBJECT-TYPE
1217 SYNTAX Counter32
1218 MAX-ACCESS read-only
1219 STATUS current
1220 DESCRIPTION
1221 "Count of the number of errors of a given type that have
1222 been accumulated in assocation with a particular group's
1223 outbound connection activities. In the case of an SMTP
1224 client these will typically be errors reported while
1225
1226
1227
1228 <span class="grey">Freed &amp; Kille Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
1231
1232
1233 attempting to contact or while communicating with the
1234 remote SMTP server. In the case of X.400 these will
1235 typically be errors encountered while constructing
1236 or attempting to deliver an outgoing message."
1237 ::= {mtaGroupErrorEntry 3}
1238
1239 -- Conformance information
1240
1241 mtaConformance OBJECT IDENTIFIER ::= {mta 4}
1242
1243 mtaGroups OBJECT IDENTIFIER ::= {mtaConformance 1}
1244 mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2}
1245
1246 -- Compliance statements
1247
1248 mtaCompliance MODULE-COMPLIANCE
1249 STATUS current
1250 DESCRIPTION
1251 "The compliance statement for SNMPv2 entities which
1252 implement the Mail Monitoring MIB for basic
1253 monitoring of MTAs."
1254 MODULE -- this module
1255 MANDATORY-GROUPS {mtaGroup}
1256 ::= {mtaCompliances 1}
1257
1258 mtaAssocCompliance MODULE-COMPLIANCE
1259 STATUS current
1260 DESCRIPTION
1261 "The compliance statement for SNMPv2 entities which
1262 implement the Mail Monitoring MIB for monitoring of
1263 MTAs and their associations."
1264 MODULE -- this module
1265 MANDATORY-GROUPS {mtaGroup, mtaAssocGroup}
1266 ::= {mtaCompliances 2}
1267
1268 mtaErrorCompliance MODULE-COMPLIANCE
1269 STATUS current
1270 DESCRIPTION
1271 "The compliance statement for SNMPv2 entities which
1272 implement the Mail Monitoring MIB for monitoring of
1273 MTAs and detailed errors."
1274 MODULE -- this module
1275 MANDATORY-GROUPS {mtaGroup, mtaErrorGroup}
1276 ::= {mtaCompliances 3}
1277
1278 mtaFullCompliance MODULE-COMPLIANCE
1279 STATUS current
1280 DESCRIPTION
1281
1282
1283
1284 <span class="grey">Freed &amp; Kille Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
1287
1288
1289 "The compliance statement for SNMPv2 entities which
1290 implement the full Mail Monitoring MIB for monitoring
1291 of MTAs, associations, and detailed errors."
1292 MODULE -- this module
1293 MANDATORY-GROUPS {mtaGroup, mtaAssocGroup, mtaErrorGroup}
1294 ::= {mtaCompliances 4}
1295
1296 -- Units of conformance
1297
1298 mtaGroup OBJECT-GROUP
1299 OBJECTS {
1300 mtaReceivedMessages, mtaStoredMessages,
1301 mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1302 mtaTransmittedVolume, mtaReceivedRecipients,
1303 mtaStoredRecipients, mtaTransmittedRecipients,
1304 mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
1305 mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1306 mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1307 mtaGroupReceivedVolume, mtaGroupStoredVolume,
1308 mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1309 mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1310 mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1311 mtaGroupOutboundAssociations, mtaLoopsDetected,
1312 mtaGroupAccumulatedInboundAssociations,
1313 mtaGroupAccumulatedOutboundAssociations,
1314 mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1315 mtaGroupLastOutboundAssociationAttempt,
1316 mtaGroupRejectedInboundAssociations,
1317 mtaGroupFailedOutboundAssociations,
1318 mtaGroupInboundRejectionReason,
1319 mtaGroupOutboundConnectFailureReason,
1320 mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName,
1321 mtaGroupSuccessfulConvertedMessages,
1322 mtaGroupFailedConvertedMessages, mtaGroupDescription,
1323 mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy,
1324 mtaGroupOldestMessageId, mtaGroupLoopsDetected}
1325 STATUS current
1326 DESCRIPTION
1327 "A collection of objects providing basic monitoring of MTAs."
1328 ::= {mtaGroups 1}
1329
1330 mtaAssocGroup OBJECT-GROUP
1331 OBJECTS {
1332 mtaGroupAssociationIndex}
1333 STATUS current
1334 DESCRIPTION
1335 "A collection of objects providing monitoring of MTA
1336 associations."
1337
1338
1339
1340 <span class="grey">Freed &amp; Kille Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
1343
1344
1345 ::= {mtaGroups 2}
1346
1347 mtaErrorGroup OBJECT-GROUP
1348 OBJECTS {
1349 mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
1350 mtaGroupOutboundErrorCount}
1351 STATUS current
1352 DESCRIPTION
1353 "A collection of objects providing monitoring of
1354 detailed MTA errors."
1355 ::= {mtaGroups 3}
1356
1357 END
1358
1359 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Changes made since <a href="./rfc1566">RFC 1566</a></span>
1360
1361 The only changes made to this document since it was issued as <a href="./rfc1566">RFC</a>
1362 <a href="./rfc1566">1566</a> [<a href="#ref-11" title="&quot;Mail Monitoring MIB&quot;">11</a>] are the following:
1363
1364 (1) A number of DESCRIPTION fields have been reworded, hopefully
1365 making them clearer.
1366
1367 (2) mtaGroupDescription and mtaGroupURL fields have been added.
1368 These fields are intended to identify and describe the MTA and
1369 the various MTA groups.
1370
1371 (3) The time since the last outbound association attempt is now
1372 distinct from the time since the last successfuol outbound
1373 association attempt.
1374
1375 (4) Conversion operation counters have been added.
1376
1377 (5) A mechanism to explicitly describe group hierarchies has been
1378 added.
1379
1380 (6) A mechanism to count specific sorts of errors has been added.
1381
1382 (7) A field for the ID of the oldest message in a group's queue
1383 has been added.
1384
1385 (8) Per-MTA and per-group message loop counters have been added.
1386
1387 (9) A new table has been added to keep track of any errors an MTA
1388 encounters.
1389
1390
1391
1392
1393
1394
1395
1396 <span class="grey">Freed &amp; Kille Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
1399
1400
1401 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span>
1402
1403 This document is a work product of the Mail and Directory Management
1404 (MADMAN) Working Group of the IETF. It is based on an earlier MIB
1405 designed by S. Kille, T. Lenggenhager, D. Partain, and W. Yeong. The
1406 Electronic Mail Association's TSC committee was instrumental in
1407 providing feedback on and suggesting enhancements to <a href="./rfc1566">RFC 1566</a> [<a href="#ref-11" title="&quot;Mail Monitoring MIB&quot;">11</a>]
1408 that have led to the present document.
1409
1410 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
1411
1412 [<a id="ref-1">1</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
1413 S. Waldbusser, "Structure of Management Information for Version
1414 2 of the Simple Network Management Protocol (SNMPv2)", <a href="./rfc1902">RFC 1902</a>,
1415 January 1996.
1416
1417 [<a id="ref-2">2</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
1418 S. Waldbusser, "Textual Conventions for Version 2 of the Simple
1419 Network Management Protocol (SNMPv2)", <a href="./rfc1903">RFC 1903</a>, January 1996.
1420
1421 [<a id="ref-3">3</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
1422 S. Waldbusser, "Conformance Statements for Version 2 of the
1423 Simple Network Management Protocol (SNMPv2)", <a href="./rfc1904">RFC 1904</a>, January
1424 1996.
1425
1426 [<a id="ref-4">4</a>] SNMPv2 Working Grou, Case, J., McCloghrie, K., Rose, M., and
1427 S. Waldbusser, "Protocol Operations for Version 2 of the Simple
1428 Network Management Protocol (SNMPv2)", <a href="./rfc1905">RFC 1905</a>, January 1996.
1429
1430 [<a id="ref-5">5</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
1431 S. Waldbusser, "Transport Mappings for Version 2 of the Simple
1432 Network Management Protocol (SNMPv2)", <a href="./rfc1906">RFC 1906</a>, January 1996.
1433
1434 [<a id="ref-6">6</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
1435 S. Waldbusser, "Management Information Base for Version 2 of the
1436 Simple Network Management Protocol (SNMPv2)", <a href="./rfc1907">RFC 1907</a>, January
1437 1996.
1438
1439 [<a id="ref-7">7</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
1440 S. Waldbusser, "Coexistence between Version 1 and Version 2 of
1441 the Internet-standard Network Management Framework", <a href="./rfc1908">RFC 1908</a>,
1442 January 1996.
1443
1444 [<a id="ref-8">8</a>] Freed, N., and S. Kille, "The Network Services Monitoring MIB",
1445 <a href="./rfc2248">RFC 2248</a>, January 1998.
1446
1447 [<a id="ref-9">9</a>] Kille, S., "A String Representation of Distinguished Names", <a href="./rfc1779">RFC</a>
1448 <a href="./rfc1779">1779</a>, March 1995.
1449
1450
1451
1452 <span class="grey">Freed &amp; Kille Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
1455
1456
1457 [<a id="ref-10">10</a>] Berners-Lee, T., Masinter, L. and M. McCahill, Uniform Resource
1458 Locators (URL)", <a href="./rfc1738">RFC 1738</a>, December 1994.
1459
1460 [<a id="ref-11">11</a>] Freed, N. and S. Kille, "Mail Monitoring MIB", <a href="./rfc1566">RFC 1566</a>, January
1461 1994.
1462
1463 [<a id="ref-12">12</a>] Kille, S., "Mapping between X.400(1988) / ISO 10021 and <a href="./rfc822">RFC</a>
1464 <a href="./rfc822">822</a>", <a href="./rfc1327">RFC 1327</a>, May 1992.
1465
1466 [<a id="ref-13">13</a>] Crocker, D., "Standard for the Format of ARPA Internet Text
1467 Message", <a href="./rfc822">RFC 822</a>, August 1982.
1468
1469 [<a id="ref-14">14</a>] Vaudreuil, G., "Enhanced Mail System Status Codes", <a href="./rfc1893">RFC 1893</a>,
1470 January 1996.
1471
1472 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span>
1473
1474 This MIB does not offer write access, and as such cannot be used to
1475 actively attack a system. However, this MIB does provide passive
1476 information about the existance, type, and configuration of
1477 applications on a given host that could potentially indicate some
1478 sort of vulnerability. Finally, the information MIB provides about
1479 network usage could be used to analyze network traffic patterns.
1480
1481 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Author and Chair Addresses</span>
1482
1483 Ned Freed
1484 Innosoft International, Inc.
1485 1050 Lakes Drive
1486 West Covina, CA 91790
1487 USA
1488
1489 Phone: +1 626 919 3600
1490 Fax: +1 626 919 3614
1491 EMail: [email protected]
1492
1493
1494 Steve Kille, MADMAN WG Chair
1495 ISODE Consortium
1496 The Dome, The Square
1497 Richmond TW9 1DT
1498 UK
1499
1500 Phone: +44 181 332 9091
1501 EMail: [email protected]
1502
1503
1504
1505
1506
1507
1508 <span class="grey">Freed &amp; Kille Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc2249">RFC 2249</a> Mail Monitoring MIB January 1998</span>
1511
1512
1513 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Full Copyright Statement</span>
1514
1515 Copyright (C) The Internet Society (1998). All Rights Reserved.
1516
1517 This document and translations of it may be copied and furnished to
1518 others, and derivative works that comment on or otherwise explain it
1519 or assist in its implementation may be prepared, copied, published
1520 and distributed, in whole or in part, without restriction of any
1521 kind, provided that the above copyright notice and this paragraph
1522 are included on all such copies and derivative works. However, this
1523 document itself may not be modified in any way, such as by removing
1524 the copyright notice or references to the Internet Society or other
1525 Internet organizations, except as needed for the purpose of
1526 developing Internet standards in which case the procedures for
1527 copyrights defined in the Internet Standards process must be
1528 followed, or as required to translate it into languages other than
1529 English.
1530
1531 The limited permissions granted above are perpetual and will not be
1532 revoked by the Internet Society or its successors or assigns.
1533
1534 This document and the information contained herein is provided on an
1535 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
1536 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
1537 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
1538 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
1539 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1540 RPO
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564 Freed &amp; Kille Standards Track [Page 28]
1565 </pre>