1
MTA-MIB DEFINITIONS ::= BEGIN
4
OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2
8
MODULE-COMPLIANCE, OBJECT-GROUP
11
FROM SNMP-FRAMEWORK-MIB
13
FROM NETWORK-SERVICES-MIB;
16
LAST-UPDATED "200003030000Z"
17
ORGANIZATION "IETF Mail and Directory Management Working Group"
21
Postal: Innosoft International, Inc.
29
E-Mail: ned.freed@innosoft.com"
31
"The MIB module describing Message Transfer Agents (MTAs)"
32
REVISION "200003030000Z"
34
"This revision, published in RFC 2789, changes a number of
35
DisplayStrings to SnmpAdminStrings. Note that this change
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"
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"
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"
66
"The original version of this MIB was published in RFC 1566"
70
SYNTAX SEQUENCE OF MtaEntry
71
MAX-ACCESS not-accessible
74
"The table holding information specific to an MTA."
79
MAX-ACCESS not-accessible
82
"The entry associated with each MTA."
86
MtaEntry ::= SEQUENCE {
91
mtaTransmittedMessages
103
mtaTransmittedRecipients
105
mtaSuccessfulConvertedMessages
107
mtaFailedConvertedMessages
113
mtaReceivedMessages OBJECT-TYPE
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."
124
mtaStoredMessages OBJECT-TYPE
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
135
mtaTransmittedMessages OBJECT-TYPE
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
146
mtaReceivedVolume OBJECT-TYPE
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
164
mtaStoredVolume OBJECT-TYPE
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."
181
mtaTransmittedVolume OBJECT-TYPE
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."
198
mtaReceivedRecipients OBJECT-TYPE
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."
214
mtaStoredRecipients OBJECT-TYPE
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."
228
mtaTransmittedRecipients OBJECT-TYPE
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."
242
mtaSuccessfulConvertedMessages OBJECT-TYPE
247
"The number of messages that have been successfully
248
converted from one form to another since MTA
252
mtaFailedConvertedMessages OBJECT-TYPE
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."
262
mtaLoopsDetected OBJECT-TYPE
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
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."
297
mtaGroupTable OBJECT-TYPE
298
SYNTAX SEQUENCE OF MtaGroupEntry
299
MAX-ACCESS not-accessible
302
"The table holding information specific to each MTA group."
305
mtaGroupEntry OBJECT-TYPE
307
MAX-ACCESS not-accessible
310
"The entry associated with each MTA group."
311
INDEX {applIndex, mtaGroupIndex}
312
::= {mtaGroupTable 1}
314
MtaGroupEntry ::= SEQUENCE {
317
mtaGroupReceivedMessages
319
mtaGroupRejectedMessages
322
mtaGroupStoredMessages
324
mtaGroupTransmittedMessages
326
mtaGroupReceivedVolume
330
mtaGroupTransmittedVolume
332
mtaGroupReceivedRecipients
334
mtaGroupStoredRecipients
336
mtaGroupTransmittedRecipients
338
mtaGroupOldestMessageStored
340
mtaGroupInboundAssociations
342
mtaGroupOutboundAssociations
344
mtaGroupAccumulatedInboundAssociations
346
mtaGroupAccumulatedOutboundAssociations
348
mtaGroupLastInboundActivity
350
mtaGroupLastOutboundActivity
352
mtaGroupLastOutboundAssociationAttempt
354
mtaGroupRejectedInboundAssociations
356
mtaGroupFailedOutboundAssociations
358
mtaGroupInboundRejectionReason
360
mtaGroupOutboundConnectFailureReason
362
mtaGroupScheduledRetry
368
mtaGroupSuccessfulConvertedMessages
371
mtaGroupFailedConvertedMessages
381
mtaGroupOldestMessageId
383
mtaGroupLoopsDetected
387
mtaGroupIndex OBJECT-TYPE
388
SYNTAX INTEGER (1..2147483647)
389
MAX-ACCESS not-accessible
392
"The index associated with a group for a given MTA."
393
::= {mtaGroupEntry 1}
395
mtaGroupReceivedMessages OBJECT-TYPE
400
"The number of messages received to this group since
402
::= {mtaGroupEntry 2}
404
mtaGroupRejectedMessages OBJECT-TYPE
409
"The number of messages rejected by this group since
411
::= {mtaGroupEntry 3}
413
mtaGroupStoredMessages OBJECT-TYPE
418
"The total number of messages currently stored in this
420
::= {mtaGroupEntry 4}
422
mtaGroupTransmittedMessages OBJECT-TYPE
427
"The number of messages transmitted by this group since
429
::= {mtaGroupEntry 5}
431
mtaGroupReceivedVolume OBJECT-TYPE
437
"The total volume of messages received to this group since
438
group creation, measured in kilo-octets. This volume
439
should include all transferred data that is logically above
440
the mail transport protocol level. For example, an
441
SMTP-based MTA should use the number of kilo-octets in the
442
message header and body, while an X.400-based MTA should use
443
the number of kilo-octets of P2 data."
444
::= {mtaGroupEntry 6}
446
mtaGroupStoredVolume OBJECT-TYPE
452
"The total volume of messages currently stored in this
453
group's queue, measured in kilo-octets. This volume should
454
include all stored data that is logically above the mail
455
transport protocol level. For example, an SMTP-based
456
MTA should use the number of kilo-octets in the message
457
header and body, while an X.400-based MTA would use the
458
number of kilo-octets of P2 data."
459
::= {mtaGroupEntry 7}
461
mtaGroupTransmittedVolume OBJECT-TYPE
467
"The total volume of messages transmitted by this group
468
since group creation, measured in kilo-octets. This
469
volume should include all transferred data that is logically
470
above the mail transport protocol level. For example, an
471
SMTP-based MTA should use the number of kilo-octets in the
472
message header and body, while an X.400-based MTA should use
473
the number of kilo-octets of P2 data."
474
::= {mtaGroupEntry 8}
476
mtaGroupReceivedRecipients OBJECT-TYPE
481
"The total number of recipients specified in all messages
482
received to this group since group creation.
483
Recipients this MTA has no responsibility for should not
485
::= {mtaGroupEntry 9}
487
mtaGroupStoredRecipients OBJECT-TYPE
492
"The total number of recipients specified in all messages
493
currently stored in this group's queue. Recipients this
494
MTA has no responsibility for should not be counted."
495
::= {mtaGroupEntry 10}
497
mtaGroupTransmittedRecipients OBJECT-TYPE
502
"The total number of recipients specified in all messages
503
transmitted by this group since group creation.
504
Recipients this MTA had no responsibility for should not
506
::= {mtaGroupEntry 11}
508
mtaGroupOldestMessageStored OBJECT-TYPE
513
"Time since the oldest message in this group's queue was
515
placed in the queue."
516
::= {mtaGroupEntry 12}
518
mtaGroupInboundAssociations OBJECT-TYPE
523
"The number of current associations to the group, where the
524
group is the responder."
525
::= {mtaGroupEntry 13}
527
mtaGroupOutboundAssociations OBJECT-TYPE
532
"The number of current associations to the group, where the
533
group is the initiator."
534
::= {mtaGroupEntry 14}
536
mtaGroupAccumulatedInboundAssociations OBJECT-TYPE
541
"The total number of associations to the group since
542
group creation, where the MTA was the responder."
543
::= {mtaGroupEntry 15}
545
mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE
550
"The total number of associations from the group since
551
group creation, where the MTA was the initiator."
552
::= {mtaGroupEntry 16}
554
mtaGroupLastInboundActivity OBJECT-TYPE
559
"Time since the last time that this group had an active
560
inbound association for purposes of message reception."
561
::= {mtaGroupEntry 17}
563
mtaGroupLastOutboundActivity OBJECT-TYPE
568
"Time since the last time that this group had a
569
successful outbound association for purposes of
571
::= {mtaGroupEntry 18}
573
mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE
578
"Time since the last time that this group attempted
579
to make an outbound association for purposes of
581
::= {mtaGroupEntry 34}
583
mtaGroupRejectedInboundAssociations OBJECT-TYPE
588
"The total number of inbound associations the group has
589
rejected, since group creation. Rejected associations
590
are not counted in the accumulated association totals."
591
::= {mtaGroupEntry 19}
593
mtaGroupFailedOutboundAssociations OBJECT-TYPE
598
"The total number associations where the group was the
599
initiator and association establishment has failed,
600
since group creation. Failed associations are
601
not counted in the accumulated association totals."
602
::= {mtaGroupEntry 20}
604
mtaGroupInboundRejectionReason OBJECT-TYPE
605
SYNTAX SnmpAdminString
609
"The failure reason, if any, for the last association this
610
group refused to respond to. If no association attempt
612
has been made since the MTA was initialized the value
614
::= {mtaGroupEntry 21}
616
mtaGroupOutboundConnectFailureReason OBJECT-TYPE
617
SYNTAX SnmpAdminString
621
"The failure reason, if any, for the last association attempt
622
this group initiated. If no association attempt has been
623
made since the MTA was initialized the value should be
625
::= {mtaGroupEntry 22}
627
mtaGroupScheduledRetry OBJECT-TYPE
632
"The amount of time until this group is next scheduled to
633
attempt to make an association."
634
::= {mtaGroupEntry 23}
636
mtaGroupMailProtocol OBJECT-TYPE
637
SYNTAX OBJECT IDENTIFIER
641
"An identification of the protocol being used by this group.
642
For an group employing OSI protocols, this will be the
643
Application Context. For Internet applications, OID
644
values of the form {applTCPProtoID port} or {applUDPProtoID
645
port} are used for TCP-based and UDP-based protocols,
646
respectively. In either case 'port' corresponds to the
647
primary port number being used by the protocol. The
648
usual IANA procedures may be used to register ports for
649
new protocols. applTCPProtoID and applUDPProtoID are
650
defined in the NETWORK-SERVICES-MIB, RFC 2788."
651
::= {mtaGroupEntry 24}
653
mtaGroupName OBJECT-TYPE
654
SYNTAX SnmpAdminString
658
"A descriptive name for the group. If this group connects to
659
a single remote MTA this should be the name of that MTA. If
661
this in turn is an Internet MTA this should be the domain
662
name. For an OSI MTA it should be the string encoded
663
distinguished name of the managed object using the format
664
defined in RFC 2253. For X.400(1984) MTAs which do not
665
have a Distinguished Name, the RFC 2156 syntax
666
'mta in globalid' used in X400-Received: fields can be
668
::= {mtaGroupEntry 25}
670
mtaGroupSuccessfulConvertedMessages OBJECT-TYPE
675
"The number of messages that have been successfully
676
converted from one form to another in this group
677
since group creation."
678
::= {mtaGroupEntry 26}
680
mtaGroupFailedConvertedMessages OBJECT-TYPE
685
"The number of messages for which an unsuccessful
686
attempt was made to convert them from one form to
687
another in this group since group creation."
688
::= {mtaGroupEntry 27}
690
mtaGroupDescription OBJECT-TYPE
691
SYNTAX SnmpAdminString
695
"A description of the group's purpose. This information is
696
intended to identify the group in a status display."
697
::= {mtaGroupEntry 28}
699
mtaGroupURL OBJECT-TYPE
704
"A URL pointing to a description of the group. This
705
information is intended to identify and briefly describe
706
the group in a status display."
707
::= {mtaGroupEntry 29}
709
mtaGroupCreationTime OBJECT-TYPE
714
"Time since this group was first created."
715
::= {mtaGroupEntry 30}
717
mtaGroupHierarchy OBJECT-TYPE
718
SYNTAX INTEGER (-2147483648..2147483647)
722
"Describes how this group fits into the hierarchy. A
723
positive value is interpreted as an mtaGroupIndex
724
value for some other group whose variables include
725
those of this group (and usually others). A negative
726
value is interpreted as a group collection code: Groups
727
with common negative hierarchy values comprise one
728
particular breakdown of MTA activity as a whole. A
729
zero value means that this MIB implementation doesn't
730
implement hierarchy indicators and thus the overall
731
group hierarchy cannot be determined."
732
::= {mtaGroupEntry 31}
734
mtaGroupOldestMessageId OBJECT-TYPE
735
SYNTAX SnmpAdminString
739
"Message ID of the oldest message in the group's queue.
740
Whenever possible this should be in the form of an
741
RFC 822 msg-id; X.400 may convert X.400 message
742
identifiers to this form by following the rules laid
744
::= {mtaGroupEntry 32}
746
mtaGroupLoopsDetected OBJECT-TYPE
751
"A message loop is defined as a situation where the MTA
752
decides that a given message will never be delivered to
753
one or more recipients and instead will continue to
754
loop endlessly through one or more MTAs. This variable
755
counts the number of times the MTA has detected such a
756
situation in conjunction with something associated with
758
this group since group creation. Note that the
759
mechanism MTAs use to detect loops (e.g., trace field
760
counting, count of references to this MTA in a trace
761
field, examination of DNS or other directory information,
762
etc.), the level at which loops are detected (e.g., per
763
message, per recipient, per directory entry, etc.), and
764
the handling of a loop once it is detected (e.g., looping
765
messages are held, looping messages are bounced or sent
766
to the postmaster, messages that the MTA knows will loop
767
won't be accepted, etc.) vary widely from one MTA to the
768
next and cannot be inferred from this variable."
769
::= {mtaGroupEntry 33}
772
mtaGroupAssociationTable OBJECT-TYPE
773
SYNTAX SEQUENCE OF MtaGroupAssociationEntry
774
MAX-ACCESS not-accessible
777
"The table holding information regarding the associations
781
mtaGroupAssociationEntry OBJECT-TYPE
782
SYNTAX MtaGroupAssociationEntry
783
MAX-ACCESS not-accessible
786
"The entry holding information regarding the associations
788
INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex}
789
::= {mtaGroupAssociationTable 1}
791
MtaGroupAssociationEntry ::= SEQUENCE {
792
mtaGroupAssociationIndex
796
mtaGroupAssociationIndex OBJECT-TYPE
797
SYNTAX INTEGER (1..2147483647)
801
"Reference into association table to allow correlation of
802
this group's active associations with the association table."
803
::= {mtaGroupAssociationEntry 1}
806
mtaGroupErrorTable OBJECT-TYPE
807
SYNTAX SEQUENCE OF MtaGroupErrorEntry
808
MAX-ACCESS not-accessible
811
"The table holding information regarding accumulated errors
815
mtaGroupErrorEntry OBJECT-TYPE
816
SYNTAX MtaGroupErrorEntry
817
MAX-ACCESS not-accessible
820
"The entry holding information regarding accumulated
821
errors for each MTA group."
822
INDEX {applIndex, mtaGroupIndex, mtaStatusCode}
823
::= {mtaGroupErrorTable 1}
825
MtaGroupErrorEntry ::= SEQUENCE {
827
INTEGER (4000000..5999999),
828
mtaGroupInboundErrorCount
830
mtaGroupInternalErrorCount
832
mtaGroupOutboundErrorCount
836
mtaGroupInboundErrorCount OBJECT-TYPE
841
"Count of the number of errors of a given type that have
842
been accumulated in association with a particular group
843
while processing incoming messages. In the case of SMTP
845
these will typically be errors reporting by an SMTP
846
server to the remote client; in the case of X.400
847
these will typically be errors encountered while
848
processing an incoming message."
849
::= {mtaGroupErrorEntry 1}
851
mtaGroupInternalErrorCount OBJECT-TYPE
856
"Count of the number of errors of a given type that have
857
been accumulated in association with a particular group
858
during internal MTA processing."
859
::= {mtaGroupErrorEntry 2}
861
mtaGroupOutboundErrorCount OBJECT-TYPE
866
"Count of the number of errors of a given type that have
867
been accumulated in association with a particular group's
868
outbound connection activities. In the case of an SMTP
869
client these will typically be errors reported while
870
attempting to contact or while communicating with the
871
remote SMTP server. In the case of X.400 these will
872
typically be errors encountered while constructing
873
or attempting to deliver an outgoing message."
874
::= {mtaGroupErrorEntry 3}
876
mtaStatusCode OBJECT-TYPE
877
SYNTAX INTEGER (4000000..5999999)
878
MAX-ACCESS not-accessible
881
"An index capable of representing an Enhanced Mail System
882
Status Code. Enhanced Mail System Status Codes are
883
defined in RFC 1893. These codes have the form
887
Here 'class' is either 2, 4, or 5 and both 'subject' and
888
'detail' are integers in the range 0..999. Given a status
889
code the corresponding index value is defined to be
890
((class * 1000) + subject) * 1000 + detail. Both SMTP
891
error response codes and X.400 reason and diagnostic codes
892
can be mapped into these codes, resulting in a namespace
894
capable of describing most error conditions a mail system
895
encounters in a generic yet detailed way."
896
::= {mtaGroupErrorEntry 4}
899
mtaConformance OBJECT IDENTIFIER ::= {mta 4}
901
mtaGroups OBJECT IDENTIFIER ::= {mtaConformance 1}
902
mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2}
905
mtaCompliance MODULE-COMPLIANCE
908
"The compliance statement for RFC 1566 implementations
909
which support the Mail Monitoring MIB for basic
911
MODULE -- this module
912
MANDATORY-GROUPS {mtaRFC1566Group}
913
::= {mtaCompliances 1}
915
mtaAssocCompliance MODULE-COMPLIANCE
918
"The compliance statement for RFC 1566 implementations
919
which support the Mail Monitoring MIB for monitoring
920
of MTAs and their associations."
921
MODULE -- this module
922
MANDATORY-GROUPS {mtaRFC1566Group, mtaRFC1566AssocGroup}
923
::= {mtaCompliances 2}
925
mtaRFC2249Compliance MODULE-COMPLIANCE
928
"The compliance statement for RFC 2249 implementations
929
which support the Mail Monitoring MIB for basic
931
MODULE -- this module
932
MANDATORY-GROUPS {mtaRFC2249Group}
933
::= {mtaCompliances 5}
935
mtaRFC2249AssocCompliance MODULE-COMPLIANCE
938
"The compliance statement for RFC 2249 implementations
940
which support the Mail Monitoring MIB for monitoring of
941
MTAs and their associations."
942
MODULE -- this module
943
MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup}
944
::= {mtaCompliances 6}
946
mtaRFC2249ErrorCompliance MODULE-COMPLIANCE
949
"The compliance statement for RFC 2249 implementations
950
which support the Mail Monitoring MIB for monitoring of
951
MTAs and detailed errors."
952
MODULE -- this module
953
MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249ErrorGroup}
954
::= {mtaCompliances 7}
956
mtaRFC2249FullCompliance MODULE-COMPLIANCE
959
"The compliance statement for RFC 2249 implementations
960
which support the full Mail Monitoring MIB for
961
monitoring of MTAs, associations, and detailed errors."
962
MODULE -- this module
963
MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup,
964
mtaRFC2249ErrorGroup}
965
::= {mtaCompliances 8}
967
mtaRFC2789Compliance MODULE-COMPLIANCE
970
"The compliance statement for RFC 2789 implementations
971
which support the Mail Monitoring MIB for basic
973
MODULE -- this module
974
MANDATORY-GROUPS {mtaRFC2789Group}
975
::= {mtaCompliances 9}
977
mtaRFC2789AssocCompliance MODULE-COMPLIANCE
980
"The compliance statement for RFC 2789 implementations
981
which support the Mail Monitoring MIB for monitoring of
982
MTAs and their associations."
983
MODULE -- this module
984
MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789AssocGroup}
985
::= {mtaCompliances 10}
987
mtaRFC2789ErrorCompliance MODULE-COMPLIANCE
990
"The compliance statement for RFC 2789 implementations
991
which support the Mail Monitoring MIB for monitoring of
992
MTAs and detailed errors."
993
MODULE -- this module
994
MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789ErrorGroup}
995
::= {mtaCompliances 11}
997
mtaRFC2789FullCompliance MODULE-COMPLIANCE
1000
"The compliance statement for RFC 2789 implementations
1001
which support the full Mail Monitoring MIB for
1002
monitoring of MTAs, associations, and detailed errors."
1003
MODULE -- this module
1004
MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789AssocGroup,
1005
mtaRFC2789ErrorGroup}
1006
::= {mtaCompliances 12}
1009
mtaRFC1566Group OBJECT-GROUP
1011
mtaReceivedMessages, mtaStoredMessages,
1012
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1013
mtaTransmittedVolume, mtaReceivedRecipients,
1014
mtaStoredRecipients, mtaTransmittedRecipients,
1015
mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1016
mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1017
mtaGroupReceivedVolume, mtaGroupStoredVolume,
1018
mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1019
mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1020
mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1021
mtaGroupOutboundAssociations,
1022
mtaGroupAccumulatedInboundAssociations,
1023
mtaGroupAccumulatedOutboundAssociations,
1024
mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1025
mtaGroupRejectedInboundAssociations,
1026
mtaGroupFailedOutboundAssociations,
1027
mtaGroupInboundRejectionReason,
1028
mtaGroupOutboundConnectFailureReason,
1029
mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName}
1032
"A collection of objects providing basic monitoring of MTAs.
1033
This is the original set of such objects defined in RFC
1037
mtaRFC1566AssocGroup OBJECT-GROUP
1039
mtaGroupAssociationIndex}
1042
"A collection of objects providing monitoring of MTA
1043
associations. This is the original set of such objects
1044
defined in RFC 1566."
1047
mtaRFC2249Group OBJECT-GROUP
1049
mtaReceivedMessages, mtaStoredMessages,
1050
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1051
mtaTransmittedVolume, mtaReceivedRecipients,
1052
mtaStoredRecipients, mtaTransmittedRecipients,
1053
mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
1054
mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1055
mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1056
mtaGroupReceivedVolume, mtaGroupStoredVolume,
1057
mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1058
mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1059
mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1060
mtaGroupOutboundAssociations, mtaLoopsDetected,
1061
mtaGroupAccumulatedInboundAssociations,
1062
mtaGroupAccumulatedOutboundAssociations,
1063
mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1064
mtaGroupLastOutboundAssociationAttempt,
1065
mtaGroupRejectedInboundAssociations,
1066
mtaGroupFailedOutboundAssociations,
1067
mtaGroupInboundRejectionReason,
1068
mtaGroupOutboundConnectFailureReason,
1069
mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName,
1070
mtaGroupSuccessfulConvertedMessages,
1071
mtaGroupFailedConvertedMessages, mtaGroupDescription,
1072
mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy,
1073
mtaGroupOldestMessageId, mtaGroupLoopsDetected}
1076
"A collection of objects providing basic monitoring of MTAs.
1077
This group was originally defined in RFC 2249."
1080
mtaRFC2249AssocGroup OBJECT-GROUP
1082
mtaGroupAssociationIndex}
1085
"A collection of objects providing monitoring of MTA
1086
associations. This group was originally defined in RFC
1090
mtaRFC2249ErrorGroup OBJECT-GROUP
1092
mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
1093
mtaGroupOutboundErrorCount}
1096
"A collection of objects providing monitoring of
1097
detailed MTA errors. This group was originally defined
1101
mtaRFC2789Group OBJECT-GROUP
1103
mtaReceivedMessages, mtaStoredMessages,
1104
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1105
mtaTransmittedVolume, mtaReceivedRecipients,
1106
mtaStoredRecipients, mtaTransmittedRecipients,
1107
mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
1108
mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1109
mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1110
mtaGroupReceivedVolume, mtaGroupStoredVolume,
1111
mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1112
mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1113
mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1114
mtaGroupOutboundAssociations, mtaLoopsDetected,
1115
mtaGroupAccumulatedInboundAssociations,
1116
mtaGroupAccumulatedOutboundAssociations,
1117
mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1118
mtaGroupLastOutboundAssociationAttempt,
1119
mtaGroupRejectedInboundAssociations,
1120
mtaGroupFailedOutboundAssociations,
1121
mtaGroupInboundRejectionReason,
1122
mtaGroupOutboundConnectFailureReason,
1123
mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName,
1124
mtaGroupSuccessfulConvertedMessages,
1125
mtaGroupFailedConvertedMessages, mtaGroupDescription,
1126
mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy,
1127
mtaGroupOldestMessageId, mtaGroupLoopsDetected}
1130
"A collection of objects providing basic monitoring of MTAs.
1132
This is the appropriate group for RFC 2789."
1135
mtaRFC2789AssocGroup OBJECT-GROUP
1137
mtaGroupAssociationIndex}
1140
"A collection of objects providing monitoring of MTA
1141
associations. This is the appropriate group for RFC
1142
2789 association monitoring."
1145
mtaRFC2789ErrorGroup OBJECT-GROUP
1147
mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
1148
mtaGroupOutboundErrorCount}
1151
"A collection of objects providing monitoring of
1152
detailed MTA errors. This is the appropriate group
1153
for RFC 2789 error monitoring."
added
removed
mibs/MTA-MIB.txt
