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
36 is not strictly supported by SMIv2. However, the alternative
37 of deprecating the old objects and defining new objects
38 would have a more adverse impact on backward compatibility
39 and interoperability, given the particular semantics of
40 these objects. The defining reference for distinguished
41 names has also been updated from RFC 1779 to RFC 2253."
42 REVISION "199905120000Z"
44 "This revision fixes a number of technical problems found in
45 previous versions: The conformance groups for different
46 versions of this MIB have been corrected, the recommendation
47 that an empty string be returned if the last operation was
48 successful has been removed from
49 mtaGroupInboundRejectionReason and
50 mtaGroupOutboundConnectFailureReason as it conflicts
51 with the stated purpose of these variables, and the
52 required mtaStatusCode entry has been added to
53 MtaGroupErrorEntry. It should be noted that this last
54 change in no way affects the bits on the wire."
55 REVISION "199708170000Z"
57 "This revision, published in RFC 2249, adds the
58 mtaGroupDescription and mtaGroupURL fields, conversion
59 operation counters, a group hierarchy description mechanism,
60 counters for specific errors, oldest message IDs, per-MTA
61 and per-group loop counters, and a new table for tracking
62 any errors an MTA encounters."
63 REVISION "199311280000Z"
65 "The original version of this MIB was published in RFC 1566"
69 SYNTAX SEQUENCE OF MtaEntry
70 MAX-ACCESS not-accessible
73 "The table holding information specific to an MTA."
78 MAX-ACCESS not-accessible
81 "The entry associated with each MTA."
85 MtaEntry ::= SEQUENCE {
90 mtaTransmittedMessages
102 mtaTransmittedRecipients
104 mtaSuccessfulConvertedMessages
106 mtaFailedConvertedMessages
112 mtaReceivedMessages OBJECT-TYPE
117 "The number of messages received since MTA initialization.
118 This includes messages transmitted to this MTA from other
119 MTAs as well as messages that have been submitted to the
120 MTA directly by end-users or applications."
123 mtaStoredMessages OBJECT-TYPE
128 "The total number of messages currently stored in the MTA.
129 This includes messages that are awaiting transmission to
130 some other MTA or are waiting for delivery to an end-user
134 mtaTransmittedMessages OBJECT-TYPE
139 "The number of messages transmitted since MTA initialization.
140 This includes messages that were transmitted to some other
141 MTA or are waiting for delivery to an end-user or
145 mtaReceivedVolume OBJECT-TYPE
151 "The total volume of messages received since MTA
152 initialization, measured in kilo-octets. This volume should
153 include all transferred data that is logically above the mail
154 transport protocol level. For example, an SMTP-based MTA
155 should use the number of kilo-octets in the message header
156 and body, while an X.400-based MTA should use the number of
157 kilo-octets of P2 data. This includes messages transmitted
158 to this MTA from other MTAs as well as messages that have
159 been submitted to the MTA directly by end-users or
163 mtaStoredVolume OBJECT-TYPE
169 "The total volume of messages currently stored in the MTA,
170 measured in kilo-octets. This volume should include all
171 stored data that is logically above the mail transport
172 protocol level. For example, an SMTP-based MTA should
173 use the number of kilo-octets in the message header and
174 body, while an X.400-based MTA would use the number of
175 kilo-octets of P2 data. This includes messages that are
176 awaiting transmission to some other MTA or are waiting
177 for delivery to an end-user or application."
180 mtaTransmittedVolume OBJECT-TYPE
186 "The total volume of messages transmitted since MTA
187 initialization, measured in kilo-octets. This volume should
188 include all transferred data that is logically above the mail
189 transport protocol level. For example, an SMTP-based MTA
190 should use the number of kilo-octets in the message header
191 and body, while an X.400-based MTA should use the number of
192 kilo-octets of P2 data. This includes messages that were
193 transmitted to some other MTA or are waiting for delivery
194 to an end-user or application."
197 mtaReceivedRecipients OBJECT-TYPE
202 "The total number of recipients specified in all messages
203 received since MTA initialization. Recipients this MTA
204 has no responsibility for, i.e. inactive envelope
205 recipients or ones referred to in message headers,
206 should not be counted even if information about such
207 recipients is available. This includes messages
208 transmitted to this MTA from other MTAs as well as
209 messages that have been submitted to the MTA directly
210 by end-users or applications."
213 mtaStoredRecipients OBJECT-TYPE
218 "The total number of recipients specified in all messages
219 currently stored in the MTA. Recipients this MTA has no
220 responsibility for, i.e. inactive envelope recipients or
221 ones referred to in message headers, should not be
222 counted. This includes messages that are awaiting
223 transmission to some other MTA or are waiting for
224 delivery to an end-user or application."
227 mtaTransmittedRecipients OBJECT-TYPE
232 "The total number of recipients specified in all messages
233 transmitted since MTA initialization. Recipients this
234 MTA had no responsibility for, i.e. inactive envelope
235 recipients or ones referred to in message headers,
236 should not be counted. This includes messages that were
237 transmitted to some other MTA or are waiting for
238 delivery to an end-user or application."
241 mtaSuccessfulConvertedMessages OBJECT-TYPE
246 "The number of messages that have been successfully
247 converted from one form to another since MTA
251 mtaFailedConvertedMessages OBJECT-TYPE
256 "The number of messages for which an unsuccessful
257 attempt was made to convert them from one form to
258 another since MTA initialization."
261 mtaLoopsDetected OBJECT-TYPE
266 "A message loop is defined as a situation where the MTA
267 decides that a given message will never be delivered to
268 one or more recipients and instead will continue to
269 loop endlessly through one or more MTAs. This variable
270 counts the number of times the MTA has detected such a
271 situation since MTA initialization. Note that the
272 mechanism MTAs use to detect loops (e.g., trace field
273 counting, count of references to this MTA in a trace
274 field, examination of DNS or other directory information,
275 etc.), the level at which loops are detected (e.g., per
276 message, per recipient, per directory entry, etc.), and
277 the handling of a loop once it is detected (e.g., looping
278 messages are held, looping messages are bounced or sent
279 to the postmaster, messages that the MTA knows will loop
280 won't be accepted, etc.) vary widely from one MTA to the
281 next and cannot be inferred from this variable."
284 -- MTAs typically group inbound reception, queue storage, and
285 -- outbound transmission in some way, rather than accounting for
286 -- such operations only across the MTA as a whole. In the most
287 -- extreme case separate information will be maintained for each
288 -- different entity that receives messages and for each entity
289 -- the MTA stores messages for and delivers messages to. Other
290 -- MTAs may elect to treat all reception equally, all queue
291 -- storage equally, all deliveries equally, or some combination
292 -- of this. Overlapped groupings are also possible, where an MTA
293 -- decomposes its traffic in different ways for different
296 -- In any case, a grouping abstraction is an extremely useful for
297 -- breaking down the activities of an MTA. For purposes of
298 -- labelling this will be called a "group" in this MIB.
300 -- Each group contains all the variables needed to monitor all
301 -- aspects of an MTA's operation. However, the fact that all
302 -- groups contain all possible variables does not imply that all
303 -- groups must use all possible variables. For example, a single
304 -- group might be used to monitor only one kind of event (inbound
305 -- processing, outbound processing, or storage). In this sort of
306 -- configuration any counters that are unused as a result of a
307 -- given MTA's use of the group construct must be inaccessible;
308 -- e.g., returning either a noSuchName error (for an SNMPv1 get),
309 -- or a noSuchInstance exception (for an SNMPv2 get).
311 -- Groups can be created at any time after MTA initialization. Once
312 -- a group is created it should not be deleted or its mtaGroupIndex
313 -- changed unless the MTA is reinitialized.
315 -- Groups are not necessarily mutually exclusive. A given event may
316 -- be recorded by more than one group, a message may be seen as
317 -- stored by more than one group, and so on. Groups should be all
318 -- inclusive, however: if groups are implemented all aspects of an
319 -- MTA's operation should be registered in at least one group.
320 -- This freedom lets implementors use different sets of groups to
321 -- provide different "views" of an MTA.
323 -- The possibility of overlap between groups means that summing
324 -- variables across groups may not produce values equal to those in
325 -- the mtaTable. mtaTable should always provide accurate information
327 -- about the MTA as a whole.
329 -- The term "channel" is often used in MTA implementations; channels
330 -- are usually, but not always, equivalent to a group. However,
331 -- this MIB does not use the term "channel" because there is no
332 -- requirement that an MTA supporting this MIB has to map its
333 -- "channel" abstraction one-to-one onto the MIB's group abstraction.
335 -- An MTA may create a group or group of groups at any time. Once
336 -- created, however, an MTA cannot delete an entry for a group from
337 -- the group table. Deletion is only allowed when the MTA is
338 -- reinitialized, and is not required even then. This restriction
339 -- is imposed so that monitoring agents can rely on group
340 -- assignments being consistent across multiple query operations.
342 -- Groups may be laid out so as to form a hierarchical arrangement,
343 -- with some groups acting as subgroups for other groups.
344 -- Alternately, disjoint groups of groups may be used to provide
345 -- different sorts of "snapshots" of MTA operation. The
346 -- mtaGroupHierarchy variable provides an indication of how each
347 -- group fits into the overall arrangement being used.
349 -- Note that SNMP also defines and uses term "group". MTA groups are
350 -- NOT the same as SNMP groups.
352 mtaGroupTable OBJECT-TYPE
353 SYNTAX SEQUENCE OF MtaGroupEntry
354 MAX-ACCESS not-accessible
357 "The table holding information specific to each MTA group."
360 mtaGroupEntry OBJECT-TYPE
362 MAX-ACCESS not-accessible
365 "The entry associated with each MTA group."
366 INDEX {applIndex, mtaGroupIndex}
367 ::= {mtaGroupTable 1}
369 MtaGroupEntry ::= SEQUENCE {
372 mtaGroupReceivedMessages
374 mtaGroupRejectedMessages
376 mtaGroupStoredMessages
378 mtaGroupTransmittedMessages
380 mtaGroupReceivedVolume
384 mtaGroupTransmittedVolume
386 mtaGroupReceivedRecipients
388 mtaGroupStoredRecipients
390 mtaGroupTransmittedRecipients
392 mtaGroupOldestMessageStored
394 mtaGroupInboundAssociations
396 mtaGroupOutboundAssociations
398 mtaGroupAccumulatedInboundAssociations
400 mtaGroupAccumulatedOutboundAssociations
402 mtaGroupLastInboundActivity
404 mtaGroupLastOutboundActivity
406 mtaGroupLastOutboundAssociationAttempt
408 mtaGroupRejectedInboundAssociations
410 mtaGroupFailedOutboundAssociations
412 mtaGroupInboundRejectionReason
414 mtaGroupOutboundConnectFailureReason
416 mtaGroupScheduledRetry
422 mtaGroupSuccessfulConvertedMessages
424 mtaGroupFailedConvertedMessages
434 mtaGroupOldestMessageId
436 mtaGroupLoopsDetected
440 mtaGroupIndex OBJECT-TYPE
441 SYNTAX INTEGER (1..2147483647)
442 MAX-ACCESS not-accessible
445 "The index associated with a group for a given MTA."
446 ::= {mtaGroupEntry 1}
448 mtaGroupReceivedMessages OBJECT-TYPE
453 "The number of messages received to this group since
455 ::= {mtaGroupEntry 2}
457 mtaGroupRejectedMessages OBJECT-TYPE
462 "The number of messages rejected by this group since
464 ::= {mtaGroupEntry 3}
466 mtaGroupStoredMessages OBJECT-TYPE
471 "The total number of messages currently stored in this
473 ::= {mtaGroupEntry 4}
475 mtaGroupTransmittedMessages OBJECT-TYPE
480 "The number of messages transmitted by this group since
482 ::= {mtaGroupEntry 5}
484 mtaGroupReceivedVolume OBJECT-TYPE
490 "The total volume of messages received to this group since
491 group creation, measured in kilo-octets. This volume
492 should include all transferred data that is logically above
493 the mail transport protocol level. For example, an
494 SMTP-based MTA should use the number of kilo-octets in the
495 message header and body, while an X.400-based MTA should use
496 the number of kilo-octets of P2 data."
497 ::= {mtaGroupEntry 6}
499 mtaGroupStoredVolume OBJECT-TYPE
505 "The total volume of messages currently stored in this
506 group's queue, measured in kilo-octets. This volume should
507 include all stored data that is logically above the mail
508 transport protocol level. For example, an SMTP-based
509 MTA should use the number of kilo-octets in the message
510 header and body, while an X.400-based MTA would use the
511 number of kilo-octets of P2 data."
512 ::= {mtaGroupEntry 7}
514 mtaGroupTransmittedVolume OBJECT-TYPE
520 "The total volume of messages transmitted by this group
521 since group creation, measured in kilo-octets. This
522 volume should include all transferred data that is logically
523 above the mail transport protocol level. For example, an
524 SMTP-based MTA should use the number of kilo-octets in the
525 message header and body, while an X.400-based MTA should use
526 the number of kilo-octets of P2 data."
527 ::= {mtaGroupEntry 8}
529 mtaGroupReceivedRecipients OBJECT-TYPE
534 "The total number of recipients specified in all messages
535 received to this group since group creation.
536 Recipients this MTA has no responsibility for should not
538 ::= {mtaGroupEntry 9}
540 mtaGroupStoredRecipients OBJECT-TYPE
545 "The total number of recipients specified in all messages
546 currently stored in this group's queue. Recipients this
547 MTA has no responsibility for should not be counted."
548 ::= {mtaGroupEntry 10}
550 mtaGroupTransmittedRecipients OBJECT-TYPE
555 "The total number of recipients specified in all messages
556 transmitted by this group since group creation.
557 Recipients this MTA had no responsibility for should not
559 ::= {mtaGroupEntry 11}
561 mtaGroupOldestMessageStored OBJECT-TYPE
566 "Time since the oldest message in this group's queue was
567 placed in the queue."
568 ::= {mtaGroupEntry 12}
570 mtaGroupInboundAssociations OBJECT-TYPE
575 "The number of current associations to the group, where the
576 group is the responder."
577 ::= {mtaGroupEntry 13}
579 mtaGroupOutboundAssociations OBJECT-TYPE
584 "The number of current associations to the group, where the
585 group is the initiator."
586 ::= {mtaGroupEntry 14}
588 mtaGroupAccumulatedInboundAssociations OBJECT-TYPE
593 "The total number of associations to the group since
594 group creation, where the MTA was the responder."
595 ::= {mtaGroupEntry 15}
597 mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE
602 "The total number of associations from the group since
603 group creation, where the MTA was the initiator."
604 ::= {mtaGroupEntry 16}
606 mtaGroupLastInboundActivity OBJECT-TYPE
611 "Time since the last time that this group had an active
612 inbound association for purposes of message reception."
613 ::= {mtaGroupEntry 17}
615 mtaGroupLastOutboundActivity OBJECT-TYPE
620 "Time since the last time that this group had a
621 successful outbound association for purposes of
623 ::= {mtaGroupEntry 18}
625 mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE
630 "Time since the last time that this group attempted
631 to make an outbound association for purposes of
633 ::= {mtaGroupEntry 34}
635 mtaGroupRejectedInboundAssociations OBJECT-TYPE
640 "The total number of inbound associations the group has
641 rejected, since group creation. Rejected associations
642 are not counted in the accumulated association totals."
643 ::= {mtaGroupEntry 19}
645 mtaGroupFailedOutboundAssociations OBJECT-TYPE
650 "The total number associations where the group was the
651 initiator and association establishment has failed,
652 since group creation. Failed associations are
653 not counted in the accumulated association totals."
654 ::= {mtaGroupEntry 20}
656 mtaGroupInboundRejectionReason OBJECT-TYPE
657 SYNTAX SnmpAdminString
661 "The failure reason, if any, for the last association this
662 group refused to respond to. If no association attempt
663 has been made since the MTA was initialized the value
665 ::= {mtaGroupEntry 21}
667 mtaGroupOutboundConnectFailureReason OBJECT-TYPE
668 SYNTAX SnmpAdminString
672 "The failure reason, if any, for the last association attempt
673 this group initiated. If no association attempt has been
674 made since the MTA was initialized the value should be
676 ::= {mtaGroupEntry 22}
678 mtaGroupScheduledRetry OBJECT-TYPE
683 "The amount of time until this group is next scheduled to
684 attempt to make an association."
685 ::= {mtaGroupEntry 23}
687 mtaGroupMailProtocol OBJECT-TYPE
688 SYNTAX OBJECT IDENTIFIER
692 "An identification of the protocol being used by this group.
693 For an group employing OSI protocols, this will be the
694 Application Context. For Internet applications, OID
695 values of the form {applTCPProtoID port} or {applUDPProtoID
696 port} are used for TCP-based and UDP-based protocols,
697 respectively. In either case 'port' corresponds to the
698 primary port number being used by the protocol. The
699 usual IANA procedures may be used to register ports for
700 new protocols. applTCPProtoID and applUDPProtoID are
701 defined in the NETWORK-SERVICES-MIB, RFC 2788."
702 ::= {mtaGroupEntry 24}
704 mtaGroupName OBJECT-TYPE
705 SYNTAX SnmpAdminString
709 "A descriptive name for the group. If this group connects to
710 a single remote MTA this should be the name of that MTA. If
711 this in turn is an Internet MTA this should be the domain
712 name. For an OSI MTA it should be the string encoded
713 distinguished name of the managed object using the format
714 defined in RFC 2253. For X.400(1984) MTAs which do not
715 have a Distinguished Name, the RFC 2156 syntax
716 'mta in globalid' used in X400-Received: fields can be
718 ::= {mtaGroupEntry 25}
720 mtaGroupSuccessfulConvertedMessages OBJECT-TYPE
725 "The number of messages that have been successfully
726 converted from one form to another in this group
727 since group creation."
728 ::= {mtaGroupEntry 26}
730 mtaGroupFailedConvertedMessages OBJECT-TYPE
735 "The number of messages for which an unsuccessful
736 attempt was made to convert them from one form to
737 another in this group since group creation."
738 ::= {mtaGroupEntry 27}
740 mtaGroupDescription OBJECT-TYPE
741 SYNTAX SnmpAdminString
745 "A description of the group's purpose. This information is
746 intended to identify the group in a status display."
747 ::= {mtaGroupEntry 28}
749 mtaGroupURL OBJECT-TYPE
754 "A URL pointing to a description of the group. This
755 information is intended to identify and briefly describe
756 the group in a status display."
757 ::= {mtaGroupEntry 29}
759 mtaGroupCreationTime OBJECT-TYPE
764 "Time since this group was first created."
765 ::= {mtaGroupEntry 30}
767 mtaGroupHierarchy OBJECT-TYPE
768 SYNTAX INTEGER (-2147483648..2147483647)
772 "Describes how this group fits into the hierarchy. A
773 positive value is interpreted as an mtaGroupIndex
774 value for some other group whose variables include
775 those of this group (and usually others). A negative
776 value is interpreted as a group collection code: Groups
777 with common negative hierarchy values comprise one
778 particular breakdown of MTA activity as a whole. A
779 zero value means that this MIB implementation doesn't
780 implement hierarchy indicators and thus the overall
781 group hierarchy cannot be determined."
782 ::= {mtaGroupEntry 31}
784 mtaGroupOldestMessageId OBJECT-TYPE
785 SYNTAX SnmpAdminString
789 "Message ID of the oldest message in the group's queue.
790 Whenever possible this should be in the form of an
791 RFC 822 msg-id; X.400 may convert X.400 message
792 identifiers to this form by following the rules laid
794 ::= {mtaGroupEntry 32}
796 mtaGroupLoopsDetected OBJECT-TYPE
801 "A message loop is defined as a situation where the MTA
802 decides that a given message will never be delivered to
803 one or more recipients and instead will continue to
804 loop endlessly through one or more MTAs. This variable
805 counts the number of times the MTA has detected such a
806 situation in conjunction with something associated with
807 this group since group creation. Note that the
808 mechanism MTAs use to detect loops (e.g., trace field
809 counting, count of references to this MTA in a trace
810 field, examination of DNS or other directory information,
811 etc.), the level at which loops are detected (e.g., per
812 message, per recipient, per directory entry, etc.), and
813 the handling of a loop once it is detected (e.g., looping
814 messages are held, looping messages are bounced or sent
815 to the postmaster, messages that the MTA knows will loop
816 won't be accepted, etc.) vary widely from one MTA to the
817 next and cannot be inferred from this variable."
818 ::= {mtaGroupEntry 33}
820 -- The mtaGroupAssociationTable provides a means of correlating
821 -- entries in the network services association table with the
822 -- MTA group responsible for the association.
824 mtaGroupAssociationTable OBJECT-TYPE
825 SYNTAX SEQUENCE OF MtaGroupAssociationEntry
826 MAX-ACCESS not-accessible
829 "The table holding information regarding the associations
833 mtaGroupAssociationEntry OBJECT-TYPE
834 SYNTAX MtaGroupAssociationEntry
835 MAX-ACCESS not-accessible
838 "The entry holding information regarding the associations
840 INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex}
841 ::= {mtaGroupAssociationTable 1}
843 MtaGroupAssociationEntry ::= SEQUENCE {
844 mtaGroupAssociationIndex
848 mtaGroupAssociationIndex OBJECT-TYPE
849 SYNTAX INTEGER (1..2147483647)
853 "Reference into association table to allow correlation of
854 this group's active associations with the association table."
855 ::= {mtaGroupAssociationEntry 1}
857 -- The mtaGroupErrorTable gives each group a way of tallying
858 -- the specific errors it has encountered. The mechanism
859 -- defined here uses RFC 1893 status codes to identify
860 -- various specific errors. There are also classes for generic
861 -- errors of various sorts, and the entire mechanism is also
862 -- extensible, in that new error codes can be defined at any
865 mtaGroupErrorTable OBJECT-TYPE
866 SYNTAX SEQUENCE OF MtaGroupErrorEntry
867 MAX-ACCESS not-accessible
870 "The table holding information regarding accumulated errors
874 mtaGroupErrorEntry OBJECT-TYPE
875 SYNTAX MtaGroupErrorEntry
876 MAX-ACCESS not-accessible
879 "The entry holding information regarding accumulated
880 errors for each MTA group."
881 INDEX {applIndex, mtaGroupIndex, mtaStatusCode}
882 ::= {mtaGroupErrorTable 1}
884 MtaGroupErrorEntry ::= SEQUENCE {
887 mtaGroupInboundErrorCount
889 mtaGroupInternalErrorCount
891 mtaGroupOutboundErrorCount
895 mtaGroupInboundErrorCount OBJECT-TYPE
900 "Count of the number of errors of a given type that have
901 been accumulated in association with a particular group
902 while processing incoming messages. In the case of SMTP
903 these will typically be errors reporting by an SMTP
904 server to the remote client; in the case of X.400
905 these will typically be errors encountered while
906 processing an incoming message."
907 ::= {mtaGroupErrorEntry 1}
909 mtaGroupInternalErrorCount OBJECT-TYPE
914 "Count of the number of errors of a given type that have
915 been accumulated in association with a particular group
916 during internal MTA processing."
917 ::= {mtaGroupErrorEntry 2}
919 mtaGroupOutboundErrorCount OBJECT-TYPE
924 "Count of the number of errors of a given type that have
925 been accumulated in association with a particular group's
926 outbound connection activities. In the case of an SMTP
927 client these will typically be errors reported while
928 attempting to contact or while communicating with the
929 remote SMTP server. In the case of X.400 these will
930 typically be errors encountered while constructing
931 or attempting to deliver an outgoing message."
932 ::= {mtaGroupErrorEntry 3}
934 mtaStatusCode OBJECT-TYPE
935 SYNTAX INTEGER (4000000..5999999)
936 MAX-ACCESS not-accessible
939 "An index capable of representing an Enhanced Mail System
940 Status Code. Enhanced Mail System Status Codes are
941 defined in RFC 1893. These codes have the form
945 Here 'class' is either 2, 4, or 5 and both 'subject' and
946 'detail' are integers in the range 0..999. Given a status
947 code the corresponding index value is defined to be
948 ((class * 1000) + subject) * 1000 + detail. Both SMTP
949 error response codes and X.400 reason and diagnostic codes
950 can be mapped into these codes, resulting in a namespace
951 capable of describing most error conditions a mail system
952 encounters in a generic yet detailed way."
953 ::= {mtaGroupErrorEntry 4}
955 -- Conformance information
957 mtaConformance OBJECT IDENTIFIER ::= {mta 4}
959 mtaGroups OBJECT IDENTIFIER ::= {mtaConformance 1}
960 mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2}
963 -- Compliance statements
965 mtaCompliance MODULE-COMPLIANCE
968 "The compliance statement for RFC 1566 implementations
969 which support the Mail Monitoring MIB for basic
971 MODULE -- this module
972 MANDATORY-GROUPS {mtaRFC1566Group}
973 ::= {mtaCompliances 1}
975 mtaAssocCompliance MODULE-COMPLIANCE
978 "The compliance statement for RFC 1566 implementations
979 which support the Mail Monitoring MIB for monitoring
980 of MTAs and their associations."
981 MODULE -- this module
982 MANDATORY-GROUPS {mtaRFC1566Group, mtaRFC1566AssocGroup}
983 ::= {mtaCompliances 2}
985 mtaRFC2249Compliance MODULE-COMPLIANCE
988 "The compliance statement for RFC 2249 implementations
989 which support the Mail Monitoring MIB for basic
991 MODULE -- this module
992 MANDATORY-GROUPS {mtaRFC2249Group}
993 ::= {mtaCompliances 5}
995 mtaRFC2249AssocCompliance MODULE-COMPLIANCE
998 "The compliance statement for RFC 2249 implementations
999 which support the Mail Monitoring MIB for monitoring of
1000 MTAs and their associations."
1001 MODULE -- this module
1002 MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup}
1003 ::= {mtaCompliances 6}
1005 mtaRFC2249ErrorCompliance MODULE-COMPLIANCE
1008 "The compliance statement for RFC 2249 implementations
1009 which support the Mail Monitoring MIB for monitoring of
1010 MTAs and detailed errors."
1011 MODULE -- this module
1012 MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249ErrorGroup}
1013 ::= {mtaCompliances 7}
1015 mtaRFC2249FullCompliance MODULE-COMPLIANCE
1018 "The compliance statement for RFC 2249 implementations
1019 which support the full Mail Monitoring MIB for
1020 monitoring of MTAs, associations, and detailed errors."
1021 MODULE -- this module
1022 MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup,
1023 mtaRFC2249ErrorGroup}
1024 ::= {mtaCompliances 8}
1026 mtaRFC2789Compliance MODULE-COMPLIANCE
1029 "The compliance statement for RFC 2789 implementations
1030 which support the Mail Monitoring MIB for basic
1031 monitoring of MTAs."
1032 MODULE -- this module
1033 MANDATORY-GROUPS {mtaRFC2789Group}
1034 ::= {mtaCompliances 9}
1036 mtaRFC2789AssocCompliance MODULE-COMPLIANCE
1039 "The compliance statement for RFC 2789 implementations
1040 which support the Mail Monitoring MIB for monitoring of
1041 MTAs and their associations."
1042 MODULE -- this module
1043 MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789AssocGroup}
1044 ::= {mtaCompliances 10}
1046 mtaRFC2789ErrorCompliance MODULE-COMPLIANCE
1049 "The compliance statement for RFC 2789 implementations
1050 which support the Mail Monitoring MIB for monitoring of
1051 MTAs and detailed errors."
1052 MODULE -- this module
1053 MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789ErrorGroup}
1054 ::= {mtaCompliances 11}
1056 mtaRFC2789FullCompliance MODULE-COMPLIANCE
1059 "The compliance statement for RFC 2789 implementations
1060 which support the full Mail Monitoring MIB for
1061 monitoring of MTAs, associations, and detailed errors."
1062 MODULE -- this module
1063 MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789AssocGroup,
1064 mtaRFC2789ErrorGroup}
1065 ::= {mtaCompliances 12}
1067 -- Units of conformance
1069 mtaRFC1566Group OBJECT-GROUP
1071 mtaReceivedMessages, mtaStoredMessages,
1072 mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1073 mtaTransmittedVolume, mtaReceivedRecipients,
1074 mtaStoredRecipients, mtaTransmittedRecipients,
1075 mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1076 mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1077 mtaGroupReceivedVolume, mtaGroupStoredVolume,
1078 mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1079 mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1080 mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1081 mtaGroupOutboundAssociations,
1082 mtaGroupAccumulatedInboundAssociations,
1083 mtaGroupAccumulatedOutboundAssociations,
1084 mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1085 mtaGroupRejectedInboundAssociations,
1086 mtaGroupFailedOutboundAssociations,
1087 mtaGroupInboundRejectionReason,
1088 mtaGroupOutboundConnectFailureReason,
1089 mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName}
1092 "A collection of objects providing basic monitoring of MTAs.
1093 This is the original set of such objects defined in RFC
1097 mtaRFC1566AssocGroup OBJECT-GROUP
1099 mtaGroupAssociationIndex}
1102 "A collection of objects providing monitoring of MTA
1103 associations. This is the original set of such objects
1104 defined in RFC 1566."
1107 mtaRFC2249Group OBJECT-GROUP
1109 mtaReceivedMessages, mtaStoredMessages,
1110 mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1111 mtaTransmittedVolume, mtaReceivedRecipients,
1112 mtaStoredRecipients, mtaTransmittedRecipients,
1113 mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
1114 mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1115 mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1116 mtaGroupReceivedVolume, mtaGroupStoredVolume,
1117 mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1118 mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1119 mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1120 mtaGroupOutboundAssociations, mtaLoopsDetected,
1121 mtaGroupAccumulatedInboundAssociations,
1122 mtaGroupAccumulatedOutboundAssociations,
1123 mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1124 mtaGroupLastOutboundAssociationAttempt,
1125 mtaGroupRejectedInboundAssociations,
1126 mtaGroupFailedOutboundAssociations,
1127 mtaGroupInboundRejectionReason,
1128 mtaGroupOutboundConnectFailureReason,
1129 mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName,
1130 mtaGroupSuccessfulConvertedMessages,
1131 mtaGroupFailedConvertedMessages, mtaGroupDescription,
1132 mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy,
1133 mtaGroupOldestMessageId, mtaGroupLoopsDetected}
1136 "A collection of objects providing basic monitoring of MTAs.
1137 This group was originally defined in RFC 2249."
1140 mtaRFC2249AssocGroup OBJECT-GROUP
1142 mtaGroupAssociationIndex}
1145 "A collection of objects providing monitoring of MTA
1146 associations. This group was originally defined in RFC
1150 mtaRFC2249ErrorGroup OBJECT-GROUP
1152 mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
1153 mtaGroupOutboundErrorCount}
1156 "A collection of objects providing monitoring of
1157 detailed MTA errors. This group was originally defined
1161 mtaRFC2789Group OBJECT-GROUP
1163 mtaReceivedMessages, mtaStoredMessages,
1164 mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
1165 mtaTransmittedVolume, mtaReceivedRecipients,
1166 mtaStoredRecipients, mtaTransmittedRecipients,
1167 mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
1168 mtaGroupReceivedMessages, mtaGroupRejectedMessages,
1169 mtaGroupStoredMessages, mtaGroupTransmittedMessages,
1170 mtaGroupReceivedVolume, mtaGroupStoredVolume,
1171 mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
1172 mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
1173 mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
1174 mtaGroupOutboundAssociations, mtaLoopsDetected,
1175 mtaGroupAccumulatedInboundAssociations,
1176 mtaGroupAccumulatedOutboundAssociations,
1177 mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
1178 mtaGroupLastOutboundAssociationAttempt,
1179 mtaGroupRejectedInboundAssociations,
1180 mtaGroupFailedOutboundAssociations,
1181 mtaGroupInboundRejectionReason,
1182 mtaGroupOutboundConnectFailureReason,
1183 mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName,
1184 mtaGroupSuccessfulConvertedMessages,
1185 mtaGroupFailedConvertedMessages, mtaGroupDescription,
1186 mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy,
1187 mtaGroupOldestMessageId, mtaGroupLoopsDetected}
1190 "A collection of objects providing basic monitoring of MTAs.
1191 This is the appropriate group for RFC 2789."
1194 mtaRFC2789AssocGroup OBJECT-GROUP
1196 mtaGroupAssociationIndex}
1199 "A collection of objects providing monitoring of MTA
1200 associations. This is the appropriate group for RFC
1201 2789 association monitoring."
1204 mtaRFC2789ErrorGroup OBJECT-GROUP
1206 mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
1207 mtaGroupOutboundErrorCount}
1210 "A collection of objects providing monitoring of
1211 detailed MTA errors. This is the appropriate group
1212 for RFC 2789 error monitoring."