« back to all changes in this revision
Viewing changes to mibs/MTA-MIB.txt
- browse files at revision 34
- compare with another revision
- download diff
- download tarball
- view history from revision 34
- Committer: Steve Langasek
- Date: 2009-12-12 05:48:22 UTC
- mfrom: (1.2.2 upstream)
- Revision ID: steve.langasek@canonical.com-20091212054822-5tiq0n03rhsio24a
Repackage upstream tarball to re-add the MIBs: even if they are not
modifiable (which is questionable), this is not a reason to keep them
out of Ubuntu main.
modifiable (which is questionable), this is not a reason to keep them
out of Ubuntu main.
- files added:
- mibs/AGENTX-MIB.txt
- files modified:
- debian/changelog
added
removed
mibs/MTA-MIB.txt
1
MTA-MIB DEFINITIONS ::= BEGIN
2
3
IMPORTS
4
OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2
5
FROM SNMPv2-SMI
6
TimeInterval
7
FROM SNMPv2-TC
8
MODULE-COMPLIANCE, OBJECT-GROUP
9
FROM SNMPv2-CONF
10
SnmpAdminString
11
FROM SNMP-FRAMEWORK-MIB
12
applIndex, URLString
13
FROM NETWORK-SERVICES-MIB;
14
15
mta MODULE-IDENTITY
16
LAST-UPDATED "200003030000Z"
17
ORGANIZATION "IETF Mail and Directory Management Working Group"
18
CONTACT-INFO
19
" Ned Freed
20
21
Postal: Innosoft International, Inc.
22
1050 Lakes Drive
23
West Covina, CA 91790
24
US
25
26
Tel: +1 626 919 3600
27
Fax: +1 626 919 3614
28
29
E-Mail: ned.freed@innosoft.com"
30
DESCRIPTION
31
"The MIB module describing Message Transfer Agents (MTAs)"
32
REVISION "200003030000Z"
33
DESCRIPTION
34
"This revision, published in RFC 2789, changes a number of
35
DisplayStrings to SnmpAdminStrings. Note that this change
36
37
is not strictly supported by SMIv2. However, the alternative
38
of deprecating the old objects and defining new objects
39
would have a more adverse impact on backward compatibility
40
and interoperability, given the particular semantics of
41
these objects. The defining reference for distinguished
42
names has also been updated from RFC 1779 to RFC 2253."
43
REVISION "199905120000Z"
44
DESCRIPTION
45
"This revision fixes a number of technical problems found in
46
previous versions: The conformance groups for different
47
versions of this MIB have been corrected, the recommendation
48
that an empty string be returned if the last operation was
49
successful has been removed from
50
mtaGroupInboundRejectionReason and
51
mtaGroupOutboundConnectFailureReason as it conflicts
52
with the stated purpose of these variables, and the
53
required mtaStatusCode entry has been added to
54
MtaGroupErrorEntry. It should be noted that this last
55
change in no way affects the bits on the wire."
56
REVISION "199708170000Z"
57
DESCRIPTION
58
"This revision, published in RFC 2249, adds the
59
mtaGroupDescription and mtaGroupURL fields, conversion
60
operation counters, a group hierarchy description mechanism,
61
counters for specific errors, oldest message IDs, per-MTA
62
and per-group loop counters, and a new table for tracking
63
any errors an MTA encounters."
64
REVISION "199311280000Z"
65
DESCRIPTION
66
"The original version of this MIB was published in RFC 1566"
67
::= {mib-2 28}
68
69
mtaTable OBJECT-TYPE
70
SYNTAX SEQUENCE OF MtaEntry
71
MAX-ACCESS not-accessible
72
STATUS current
73
DESCRIPTION
74
"The table holding information specific to an MTA."
75
::= {mta 1}
76
77
mtaEntry OBJECT-TYPE
78
SYNTAX MtaEntry
79
MAX-ACCESS not-accessible
80
STATUS current
81
DESCRIPTION
82
"The entry associated with each MTA."
83
INDEX {applIndex}
84
::= {mtaTable 1}
85
86
MtaEntry ::= SEQUENCE {
87
mtaReceivedMessages
88
Counter32,
89
mtaStoredMessages
90
Gauge32,
91
mtaTransmittedMessages
92
Counter32,
93
mtaReceivedVolume
94
Counter32,
95
mtaStoredVolume
96
Gauge32,
97
mtaTransmittedVolume
98
Counter32,
99
mtaReceivedRecipients
100
Counter32,
101
mtaStoredRecipients
102
Gauge32,
103
mtaTransmittedRecipients
104
Counter32,
105
mtaSuccessfulConvertedMessages
106
Counter32,
107
mtaFailedConvertedMessages
108
Counter32,
109
mtaLoopsDetected
110
Counter32
111
}
112
113
mtaReceivedMessages OBJECT-TYPE
114
SYNTAX Counter32
115
MAX-ACCESS read-only
116
STATUS current
117
DESCRIPTION
118
"The number of messages received since MTA initialization.
119
This includes messages transmitted to this MTA from other
120
MTAs as well as messages that have been submitted to the
121
MTA directly by end-users or applications."
122
::= {mtaEntry 1}
123
124
mtaStoredMessages OBJECT-TYPE
125
SYNTAX Gauge32
126
MAX-ACCESS read-only
127
STATUS current
128
DESCRIPTION
129
"The total number of messages currently stored in the MTA.
130
This includes messages that are awaiting transmission to
131
some other MTA or are waiting for delivery to an end-user
132
or application."
133
::= {mtaEntry 2}
134
135
mtaTransmittedMessages OBJECT-TYPE
136
SYNTAX Counter32
137
MAX-ACCESS read-only
138
STATUS current
139
DESCRIPTION
140
"The number of messages transmitted since MTA initialization.
141
This includes messages that were transmitted to some other
142
MTA or are waiting for delivery to an end-user or
143
application."
144
::= {mtaEntry 3}
145
146
mtaReceivedVolume OBJECT-TYPE
147
SYNTAX Counter32
148
UNITS "K-octets"
149
MAX-ACCESS read-only
150
STATUS current
151
DESCRIPTION
152
"The total volume of messages received since MTA
153
initialization, measured in kilo-octets. This volume should
154
include all transferred data that is logically above the mail
155
transport protocol level. For example, an SMTP-based MTA
156
should use the number of kilo-octets in the message header
157
and body, while an X.400-based MTA should use the number of
158
kilo-octets of P2 data. This includes messages transmitted
159
to this MTA from other MTAs as well as messages that have
160
been submitted to the MTA directly by end-users or
161
applications."
162
::= {mtaEntry 4}
163
164
mtaStoredVolume OBJECT-TYPE
165
SYNTAX Gauge32
166
UNITS "K-octets"
167
MAX-ACCESS read-only
168
STATUS current
169
DESCRIPTION
170
"The total volume of messages currently stored in the MTA,
171
measured in kilo-octets. This volume should include all
172
stored data that is logically above the mail transport
173
protocol level. For example, an SMTP-based MTA should
174
use the number of kilo-octets in the message header and
175
body, while an X.400-based MTA would use the number of
176
kilo-octets of P2 data. This includes messages that are
177
awaiting transmission to some other MTA or are waiting
178
for delivery to an end-user or application."
179
::= {mtaEntry 5}
180
181
mtaTransmittedVolume OBJECT-TYPE
182
SYNTAX Counter32
183
UNITS "K-octets"
184
MAX-ACCESS read-only
185
STATUS current
186
DESCRIPTION
187
"The total volume of messages transmitted since MTA
188
initialization, measured in kilo-octets. This volume should
189
include all transferred data that is logically above the mail
190
transport protocol level. For example, an SMTP-based MTA
191
should use the number of kilo-octets in the message header
192
and body, while an X.400-based MTA should use the number of
193
kilo-octets of P2 data. This includes messages that were
194
transmitted to some other MTA or are waiting for delivery
195
to an end-user or application."
196
::= {mtaEntry 6}
197
198
mtaReceivedRecipients OBJECT-TYPE
199
SYNTAX Counter32
200
MAX-ACCESS read-only
201
STATUS current
202
DESCRIPTION
203
"The total number of recipients specified in all messages
204
received since MTA initialization. Recipients this MTA
205
has no responsibility for, i.e. inactive envelope
206
recipients or ones referred to in message headers,
207
should not be counted even if information about such
208
recipients is available. This includes messages
209
transmitted to this MTA from other MTAs as well as
210
messages that have been submitted to the MTA directly
211
by end-users or applications."
212
::= {mtaEntry 7}
213
214
mtaStoredRecipients OBJECT-TYPE
215
SYNTAX Gauge32
216
MAX-ACCESS read-only
217
STATUS current
218
DESCRIPTION
219
"The total number of recipients specified in all messages
220
currently stored in the MTA. Recipients this MTA has no
221
responsibility for, i.e. inactive envelope recipients or
222
ones referred to in message headers, should not be
223
counted. This includes messages that are awaiting
224
transmission to some other MTA or are waiting for
225
delivery to an end-user or application."
226
::= {mtaEntry 8}
227
228
mtaTransmittedRecipients OBJECT-TYPE
229
SYNTAX Counter32
230
MAX-ACCESS read-only
231
STATUS current
232
DESCRIPTION
233
"The total number of recipients specified in all messages
234
transmitted since MTA initialization. Recipients this
235
MTA had no responsibility for, i.e. inactive envelope
236
recipients or ones referred to in message headers,
237
should not be counted. This includes messages that were
238
transmitted to some other MTA or are waiting for
239
delivery to an end-user or application."
240
::= {mtaEntry 9}
241
242
mtaSuccessfulConvertedMessages OBJECT-TYPE
243
SYNTAX Counter32
244
MAX-ACCESS read-only
245
STATUS current
246
DESCRIPTION
247
"The number of messages that have been successfully
248
converted from one form to another since MTA
249
initialization."
250
::= {mtaEntry 10}
251
252
mtaFailedConvertedMessages OBJECT-TYPE
253
SYNTAX Counter32
254
MAX-ACCESS read-only
255
STATUS current
256
DESCRIPTION
257
"The number of messages for which an unsuccessful
258
attempt was made to convert them from one form to
259
another since MTA initialization."
260
::= {mtaEntry 11}
261
262
mtaLoopsDetected OBJECT-TYPE
263
SYNTAX Counter32
264
MAX-ACCESS read-only
265
STATUS current
266
DESCRIPTION
267
"A message loop is defined as a situation where the MTA
268
decides that a given message will never be delivered to
269
one or more recipients and instead will continue to
270
loop endlessly through one or more MTAs. This variable
271
counts the number of times the MTA has detected such a
272
situation since MTA initialization. Note that the
273
mechanism MTAs use to detect loops (e.g., trace field
274
counting, count of references to this MTA in a trace
275
field, examination of DNS or other directory information,
276
etc.), the level at which loops are detected (e.g., per
277
message, per recipient, per directory entry, etc.), and
278
the handling of a loop once it is detected (e.g., looping
279
280
messages are held, looping messages are bounced or sent
281
to the postmaster, messages that the MTA knows will loop
282
won't be accepted, etc.) vary widely from one MTA to the
283
next and cannot be inferred from this variable."
284
::= {mtaEntry 12}
285
286
-- MTAs typically group inbound reception, queue storage, and
287
-- outbound transmission in some way, rather than accounting for
288
-- such operations only across the MTA as a whole. In the most
289
-- extreme case separate information will be maintained for each
290
-- different entity that receives messages and for each entity
291
-- the MTA stores messages for and delivers messages to. Other
292
-- MTAs may elect to treat all reception equally, all queue
293
-- storage equally, all deliveries equally, or some combination
294
-- of this. Overlapped groupings are also possible, where an MTA
295
-- decomposes its traffic in different ways for different
296
-- purposes.
297
298
-- In any case, a grouping abstraction is an extremely useful for
299
-- breaking down the activities of an MTA. For purposes of
300
-- labelling this will be called a "group" in this MIB.
301
302
-- Each group contains all the variables needed to monitor all
303
-- aspects of an MTA's operation. However, the fact that all
304
-- groups contain all possible variables does not imply that all
305
-- groups must use all possible variables. For example, a single
306
-- group might be used to monitor only one kind of event (inbound
307
-- processing, outbound processing, or storage). In this sort of
308
-- configuration any counters that are unused as a result of a
309
-- given MTA's use of the group construct must be inaccessible;
310
-- e.g., returning either a noSuchName error (for an SNMPv1 get),
311
-- or a noSuchInstance exception (for an SNMPv2 get).
312
313
-- Groups can be created at any time after MTA initialization. Once
314
-- a group is created it should not be deleted or its mtaGroupIndex
315
-- changed unless the MTA is reinitialized.
316
317
-- Groups are not necessarily mutually exclusive. A given event may
318
-- be recorded by more than one group, a message may be seen as
319
-- stored by more than one group, and so on. Groups should be all
320
-- inclusive, however: if groups are implemented all aspects of an
321
-- MTA's operation should be registered in at least one group.
322
-- This freedom lets implementors use different sets of groups to
323
-- provide different "views" of an MTA.
324
325
-- The possibility of overlap between groups means that summing
326
-- variables across groups may not produce values equal to those in
327
-- the mtaTable. mtaTable should always provide accurate information
328
329
-- about the MTA as a whole.
330
331
-- The term "channel" is often used in MTA implementations; channels
332
-- are usually, but not always, equivalent to a group. However,
333
-- this MIB does not use the term "channel" because there is no
334
-- requirement that an MTA supporting this MIB has to map its
335
-- "channel" abstraction one-to-one onto the MIB's group abstraction.
336
337
-- An MTA may create a group or group of groups at any time. Once
338
-- created, however, an MTA cannot delete an entry for a group from
339
-- the group table. Deletion is only allowed when the MTA is
340
-- reinitialized, and is not required even then. This restriction
341
-- is imposed so that monitoring agents can rely on group
342
-- assignments being consistent across multiple query operations.
343
344
-- Groups may be laid out so as to form a hierarchical arrangement,
345
-- with some groups acting as subgroups for other groups.
346
-- Alternately, disjoint groups of groups may be used to provide
347
-- different sorts of "snapshots" of MTA operation. The
348
-- mtaGroupHierarchy variable provides an indication of how each
349
-- group fits into the overall arrangement being used.
350
351
-- Note that SNMP also defines and uses term "group". MTA groups are
352
-- NOT the same as SNMP groups.
353
354
mtaGroupTable OBJECT-TYPE
355
SYNTAX SEQUENCE OF MtaGroupEntry
356
MAX-ACCESS not-accessible
357
STATUS current
358
DESCRIPTION
359
"The table holding information specific to each MTA group."
360
::= {mta 2}
361
362
mtaGroupEntry OBJECT-TYPE
363
SYNTAX MtaGroupEntry
364
MAX-ACCESS not-accessible
365
STATUS current
366
DESCRIPTION
367
"The entry associated with each MTA group."
368
INDEX {applIndex, mtaGroupIndex}
369
::= {mtaGroupTable 1}
370
371
MtaGroupEntry ::= SEQUENCE {
372
mtaGroupIndex
373
INTEGER,
374
mtaGroupReceivedMessages
375
Counter32,
376
mtaGroupRejectedMessages
377
378
Counter32,
379
mtaGroupStoredMessages
380
Gauge32,
381
mtaGroupTransmittedMessages
382
Counter32,
383
mtaGroupReceivedVolume
384
Counter32,
385
mtaGroupStoredVolume
386
Gauge32,
387
mtaGroupTransmittedVolume
388
Counter32,
389
mtaGroupReceivedRecipients
390
Counter32,
391
mtaGroupStoredRecipients
392
Gauge32,
393
mtaGroupTransmittedRecipients
394
Counter32,
395
mtaGroupOldestMessageStored
396
TimeInterval,
397
mtaGroupInboundAssociations
398
Gauge32,
399
mtaGroupOutboundAssociations
400
Gauge32,
401
mtaGroupAccumulatedInboundAssociations
402
Counter32,
403
mtaGroupAccumulatedOutboundAssociations
404
Counter32,
405
mtaGroupLastInboundActivity
406
TimeInterval,
407
mtaGroupLastOutboundActivity
408
TimeInterval,
409
mtaGroupLastOutboundAssociationAttempt
410
TimeInterval,
411
mtaGroupRejectedInboundAssociations
412
Counter32,
413
mtaGroupFailedOutboundAssociations
414
Counter32,
415
mtaGroupInboundRejectionReason
416
SnmpAdminString,
417
mtaGroupOutboundConnectFailureReason
418
SnmpAdminString,
419
mtaGroupScheduledRetry
420
TimeInterval,
421
mtaGroupMailProtocol
422
OBJECT IDENTIFIER,
423
mtaGroupName
424
SnmpAdminString,
425
mtaGroupSuccessfulConvertedMessages
426
427
Counter32,
428
mtaGroupFailedConvertedMessages
429
Counter32,
430
mtaGroupDescription
431
SnmpAdminString,
432
mtaGroupURL
433
URLString,
434
mtaGroupCreationTime
435
TimeInterval,
436
mtaGroupHierarchy
437
INTEGER,
438
mtaGroupOldestMessageId
439
SnmpAdminString,
440
mtaGroupLoopsDetected
441
Counter32
442
}
443
444
mtaGroupIndex OBJECT-TYPE
445
SYNTAX INTEGER (1..2147483647)
446
MAX-ACCESS not-accessible
447
STATUS current
448
DESCRIPTION
449
"The index associated with a group for a given MTA."
450
::= {mtaGroupEntry 1}
451
452
mtaGroupReceivedMessages OBJECT-TYPE
453
SYNTAX Counter32
454
MAX-ACCESS read-only
455
STATUS current
456
DESCRIPTION
457
"The number of messages received to this group since
458
group creation."
459
::= {mtaGroupEntry 2}
460
461
mtaGroupRejectedMessages OBJECT-TYPE
462
SYNTAX Counter32
463
MAX-ACCESS read-only
464
STATUS current
465
DESCRIPTION
466
"The number of messages rejected by this group since
467
group creation."
468
::= {mtaGroupEntry 3}
469
470
mtaGroupStoredMessages OBJECT-TYPE
471
SYNTAX Gauge32
472
MAX-ACCESS read-only
473
STATUS current
474
DESCRIPTION
475
"The total number of messages currently stored in this
476
group's queue."
477
::= {mtaGroupEntry 4}
478
479
mtaGroupTransmittedMessages OBJECT-TYPE
480
SYNTAX Counter32
481
MAX-ACCESS read-only
482
STATUS current
483
DESCRIPTION
484
"The number of messages transmitted by this group since
485
group creation."
486
::= {mtaGroupEntry 5}
487
488
mtaGroupReceivedVolume OBJECT-TYPE
489
SYNTAX Counter32
490
UNITS "K-octets"
491
MAX-ACCESS read-only
492
STATUS current
493
DESCRIPTION
494
"The total volume of messages received to this group since
495
group creation, measured in kilo-octets. This volume
496
should include all transferred data that is logically above
497
the mail transport protocol level. For example, an
498
SMTP-based MTA should use the number of kilo-octets in the
499
message header and body, while an X.400-based MTA should use
500
the number of kilo-octets of P2 data."
501
::= {mtaGroupEntry 6}
502
503
mtaGroupStoredVolume OBJECT-TYPE
504
SYNTAX Gauge32
505
UNITS "K-octets"
506
MAX-ACCESS read-only
507
STATUS current
508
DESCRIPTION
509
"The total volume of messages currently stored in this
510
group's queue, measured in kilo-octets. This volume should
511
include all stored data that is logically above the mail
512
transport protocol level. For example, an SMTP-based
513
MTA should use the number of kilo-octets in the message
514
header and body, while an X.400-based MTA would use the
515
number of kilo-octets of P2 data."
516
::= {mtaGroupEntry 7}
517
518
mtaGroupTransmittedVolume OBJECT-TYPE
519
SYNTAX Counter32
520
UNITS "K-octets"
521
MAX-ACCESS read-only
522
STATUS current
523
DESCRIPTION
524
"The total volume of messages transmitted by this group
525
since group creation, measured in kilo-octets. This
526
volume should include all transferred data that is logically
527
above the mail transport protocol level. For example, an
528
SMTP-based MTA should use the number of kilo-octets in the
529
message header and body, while an X.400-based MTA should use
530
the number of kilo-octets of P2 data."
531
::= {mtaGroupEntry 8}
532
533
mtaGroupReceivedRecipients OBJECT-TYPE
534
SYNTAX Counter32
535
MAX-ACCESS read-only
536
STATUS current
537
DESCRIPTION
538
"The total number of recipients specified in all messages
539
received to this group since group creation.
540
Recipients this MTA has no responsibility for should not
541
be counted."
542
::= {mtaGroupEntry 9}
543
544
mtaGroupStoredRecipients OBJECT-TYPE
545
SYNTAX Gauge32
546
MAX-ACCESS read-only
547
STATUS current
548
DESCRIPTION
549
"The total number of recipients specified in all messages
550
currently stored in this group's queue. Recipients this
551
MTA has no responsibility for should not be counted."
552
::= {mtaGroupEntry 10}
553
554
mtaGroupTransmittedRecipients OBJECT-TYPE
555
SYNTAX Counter32
556
MAX-ACCESS read-only
557
STATUS current
558
DESCRIPTION
559
"The total number of recipients specified in all messages
560
transmitted by this group since group creation.
561
Recipients this MTA had no responsibility for should not
562
be counted."
563
::= {mtaGroupEntry 11}
564
565
mtaGroupOldestMessageStored OBJECT-TYPE
566
SYNTAX TimeInterval
567
MAX-ACCESS read-only
568
STATUS current
569
DESCRIPTION
570
"Time since the oldest message in this group's queue was
571
572
placed in the queue."
573
::= {mtaGroupEntry 12}
574
575
mtaGroupInboundAssociations OBJECT-TYPE
576
SYNTAX Gauge32
577
MAX-ACCESS read-only
578
STATUS current
579
DESCRIPTION
580
"The number of current associations to the group, where the
581
group is the responder."
582
::= {mtaGroupEntry 13}
583
584
mtaGroupOutboundAssociations OBJECT-TYPE
585
SYNTAX Gauge32
586
MAX-ACCESS read-only
587
STATUS current
588
DESCRIPTION
589
"The number of current associations to the group, where the
590
group is the initiator."
591
::= {mtaGroupEntry 14}
592
593
mtaGroupAccumulatedInboundAssociations OBJECT-TYPE
594
SYNTAX Counter32
595
MAX-ACCESS read-only
596
STATUS current
597
DESCRIPTION
598
"The total number of associations to the group since
599
group creation, where the MTA was the responder."
600
::= {mtaGroupEntry 15}
601
602
mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE
603
SYNTAX Counter32
604
MAX-ACCESS read-only
605
STATUS current
606
DESCRIPTION
607
"The total number of associations from the group since
608
group creation, where the MTA was the initiator."
609
::= {mtaGroupEntry 16}
610
611
mtaGroupLastInboundActivity OBJECT-TYPE
612
SYNTAX TimeInterval
613
MAX-ACCESS read-only
614
STATUS current
615
DESCRIPTION
616
"Time since the last time that this group had an active
617
inbound association for purposes of message reception."
618
::= {mtaGroupEntry 17}
619
620
mtaGroupLastOutboundActivity OBJECT-TYPE
621
SYNTAX TimeInterval
622
MAX-ACCESS read-only
623
STATUS current
624
DESCRIPTION
625
"Time since the last time that this group had a
626
successful outbound association for purposes of
627
message delivery."
628
::= {mtaGroupEntry 18}
629
630
mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE
631
SYNTAX TimeInterval
632
MAX-ACCESS read-only
633
STATUS current
634
DESCRIPTION
635
"Time since the last time that this group attempted
636
to make an outbound association for purposes of
637
message delivery."
638
::= {mtaGroupEntry 34}
639
640
mtaGroupRejectedInboundAssociations OBJECT-TYPE
641
SYNTAX Counter32
642
MAX-ACCESS read-only
643
STATUS current
644
DESCRIPTION
645
"The total number of inbound associations the group has
646
rejected, since group creation. Rejected associations
647
are not counted in the accumulated association totals."
648
::= {mtaGroupEntry 19}
649
650
mtaGroupFailedOutboundAssociations OBJECT-TYPE
651
SYNTAX Counter32
652
MAX-ACCESS read-only
653
STATUS current
654
DESCRIPTION
655
"The total number associations where the group was the
656
initiator and association establishment has failed,
657
since group creation. Failed associations are
658
not counted in the accumulated association totals."
659
::= {mtaGroupEntry 20}
660
661
mtaGroupInboundRejectionReason OBJECT-TYPE
662
SYNTAX SnmpAdminString
663
MAX-ACCESS read-only
664
STATUS current
665
DESCRIPTION
666
"The failure reason, if any, for the last association this
667
group refused to respond to. If no association attempt
668
669
has been made since the MTA was initialized the value
670
should be 'never'."
671
::= {mtaGroupEntry 21}
672
673
mtaGroupOutboundConnectFailureReason OBJECT-TYPE
674
SYNTAX SnmpAdminString
675
MAX-ACCESS read-only
676
STATUS current
677
DESCRIPTION
678
"The failure reason, if any, for the last association attempt
679
this group initiated. If no association attempt has been
680
made since the MTA was initialized the value should be
681
'never'."
682
::= {mtaGroupEntry 22}
683
684
mtaGroupScheduledRetry OBJECT-TYPE
685
SYNTAX TimeInterval
686
MAX-ACCESS read-only
687
STATUS current
688
DESCRIPTION
689
"The amount of time until this group is next scheduled to
690
attempt to make an association."
691
::= {mtaGroupEntry 23}
692
693
mtaGroupMailProtocol OBJECT-TYPE
694
SYNTAX OBJECT IDENTIFIER
695
MAX-ACCESS read-only
696
STATUS current
697
DESCRIPTION
698
"An identification of the protocol being used by this group.
699
For an group employing OSI protocols, this will be the
700
Application Context. For Internet applications, OID
701
values of the form {applTCPProtoID port} or {applUDPProtoID
702
port} are used for TCP-based and UDP-based protocols,
703
respectively. In either case 'port' corresponds to the
704
primary port number being used by the protocol. The
705
usual IANA procedures may be used to register ports for
706
new protocols. applTCPProtoID and applUDPProtoID are
707
defined in the NETWORK-SERVICES-MIB, RFC 2788."
708
::= {mtaGroupEntry 24}
709
710
mtaGroupName OBJECT-TYPE
711
SYNTAX SnmpAdminString
712
MAX-ACCESS read-only
713
STATUS current
714
DESCRIPTION
715
"A descriptive name for the group. If this group connects to
716
a single remote MTA this should be the name of that MTA. If
717
718
this in turn is an Internet MTA this should be the domain
719
name. For an OSI MTA it should be the string encoded
720
distinguished name of the managed object using the format
721
defined in RFC 2253. For X.400(1984) MTAs which do not
722
have a Distinguished Name, the RFC 2156 syntax
723
'mta in globalid' used in X400-Received: fields can be
724
used."
725
::= {mtaGroupEntry 25}
726
727
mtaGroupSuccessfulConvertedMessages OBJECT-TYPE
728
SYNTAX Counter32
729
MAX-ACCESS read-only
730
STATUS current
731
DESCRIPTION
732
"The number of messages that have been successfully
733
converted from one form to another in this group
734
since group creation."
735
::= {mtaGroupEntry 26}
736
737
mtaGroupFailedConvertedMessages OBJECT-TYPE
738
SYNTAX Counter32
739
MAX-ACCESS read-only
740
STATUS current
741
DESCRIPTION
742
"The number of messages for which an unsuccessful
743
attempt was made to convert them from one form to
744
another in this group since group creation."
745
::= {mtaGroupEntry 27}
746
747
mtaGroupDescription OBJECT-TYPE
748
SYNTAX SnmpAdminString
749
MAX-ACCESS read-only
750
STATUS current
751
DESCRIPTION
752
"A description of the group's purpose. This information is
753
intended to identify the group in a status display."
754
::= {mtaGroupEntry 28}
755
756
mtaGroupURL OBJECT-TYPE
757
SYNTAX URLString
758
MAX-ACCESS read-only
759
STATUS current
760
DESCRIPTION
761
"A URL pointing to a description of the group. This
762
information is intended to identify and briefly describe
763
the group in a status display."
764
::= {mtaGroupEntry 29}
765
766
mtaGroupCreationTime OBJECT-TYPE
767
SYNTAX TimeInterval
768
MAX-ACCESS read-only
769
STATUS current
770
DESCRIPTION
771
"Time since this group was first created."
772
::= {mtaGroupEntry 30}
773
774
mtaGroupHierarchy OBJECT-TYPE
775
SYNTAX INTEGER (-2147483648..2147483647)
776
MAX-ACCESS read-only
777
STATUS current
778
DESCRIPTION
779
"Describes how this group fits into the hierarchy. A
780
positive value is interpreted as an mtaGroupIndex
781
value for some other group whose variables include
782
those of this group (and usually others). A negative
783
value is interpreted as a group collection code: Groups
784
with common negative hierarchy values comprise one
785
particular breakdown of MTA activity as a whole. A
786
zero value means that this MIB implementation doesn't
787
implement hierarchy indicators and thus the overall
788
group hierarchy cannot be determined."
789
::= {mtaGroupEntry 31}
790
791
mtaGroupOldestMessageId OBJECT-TYPE
792
SYNTAX SnmpAdminString
793
MAX-ACCESS read-only
794
STATUS current
795
DESCRIPTION
796
"Message ID of the oldest message in the group's queue.
797
Whenever possible this should be in the form of an
798
RFC 822 msg-id; X.400 may convert X.400 message
799
identifiers to this form by following the rules laid
800
out in RFC2156."
801
::= {mtaGroupEntry 32}
802
803
mtaGroupLoopsDetected OBJECT-TYPE
804
SYNTAX Counter32
805
MAX-ACCESS read-only
806
STATUS current
807
DESCRIPTION
808
"A message loop is defined as a situation where the MTA
809
decides that a given message will never be delivered to
810
one or more recipients and instead will continue to
811
loop endlessly through one or more MTAs. This variable
812
counts the number of times the MTA has detected such a
813
situation in conjunction with something associated with
814
815
this group since group creation. Note that the
816
mechanism MTAs use to detect loops (e.g., trace field
817
counting, count of references to this MTA in a trace
818
field, examination of DNS or other directory information,
819
etc.), the level at which loops are detected (e.g., per
820
message, per recipient, per directory entry, etc.), and
821
the handling of a loop once it is detected (e.g., looping
822
messages are held, looping messages are bounced or sent
823
to the postmaster, messages that the MTA knows will loop
824
won't be accepted, etc.) vary widely from one MTA to the
825
next and cannot be inferred from this variable."
826
::= {mtaGroupEntry 33}
827
828
-- The mtaGroupAssociationTable provides a means of correlating
829
-- entries in the network services association table with the
830
-- MTA group responsible for the association.
831
832
mtaGroupAssociationTable OBJECT-TYPE
833
SYNTAX SEQUENCE OF MtaGroupAssociationEntry
834
MAX-ACCESS not-accessible
835
STATUS current
836
DESCRIPTION
837
"The table holding information regarding the associations
838
for each MTA group."
839
::= {mta 3}
840
841
mtaGroupAssociationEntry OBJECT-TYPE
842
SYNTAX MtaGroupAssociationEntry
843
MAX-ACCESS not-accessible
844
STATUS current
845
DESCRIPTION
846
"The entry holding information regarding the associations
847
for each MTA group."
848
INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex}
849
::= {mtaGroupAssociationTable 1}
850
851
MtaGroupAssociationEntry ::= SEQUENCE {
852
mtaGroupAssociationIndex
853
INTEGER
854
}
855
856
mtaGroupAssociationIndex OBJECT-TYPE
857
SYNTAX INTEGER (1..2147483647)
858
MAX-ACCESS read-only
859
STATUS current
860
DESCRIPTION
861
"Reference into association table to allow correlation of
862
this group's active associations with the association table."
863
::= {mtaGroupAssociationEntry 1}
864
865
-- The mtaGroupErrorTable gives each group a way of tallying
866
-- the specific errors it has encountered. The mechanism
867
-- defined here uses RFC 1893 status codes to identify
868
-- various specific errors. There are also classes for generic
869
-- errors of various sorts, and the entire mechanism is also
870
-- extensible, in that new error codes can be defined at any
871
-- time.
872
873
mtaGroupErrorTable OBJECT-TYPE
874
SYNTAX SEQUENCE OF MtaGroupErrorEntry
875
MAX-ACCESS not-accessible
876
STATUS current
877
DESCRIPTION
878
"The table holding information regarding accumulated errors
879
for each MTA group."
880
::= {mta 5}
881
882
mtaGroupErrorEntry OBJECT-TYPE
883
SYNTAX MtaGroupErrorEntry
884
MAX-ACCESS not-accessible
885
STATUS current
886
DESCRIPTION
887
"The entry holding information regarding accumulated
888
errors for each MTA group."
889
INDEX {applIndex, mtaGroupIndex, mtaStatusCode}
890
::= {mtaGroupErrorTable 1}
891
892
MtaGroupErrorEntry ::= SEQUENCE {
893
mtaStatusCode
894
INTEGER (4000000..5999999),
895
mtaGroupInboundErrorCount
896
Counter32,
897
mtaGroupInternalErrorCount
898
Counter32,
899
mtaGroupOutboundErrorCount
900
Counter32
901
}
902
903
mtaGroupInboundErrorCount OBJECT-TYPE
904
SYNTAX Counter32
905
MAX-ACCESS read-only
906
STATUS current
907
DESCRIPTION
908
"Count of the number of errors of a given type that have
909
been accumulated in association with a particular group
910
while processing incoming messages. In the case of SMTP
911
912
these will typically be errors reporting by an SMTP
913
server to the remote client; in the case of X.400
914
these will typically be errors encountered while
915
processing an incoming message."
916
::= {mtaGroupErrorEntry 1}
917
918
mtaGroupInternalErrorCount OBJECT-TYPE
919
SYNTAX Counter32
920
MAX-ACCESS read-only
921
STATUS current
922
DESCRIPTION
923
"Count of the number of errors of a given type that have
924
been accumulated in association with a particular group
925
during internal MTA processing."
926
::= {mtaGroupErrorEntry 2}
927
928
mtaGroupOutboundErrorCount OBJECT-TYPE
929
SYNTAX Counter32
930
MAX-ACCESS read-only
931
STATUS current
932
DESCRIPTION
933
"Count of the number of errors of a given type that have
934
been accumulated in association with a particular group's
935
outbound connection activities. In the case of an SMTP
936
client these will typically be errors reported while
937
attempting to contact or while communicating with the
938
remote SMTP server. In the case of X.400 these will
939
typically be errors encountered while constructing
940
or attempting to deliver an outgoing message."
941
::= {mtaGroupErrorEntry 3}
942
943
mtaStatusCode OBJECT-TYPE
944
SYNTAX INTEGER (4000000..5999999)
945
MAX-ACCESS not-accessible
946
STATUS current
947
DESCRIPTION
948
"An index capable of representing an Enhanced Mail System
949
Status Code. Enhanced Mail System Status Codes are
950
defined in RFC 1893. These codes have the form
951
952
class.subject.detail
953
954
Here 'class' is either 2, 4, or 5 and both 'subject' and
955
'detail' are integers in the range 0..999. Given a status
956
code the corresponding index value is defined to be
957
((class * 1000) + subject) * 1000 + detail. Both SMTP
958
error response codes and X.400 reason and diagnostic codes
959
can be mapped into these codes, resulting in a namespace
960
961
capable of describing most error conditions a mail system
962
encounters in a generic yet detailed way."
963
::= {mtaGroupErrorEntry 4}
964
965
-- Conformance information
966
967
mtaConformance OBJECT IDENTIFIER ::= {mta 4}
968
969
mtaGroups OBJECT IDENTIFIER ::= {mtaConformance 1}
970
mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2}
971
972
-- Compliance statements
973
974
mtaCompliance MODULE-COMPLIANCE
975
STATUS current
976
DESCRIPTION
977
"The compliance statement for RFC 1566 implementations
978
which support the Mail Monitoring MIB for basic
979
monitoring of MTAs."
980
MODULE -- this module
981
MANDATORY-GROUPS {mtaRFC1566Group}
982
::= {mtaCompliances 1}
983
984
mtaAssocCompliance MODULE-COMPLIANCE
985
STATUS current
986
DESCRIPTION
987
"The compliance statement for RFC 1566 implementations
988
which support the Mail Monitoring MIB for monitoring
989
of MTAs and their associations."
990
MODULE -- this module
991
MANDATORY-GROUPS {mtaRFC1566Group, mtaRFC1566AssocGroup}
992
::= {mtaCompliances 2}
993
994
mtaRFC2249Compliance MODULE-COMPLIANCE
995
STATUS current
996
DESCRIPTION
997
"The compliance statement for RFC 2249 implementations
998
which support the Mail Monitoring MIB for basic
999
monitoring of MTAs."
1000
MODULE -- this module
1001
MANDATORY-GROUPS {mtaRFC2249Group}
1002
::= {mtaCompliances 5}
1003
1004
mtaRFC2249AssocCompliance MODULE-COMPLIANCE
1005
STATUS current
1006
DESCRIPTION
1007
"The compliance statement for RFC 2249 implementations
1008
1009
which support the Mail Monitoring MIB for monitoring of
1010
MTAs and their associations."
1011
MODULE -- this module
1012
MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup}
1013
::= {mtaCompliances 6}
1014
1015
mtaRFC2249ErrorCompliance MODULE-COMPLIANCE
1016
STATUS current
1017
DESCRIPTION
1018
"The compliance statement for RFC 2249 implementations
1019
which support the Mail Monitoring MIB for monitoring of
1020
MTAs and detailed errors."
1021
MODULE -- this module
1022
MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249ErrorGroup}
1023
::= {mtaCompliances 7}
1024
1025
mtaRFC2249FullCompliance MODULE-COMPLIANCE
1026
STATUS current
1027
DESCRIPTION
1028
"The compliance statement for RFC 2249 implementations
1029
which support the full Mail Monitoring MIB for
1030
monitoring of MTAs, associations, and detailed errors."
1031
MODULE -- this module
1032
MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup,
1033
mtaRFC2249ErrorGroup}
1034
::= {mtaCompliances 8}
1035
1036
mtaRFC2789Compliance MODULE-COMPLIANCE
1037
STATUS current
1038
DESCRIPTION
1039
"The compliance statement for RFC 2789 implementations
1040
which support the Mail Monitoring MIB for basic
1041
monitoring of MTAs."
1042
MODULE -- this module
1043
MANDATORY-GROUPS {mtaRFC2789Group}
1044
::= {mtaCompliances 9}
1045
1046
mtaRFC2789AssocCompliance MODULE-COMPLIANCE
1047
STATUS current
1048
DESCRIPTION
1049
"The compliance statement for RFC 2789 implementations
1050
which support the Mail Monitoring MIB for monitoring of
1051
MTAs and their associations."
1052
MODULE -- this module
1053
MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789AssocGroup}
1054
::= {mtaCompliances 10}
1055
1056
mtaRFC2789ErrorCompliance MODULE-COMPLIANCE
1057
STATUS current
1058
DESCRIPTION
1059
"The compliance statement for RFC 2789 implementations
1060
which support the Mail Monitoring MIB for monitoring of
1061
MTAs and detailed errors."
1062
MODULE -- this module
1063
MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789ErrorGroup}
1064
::= {mtaCompliances 11}
1065
1066
mtaRFC2789FullCompliance MODULE-COMPLIANCE
1067
STATUS current
1068
DESCRIPTION
1069
"The compliance statement for RFC 2789 implementations
1070
which support the full Mail Monitoring MIB for
1071
monitoring of MTAs, associations, and detailed errors."
1072
MODULE -- this module
1073
MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789AssocGroup,
1074
mtaRFC2789ErrorGroup}
1075
::= {mtaCompliances 12}
1076
1077
-- Units of conformance
1078
1079
mtaRFC1566Group OBJECT-GROUP
1080
OBJECTS {
1081
mtaReceivedMessages, mtaStoredMessages,
1082
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1083
mtaTransmittedVolume, mtaReceivedRecipients,
1084
mtaStoredRecipients, mtaTransmittedRecipients,
1085
mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1086
mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1087
mtaGroupReceivedVolume, mtaGroupStoredVolume,
1088
mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1089
mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1090
mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1091
mtaGroupOutboundAssociations,
1092
mtaGroupAccumulatedInboundAssociations,
1093
mtaGroupAccumulatedOutboundAssociations,
1094
mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1095
mtaGroupRejectedInboundAssociations,
1096
mtaGroupFailedOutboundAssociations,
1097
mtaGroupInboundRejectionReason,
1098
mtaGroupOutboundConnectFailureReason,
1099
mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName}
1100
STATUS current
1101
DESCRIPTION
1102
"A collection of objects providing basic monitoring of MTAs.
1103
This is the original set of such objects defined in RFC
1104
1566."
1105
::= {mtaGroups 10}
1106
1107
mtaRFC1566AssocGroup OBJECT-GROUP
1108
OBJECTS {
1109
mtaGroupAssociationIndex}
1110
STATUS current
1111
DESCRIPTION
1112
"A collection of objects providing monitoring of MTA
1113
associations. This is the original set of such objects
1114
defined in RFC 1566."
1115
::= {mtaGroups 11}
1116
1117
mtaRFC2249Group OBJECT-GROUP
1118
OBJECTS {
1119
mtaReceivedMessages, mtaStoredMessages,
1120
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1121
mtaTransmittedVolume, mtaReceivedRecipients,
1122
mtaStoredRecipients, mtaTransmittedRecipients,
1123
mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
1124
mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1125
mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1126
mtaGroupReceivedVolume, mtaGroupStoredVolume,
1127
mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1128
mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1129
mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1130
mtaGroupOutboundAssociations, mtaLoopsDetected,
1131
mtaGroupAccumulatedInboundAssociations,
1132
mtaGroupAccumulatedOutboundAssociations,
1133
mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1134
mtaGroupLastOutboundAssociationAttempt,
1135
mtaGroupRejectedInboundAssociations,
1136
mtaGroupFailedOutboundAssociations,
1137
mtaGroupInboundRejectionReason,
1138
mtaGroupOutboundConnectFailureReason,
1139
mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName,
1140
mtaGroupSuccessfulConvertedMessages,
1141
mtaGroupFailedConvertedMessages, mtaGroupDescription,
1142
mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy,
1143
mtaGroupOldestMessageId, mtaGroupLoopsDetected}
1144
STATUS current
1145
DESCRIPTION
1146
"A collection of objects providing basic monitoring of MTAs.
1147
This group was originally defined in RFC 2249."
1148
::= {mtaGroups 4}
1149
1150
mtaRFC2249AssocGroup OBJECT-GROUP
1151
OBJECTS {
1152
mtaGroupAssociationIndex}
1153
STATUS current
1154
DESCRIPTION
1155
"A collection of objects providing monitoring of MTA
1156
associations. This group was originally defined in RFC
1157
2249."
1158
::= {mtaGroups 5}
1159
1160
mtaRFC2249ErrorGroup OBJECT-GROUP
1161
OBJECTS {
1162
mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
1163
mtaGroupOutboundErrorCount}
1164
STATUS current
1165
DESCRIPTION
1166
"A collection of objects providing monitoring of
1167
detailed MTA errors. This group was originally defined
1168
in RFC 2249."
1169
::= {mtaGroups 6}
1170
1171
mtaRFC2789Group OBJECT-GROUP
1172
OBJECTS {
1173
mtaReceivedMessages, mtaStoredMessages,
1174
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1175
mtaTransmittedVolume, mtaReceivedRecipients,
1176
mtaStoredRecipients, mtaTransmittedRecipients,
1177
mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
1178
mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1179
mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1180
mtaGroupReceivedVolume, mtaGroupStoredVolume,
1181
mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1182
mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1183
mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1184
mtaGroupOutboundAssociations, mtaLoopsDetected,
1185
mtaGroupAccumulatedInboundAssociations,
1186
mtaGroupAccumulatedOutboundAssociations,
1187
mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1188
mtaGroupLastOutboundAssociationAttempt,
1189
mtaGroupRejectedInboundAssociations,
1190
mtaGroupFailedOutboundAssociations,
1191
mtaGroupInboundRejectionReason,
1192
mtaGroupOutboundConnectFailureReason,
1193
mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName,
1194
mtaGroupSuccessfulConvertedMessages,
1195
mtaGroupFailedConvertedMessages, mtaGroupDescription,
1196
mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy,
1197
mtaGroupOldestMessageId, mtaGroupLoopsDetected}
1198
STATUS current
1199
DESCRIPTION
1200
"A collection of objects providing basic monitoring of MTAs.
1201
1202
This is the appropriate group for RFC 2789."
1203
::= {mtaGroups 7}
1204
1205
mtaRFC2789AssocGroup OBJECT-GROUP
1206
OBJECTS {
1207
mtaGroupAssociationIndex}
1208
STATUS current
1209
DESCRIPTION
1210
"A collection of objects providing monitoring of MTA
1211
associations. This is the appropriate group for RFC
1212
2789 association monitoring."
1213
::= {mtaGroups 8}
1214
1215
mtaRFC2789ErrorGroup OBJECT-GROUP
1216
OBJECTS {
1217
mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
1218
mtaGroupOutboundErrorCount}
1219
STATUS current
1220
DESCRIPTION
1221
"A collection of objects providing monitoring of
1222
detailed MTA errors. This is the appropriate group
1223
for RFC 2789 error monitoring."
1224
::= {mtaGroups 9}
1225
1226
END
Loggerhead is a web-based interface for Breezy
Version: 2.0.1