[要約] RFC 2249は、電子メールの監視に関する管理情報ベース（MIB）を定義しています。その目的は、ネットワーク管理者が電子メールのトラフィックを監視し、問題を特定するための情報を提供することです。
Network Working Group N. Freed
Request for Comments: 2249 Innosoft
Obsoletes: 1566 S. Kille
Category: Standards Track ISODE Consortium
January 1998
Mail Monitoring MIB
メール監視MIB
Status of this Memo
本文書の状態
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
このドキュメントは、インターネットコミュニティのインターネット標準トラックプロトコルを指定し、改善のための議論と提案を要求します。このプロトコルの標準化状態とステータスについては、「インターネット公式プロトコル標準」（STD 1）の最新版を参照してください。このメモの配布は無制限です。
Copyright Notice
著作権表示
Copyright (C) The Internet Society (1998). All Rights Reserved.
Copyright（C）The Internet Society（1998）。全著作権所有。
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Specifically, this memo extends the basic Network Services Monitoring MIB [8] to allow monitoring of Message Transfer Agents (MTAs). It may also be used to monitor MTA components within gateways.
このメモは、インターネットコミュニティのネットワーク管理プロトコルで使用するための管理情報ベース（MIB）の一部を定義します。具体的には、このメモは基本的なネットワークサービス監視MIB [8]を拡張して、メッセージ転送エージェント（MTA）の監視を可能にします。ゲートウェイ内のMTAコンポーネントの監視にも使用できます。
1 Introduction ............................................. 1
2 Table of Contents ........................................ 1
3 The SNMPv2 Network Management Framework .................. 2
3.1 Object Definitions ..................................... 2
4 Message Flow Model ....................................... 2
5 MTA Objects .............................................. 3
6 Definitions .............................................. 4
7 Changes made since RFC 1566 .............................. 25
8 Acknowledgements ......................................... 26
9 References ............................................... 26
10 Security Considerations ................................. 27
11 Author and Chair Addresses .............................. 27
12 Full Copyright Statement ................................ 28
The SNMPv2 Network Management Framework consists of seven major components. They are:
SNMPv2ネットワーク管理フレームワークは、7つの主要コンポーネントで構成されています。彼らです：
o RFC 1902 [1] which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management.
o RFC 1902 [1]は、SMIを定義します。これは、管理の目的でオブジェクトの説明と命名に使用されるメカニズムです。
o RFC 1903 [2] defines textual conventions for SNMPv2.
o RFC 1903 [2]は、SNMPv2のテキスト表記法を定義しています。
o RFC 1904 [3] defines conformance statements for SNMPv2.
o RFC 1904 [3]は、SNMPv2の準拠ステートメントを定義しています。
o RFC 1905 [4] defines transport mappings for SNMPv2.
o RFC 1905 [4]は、SNMPv2のトランスポートマッピングを定義しています。
o RFC 1906 [5] defines the protocol operations used for network access to managed objects.
o RFC 1906 [5]は、管理対象オブジェクトへのネットワークアクセスに使用されるプロトコル操作を定義しています。
o RFC 1907 [6] defines the Management Information Base for SNMPv2.
o RFC 1907 [6]は、SNMPv2の管理情報ベースを定義しています。
o RFC 1908 [7] specifies coexistance between SNMP and SNMPv2.
o RFC 1908 [7]は、SNMPとSNMPv2の共存を規定しています。
The Framework permits new objects to be defined for the purpose of experimentation and evaluation.
フレームワークでは、実験と評価の目的で新しいオブジェクトを定義できます。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type.
管理対象オブジェクトは、管理情報ベースまたはMIBと呼ばれる仮想情報ストアを介してアクセスされます。 MIB内のオブジェクトは、SMIで定義された抽象構文記法1（ASN.1）のサブセットを使用して定義されます。特に、各オブジェクトタイプには、管理上割り当てられた名前であるOBJECT IDENTIFIERによって名前が付けられます。オブジェクトタイプとオブジェクトインスタンスは、オブジェクトの特定のインスタンス化を一意に識別するのに役立ちます。人間の便宜のため、記述子と呼ばれるテキスト文字列を使用してオブジェクトタイプを参照することがよくあります。
A general model of message flow inside an MTA has to be presented before a MIB can be described. Generally speaking, message flow is modelled as occuring in four steps:
MTA内のメッセージフローの一般的なモデルは、MIBを説明する前に提示する必要があります。一般的に、メッセージフローは4つのステップで発生するようにモデル化されています。
(1) Messages are received by the MTA from User Agents, Message Stores, other MTAs, and gateways.
（1）MTAは、ユーザーエージェント、メッセージストア、その他のMTA、ゲートウェイからメッセージを受信します。
(2) The "next hop" for the each message is determined. This is simply the destination the message is to be transmitted to; it may or may not be the final destination of the message.
（2）各メッセージの「ネクストホップ」が決定されます。これは単にメッセージが送信される宛先です。メッセージの最終宛先である場合とそうでない場合があります。
Multiple "next hops" may exist for a single message (as a result of either having multiple recipients or distribution list expansion); this may make it necessary to duplicate messages.
1つのメッセージに対して複数の「ネクストホップ」が存在する可能性があります（複数の受信者または配布リストの展開があるため）。これにより、メッセージの複製が必要になる場合があります。
(3) If necessary messages are converted into the format that's appropriate for the next hop. Conversion operations may be successful or unsuccessful.
（3）必要な場合、メッセージはネクストホップに適した形式に変換されます。変換操作は成功する場合と失敗する場合があります。
(4) Messages are transmitted to the appropriate destination, which may be a User Agent, Message Store, another MTA, or gateway.
（4）メッセージは適切な宛先（ユーザーエージェント、メッセージストア、別のMTA、ゲートウェイなど）に送信されます。
Storage of messages in the MTA occurs at some point during this process. However, it is important to note that storage may occur at different and possibly even multiple points during this process. For example, some MTAs expand messages into multiple copies as they are received. In this case (1), (2), and (3) may all occur prior to storage. Other MTAs store messages precisely as they are received and perform all expansions and conversions during retransmission processing. So here only (1) occurs prior to storage. This leads to situations where, in general, a measurement of messages received may not equal a measurement of messages in store, or a measurement of messages stored may not equal a measurement of messages retransmitted, or both.
MTAへのメッセージの保存は、このプロセスのある時点で行われます。ただし、ストレージは、このプロセス中のさまざまなポイントで、場合によっては複数のポイントで発生する可能性があることに注意することが重要です。たとえば、一部のMTAは、受信時にメッセージを複数のコピーに展開します。この場合、（1）、（2）、および（3）はすべて保管前に発生する可能性があります。他のMTAは、メッセージを受信したとおりに格納し、再送信処理中にすべての拡張と変換を実行します。したがって、ここでは（1）のみがストレージの前に発生します。これにより、一般に、受信したメッセージの測定値がストア内のメッセージの測定値と等しくない場合や、格納されたメッセージの測定値が再送信されたメッセージの測定値と等しくない場合、またはその両方が発生します。
If there are one or more MTAs on the host, the following MIB may be used to monitor them. Any number of the MTAs on a single host or group of hosts may be monitored. Each MTA is dealt with as a separate network service and has its own applTable entry in the Network Services Monitoring MIB.
ホスト上に1つ以上のMTAがある場合、次のMIBを使用してそれらを監視できます。単一のホストまたはホストのグループ上のMTAはいくつでも監視できます。各MTAは個別のネットワークサービスとして扱われ、ネットワークサービス監視MIBに独自のapplTableエントリがあります。
The MIB described in this document covers only the portion which is specific to the monitoring of MTAs. The network service related part of the MIB is covered in a separate document [8].
このドキュメントで説明されているMIBは、MTAの監視に固有の部分のみをカバーしています。 MIBのネットワークサービス関連部分は、別のドキュメント[8]で説明されています。
This MIB defines four tables. The first of these contains per-MTA information that isn't specific to any particular part of MTA. The second breaks each MTA down into a collection of separate components called groups. Groups are described in detail in the comments embedded in the MIB below. The third table provides a means of correlating associations tracked by the network services MIB with specific groups within different MTAs. Finally, the fourth table provides a means of tracking any errors encountered during the operation of the MTA. The first two tables must be implemented to conform with this MIB; the last two are optional.
このMIBは4つのテーブルを定義します。これらの最初の部分には、MTAの特定の部分に固有ではないMTAごとの情報が含まれています。 2番目は、各MTAをグループと呼ばれる個別のコンポーネントのコレクションに分割します。グループは、以下のMIBに埋め込まれたコメントで詳細に説明されています。 3番目の表は、ネットワークサービスMIBによって追跡される関連付けを、さまざまなMTA内の特定のグループと関連付ける方法を示しています。最後に、4番目の表は、MTAの操作中に発生したエラーを追跡する手段を提供します。このMIBに準拠するには、最初の2つのテーブルを実装する必要があります。最後の2つはオプションです。
MTA-MIB DEFINITIONS ::= BEGIN
IMPORTS OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI DisplayString, TimeInterval FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF applIndex, URLString FROM NETWORK-SERVICES-MIB;
IMPORTS OBJECT-TYPE、Counter32、Gauge32、MODULE-IDENTITY、mib-2 FROM SNMPv2-SMI DisplayString、TimeInterval FROM SNMPv2-TC MODULE-COMPLIANCE、OBJECT-GROUP FROM SNMPv2-CONF applIndex、URLString FROM NETWORK-SERVICES-MIB;
mta MODULE-IDENTITY LAST-UPDATED "9708170000Z" ORGANIZATION "IETF Mail and Directory Management Working Group" CONTACT-INFO " Ned Freed
mta MODULE-IDENTITY LAST-UPDATED "9708170000Z" ORGANIZATION "IETF Mail and Directory Management Working Group" CONTACT-INFO "Ned Freed
Postal: Innosoft International, Inc. 1050 Lakes Drive West Covina, CA 91790 US
郵便：Innosoft International、Inc. 1050 Lakes Drive West Covina、CA 91790 US
Tel: +1 626 919 3600
Fax: +1 626 919 3614
E-Mail: ned.freed@innosoft.com"
DESCRIPTION
"The MIB module describing Message Transfer Agents (MTAs)"
REVISION "9311280000Z"
DESCRIPTION
"The original version of this MIB was published in RFC 1566"
::= {mib-2 28}
mtaTable OBJECT-TYPE
SYNTAX SEQUENCE OF MtaEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table holding information specific to an MTA."
::= {mta 1}
mtaStatusCode OBJECT-TYPE SYNTAX INTEGER (4000000..5999999) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An index capable of representing an Enhanced Mail System Status Code. Enhanced Mail System Status Codes are defined in RFC 1893 [14]. These codes have the form
mtaStatusCode OBJECT-TYPE SYNTAX INTEGER（4000000..5999999）MAX-ACCESS not-accessible STATUS current DESCRIPTION "拡張メールシステムステータスコードを表すことができるインデックス。拡張メールシステムステータスコードはRFC 1893 [14]で定義されています。これらのコード形をしている
class.subject.detail
class.subject.detail
Here 'class' is either 2, 4, or 5 and both 'subject' and
'detail' are integers in the range 0..999. Given a status
code the corresponding index value is defined to be
((class * 1000) + subject) * 1000 + detail. Both SMTP
error response codes and X.400 reason and diagnostic codes
can be mapped into these codes, resulting in a namespace
capable of describing most error conditions a mail system
encounters in a generic yet detailed way."
::= {mta 6}
mtaEntry OBJECT-TYPE
SYNTAX MtaEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The entry associated with each MTA."
INDEX {applIndex}
::= {mtaTable 1}
MtaEntry ::= SEQUENCE {
mtaReceivedMessages
Counter32,
mtaStoredMessages
Gauge32,
mtaTransmittedMessages
Counter32,
mtaReceivedVolume
Counter32,
mtaStoredVolume
Gauge32,
mtaTransmittedVolume
Counter32,
mtaReceivedRecipients
Counter32,
mtaStoredRecipients
Gauge32,
mtaTransmittedRecipients
Counter32,
mtaSuccessfulConvertedMessages
Counter32,
mtaFailedConvertedMessages
Counter32, mtaLoopsDetected Counter32 }
Counter32、mtaLoopsDetected Counter32}
mtaReceivedMessages OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of messages received since MTA initialization.
This includes messages transmitted to this MTA from other
MTAs as well as messages that have been submitted to the
MTA directly by end-users or applications."
::= {mtaEntry 1}
mtaStoredMessages OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of messages currently stored in the MTA.
This includes messages that are awaiting transmission to
some other MTA or are waiting for delivery to an end-user
or application."
::= {mtaEntry 2}
mtaTransmittedMessages OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of messages transmitted since MTA initialization.
This includes messages that were transmitted to some other
MTA or are waiting for delivery to an end-user or
application."
::= {mtaEntry 3}
mtaReceivedVolume OBJECT-TYPE
SYNTAX Counter32
UNITS "K-octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total volume of messages received since MTA
initialization, measured in kilo-octets. This volume should
include all transferred data that is logically above the mail
transport protocol level. For example, an SMTP-based MTA
should use the number of kilo-octets in the message header
and body, while an X.400-based MTA should use the number of
kilo-octets of P2 data. This includes messages transmitted
to this MTA from other MTAs as well as messages that have
been submitted to the MTA directly by end-users or
applications."
::= {mtaEntry 4}
mtaStoredVolume OBJECT-TYPE
SYNTAX Gauge32
UNITS "K-octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total volume of messages currently stored in the MTA,
measured in kilo-octets. This volume should include all
stored data that is logically above the mail transport
protocol level. For example, an SMTP-based MTA should
use the number of kilo-octets in the message header and
body, while an X.400-based MTA would use the number of
kilo-octets of P2 data. This includes messages that are
awaiting transmission to some other MTA or are waiting
for delivery to an end-user or application."
::= {mtaEntry 5}
mtaTransmittedVolume OBJECT-TYPE
SYNTAX Counter32
UNITS "K-octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total volume of messages transmitted since MTA
initialization, measured in kilo-octets. This volume should
include all transferred data that is logically above the mail
transport protocol level. For example, an SMTP-based MTA
should use the number of kilo-octets in the message header
and body, while an X.400-based MTA should use the number of
kilo-octets of P2 data. This includes messages that were
transmitted to some other MTA or are waiting for delivery
to an end-user or application."
::= {mtaEntry 6}
mtaReceivedRecipients OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of recipients specified in all messages
mtaReceivedRecipients OBJECT-TYPE構文Counter32 MAX-ACCESS読み取り専用ステータス現在の説明「すべてのメッセージで指定された受信者の総数
received since MTA initialization. Recipients this MTA
has no responsibility for, i.e. inactive envelope
recipients or ones referred to in message headers,
should not be counted even if information about such
recipients is available. This includes messages
transmitted to this MTA from other MTAs as well as
messages that have been submitted to the MTA directly
by end-users or applications."
::= {mtaEntry 7}
mtaStoredRecipients OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of recipients specified in all messages
currently stored in the MTA. Recipients this MTA has no
responsibility for, i.e. inactive envelope recipients or
ones referred to in message headers, should not be
counted. This includes messages that are awaiting
transmission to some other MTA or are waiting for
delivery to an end-user or application."
::= {mtaEntry 8}
mtaTransmittedRecipients OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of recipients specified in all messages
transmitted since MTA initialization. Recipients this
MTA had no responsibility for, i.e. inactive envelope
recipients or ones referred to in message headers,
should not be counted. This includes messages that were
transmitted to some other MTA or are waiting for
delivery to an end-user or application."
::= {mtaEntry 9}
mtaSuccessfulConvertedMessages OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of messages that have been successfully
converted from one form to another since MTA
initialization."
::= {mtaEntry 10}
mtaFailedConvertedMessages OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of messages for which an unsuccessful
attempt was made to convert them from one form to
another since MTA initialization."
::= {mtaEntry 11}
mtaLoopsDetected OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A message loop is defined as a situation where the MTA
decides that a given message will never be delivered to
one or more recipients and instead will continue to
loop endlessly through one or more MTAs. This variable
counts the number of times the MTA has detected such a
situation since MTA initialization. Note that the
mechanism MTAs use to detect loops (e.g. trace field
counting, count of references to this MTA in a trace
field, examination of DNS or other directory information,
etc.), the level at which loops are detected (e.g. per
message, per recipient, per directory entry, etc.), and
the handling of a loop once it is detected (e.g. looping
messages are held, looping messages are bounced or sent
to the postmaster, messages that the MTA knows will loop
won't be accepted, etc.) vary widely from one MTA to the
next and cannot be inferred from this variable."
::= {mtaEntry 12}
-- MTAs typically group inbound reception, queue storage, and -- outbound transmission in some way, rather than accounting for -- such operations only across the MTA as a whole. In the most -- extreme case separate information will be maintained for each -- different entity that receives messages and for each entity -- the MTA stores messages for and delivers messages to. Other -- MTAs may elect to treat all reception equally, all queue -- storage equally, all deliveries equally, or some combination -- of this. Overlapped groupings are also possible, where an MTA -- decomposes its traffic in different ways for different -- purposes.
-MTAは通常、インバウンド受信、キューストレージをグループ化します。-アカウンティングではなく、何らかの方法でアウトバウンド送信を行います。-このような操作は、MTA全体でのみ行われます。ほとんどの場合-極端な場合、それぞれについて個別の情報が維持されます-メッセージを受信する異なるエンティティおよび各エンティティに対して-MTAは、メッセージを格納し、メッセージを配信します。その他-MTAは、すべての受信を同等に、すべてのキューを-ストレージを同等に、すべての配信を同等に、またはいくつか組み合わせて-扱うことを選択できます。重複したグループ化も可能です。MTA-トラフィックをさまざまな方法でさまざまな方法で分解します-目的。
-- In any case, a grouping abstraction is an extremely useful for -- breaking down the activities of an MTA. For purposes of -- labelling this will be called a "group" in this MIB.
-いずれにしても、グループ化の抽象化は非常に役立ちます-MTAのアクティビティを分解する。目的-ラベル付けは、このMIBでは「グループ」と呼ばれます。
-- Each group contains all the variables needed to monitor all -- aspects of an MTA's operation. However, the fact that all -- groups contain all possible variables does not imply that all -- groups must use all possible variables. For example, a single -- group might be used to monitor only one kind of event (inbound -- processing, outbound processing, or storage). In this sort of -- configuration all unused counters would be inaccessible; e.g., -- returning either a noSuchName error (for an SNMPv1 get), or a -- noSuchInstance exception (for an SNMPv2 get).
-各グループには、すべてを監視するために必要なすべての変数が含まれています-MTAの操作の側面。ただし、すべて-グループにすべての可能な変数が含まれているという事実は、すべて-グループがすべての可能な変数を使用する必要があることを意味するものではありません。たとえば、単一の-グループを使用して、1種類のイベント（受信-処理、送信処理、またはストレージ）のみを監視できます。この種の-構成では、すべての未使用のカウンターにアクセスできなくなります。たとえば、-noSuchNameエラー（SNMPv1 getの場合）または-noSuchInstance例外（SNMPv2 getの場合）を返します。
-- Groups can be created at any time after MTA initialization. Once -- a group is created it should not be deleted or its mtaGroupIndex -- changed unless the MTA is reinitialized.
-MTAの初期化後はいつでもグループを作成できます。グループが作成されたら、削除したり、そのmtaGroupIndexを変更したりしないでください。MTAが再初期化されない限り、グループは変更されません。
-- Groups are not necessarily mutually exclusive. A given event may -- be recorded by more than one group, a message may be seen as -- stored by more than one group, and so on. Groups should be all -- inclusive, however: if groups are implemented all aspects of an -- MTA's operation should be registered in at least one group. This -- freedom lets implementors use different sets of groups to -- provide differents "views" of an MTA.
-グループは必ずしも相互に排他的ではありません。特定のイベントが-複数のグループによって記録され、メッセージが-と見なされる場合があります-複数のグループによって保存されます。グループはすべてである必要があります。ただし、包括的です。グループがすべての側面で実装されている場合、MTAの操作は少なくとも1つのグループに登録する必要があります。これ-自由は実装者が異なるグループのセットを使用することを可能にします-MTAの異なる "ビュー"を提供します。
-- The possibility of overlap between groups means that summing -- variables across groups may not produce values equal to those in -- the mtaTable. mtaTable should always provide accurate information -- about the MTA as a whole.
-グループ間のオーバーラップの可能性は、合計-グループ間の変数が次のものと等しい値を生成しない可能性があることを意味します-mtaTable。 mtaTableは常に、MTA全体に関する正確な情報を提供する必要があります。
-- The term "channel" is often used in MTA implementations; channels -- are usually, but not always, equivalent to a group. However, -- this MIB does not use the term "channel" because there is no -- requirement that an MTA supporting this MIB has to map its -- "channel" abstraction one-to-one onto the MIB's group abstration.
-「チャネル」という用語は、MTA実装でよく使用されます。チャネル-常にではありませんが、通常はグループと同等です。ただし、-このMIBは「チャネル」という用語を使用しないので、-このMIBをサポートするMTAがマッピングする必要があるという要件-「チャネル」抽象化とMIBのグループ抽象化とを1対1で対応させる必要があります。
-- An MTA may create a group or group of groups at any time. Once -- created, however, an MTA cannot delete an entry for a group from -- the group table. Deletation is only allowed when the MTA is -- reinitialized, and is not required even then. This restriction -- is imposed so that monitoring agents can rely on group -- assignments being consistent across multiple query operations.
-MTAはグループまたはグループのグループをいつでも作成できます。ただし、作成された後、MTAはグループのエントリをグループテーブルから削除できません。削除は、MTAが-再初期化されている場合にのみ許可され、それでも必要ありません。この制限は-監視エージェントがグループに依存できるように課されています-割り当ては複数のクエリ操作にわたって一貫しています。
-- Groups may be laid out so as to form a hierarchical arrangement, -- with some groups acting as subgroups for other groups. -- Alternately, disjoint groups of groups may be used to provide -- different sorts of "snapshots" of MTA operation. The -- mtaGroupHierarchy variable provides an indication of how each -- group fits into the overall arrangement being used.
-グループは、階層配置を形成するようにレイアウトできます-一部のグループは、他のグループのサブグループとして機能します。 -代わりに、グループのばらばらのグループを使用して提供することもできます-MTA操作のさまざまな種類の「スナップショット」。 -mtaGroupHierarchy変数は、各-グループが使用されている全体的な配置に適合するかを示します。
mtaGroupTable OBJECT-TYPE
mtaGroupTable OBJECT-TYPE
SYNTAX SEQUENCE OF MtaGroupEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table holding information specific to each MTA group."
::= {mta 2}
mtaGroupEntry OBJECT-TYPE
SYNTAX MtaGroupEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The entry associated with each MTA group."
INDEX {applIndex, mtaGroupIndex}
::= {mtaGroupTable 1}
MtaGroupEntry ::= SEQUENCE {
mtaGroupIndex
INTEGER,
mtaGroupReceivedMessages
Counter32,
mtaGroupRejectedMessages
Counter32,
mtaGroupStoredMessages
Gauge32,
mtaGroupTransmittedMessages
Counter32,
mtaGroupReceivedVolume
Counter32,
mtaGroupStoredVolume
Gauge32,
mtaGroupTransmittedVolume
Counter32,
mtaGroupReceivedRecipients
Counter32,
mtaGroupStoredRecipients
Gauge32,
mtaGroupTransmittedRecipients
Counter32,
mtaGroupOldestMessageStored
TimeInterval,
mtaGroupInboundAssociations
Gauge32,
mtaGroupOutboundAssociations
Gauge32,
mtaGroupAccumulatedInboundAssociations
Counter32,
mtaGroupAccumulatedOutboundAssociations
Counter32, mtaGroupLastInboundActivity TimeInterval, mtaGroupLastOutboundActivity TimeInterval, mtaGroupLastOutboundAssociationAttempt TimeInterval, mtaGroupRejectedInboundAssociations Counter32, mtaGroupFailedOutboundAssociations Counter32, mtaGroupInboundRejectionReason DisplayString, mtaGroupOutboundConnectFailureReason DisplayString, mtaGroupScheduledRetry TimeInterval, mtaGroupMailProtocol OBJECT IDENTIFIER, mtaGroupName DisplayString, mtaGroupSuccessfulConvertedMessages Counter32, mtaGroupFailedConvertedMessages Counter32, mtaGroupDescription DisplayString, mtaGroupURL URLString, mtaGroupCreationTime TimeInterval, mtaGroupHierarchy INTEGER, mtaGroupOldestMessageId DisplayString, mtaGroupLoopsDetected Counter32 }
Counter32の、mtaGroupLastInboundActivity時間間隔、mtaGroupLastOutboundActivity時間間隔、mtaGroupLastOutboundAssociationAttempt時間間隔、mtaGroupRejectedInboundAssociations Counter32の、mtaGroupFailedOutboundAssociations Counter32の、mtaGroupInboundRejectionReasonのDisplayString、mtaGroupOutboundConnectFailureReasonのDisplayString、mtaGroupScheduledRetry時間間隔、mtaGroupMailProtocolオブジェクト識別子、mtaGroupNameのDisplayString、mtaGroupSuccessfulConvertedMessages Counter32の、mtaGroupFailedConvertedMessages Counter32の、mtaGroupDescriptionのDisplayString、mtaGroupURL URLString、mtaGroupCreationTime時間間隔、mtaGroupHierarchy INTEGER 、mtaGroupOldestMessageId DisplayString、mtaGroupLoopsDetected Counter32}
mtaGroupIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index associated with a group for a given MTA."
::= {mtaGroupEntry 1}
mtaGroupReceivedMessages OBJECT-TYPE
mtaGroupReceivedMessages OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of messages received to this group since
group creation."
::= {mtaGroupEntry 2}
mtaGroupRejectedMessages OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of messages rejected by this group since
group creation."
::= {mtaGroupEntry 3}
mtaGroupStoredMessages OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of messages currently stored in this
group's queue."
::= {mtaGroupEntry 4}
mtaGroupTransmittedMessages OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of messages transmitted by this group since
group creation."
::= {mtaGroupEntry 5}
mtaGroupReceivedVolume OBJECT-TYPE SYNTAX Counter32 UNITS "K-octets" MAX-ACCESS read-only STATUS current DESCRIPTION "The total volume of messages received to this group since group creation, measured in kilo-octets. This volume should include all transferred data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA should use the number of kilo-octets of P2 data."
mtaGroupReceivedVolume OBJECT-TYPE SYNTAX Counter32 UNITS "K-octets" MAX-ACCESS read-only STATUS current DESCRIPTION "このグループに受信されたメッセージの総量。キロオクテットで測定されます。この量には、論理的にはメールトランスポートプロトコルレベルを上回ります。たとえば、SMTPベースのMTAはメッセージヘッダーと本文でキロオクテットの数を使用し、X.400ベースのMTAはP2データのキロオクテットの数を使用する必要があります。 」
::= {mtaGroupEntry 6}
mtaGroupStoredVolume OBJECT-TYPE
SYNTAX Gauge32
UNITS "K-octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total volume of messages currently stored in this
group's queue, measured in kilo-octets. This volume should
include all stored data that is logically above the mail
transport protocol level. For example, an SMTP-based
MTA should use the number of kilo-octets in the message
header and body, while an X.400-based MTA would use the
number of kilo-octets of P2 data."
::= {mtaGroupEntry 7}
mtaGroupTransmittedVolume OBJECT-TYPE
SYNTAX Counter32
UNITS "K-octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total volume of messages transmitted by this group
since group creation, measured in kilo-octets. This
volume should include all transferred data that is logically
above the mail transport protocol level. For example, an
SMTP-based MTA should use the number of kilo-octets in the
message header and body, while an X.400-based MTA should use
the number of kilo-octets of P2 data."
::= {mtaGroupEntry 8}
mtaGroupReceivedRecipients OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of recipients specified in all messages
received to this group since group creation.
Recipients this MTA has no responsibility for should not
be counted."
::= {mtaGroupEntry 9}
mtaGroupStoredRecipients OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION
mtaGroupStoredRecipients OBJECT-TYPE構文Gauge32 MAX-ACCESS読み取り専用ステータス現在の説明
"The total number of recipients specified in all messages
currently stored in this group's queue. Recipients this
MTA has no responsibility for should not be counted."
::= {mtaGroupEntry 10}
mtaGroupTransmittedRecipients OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of recipients specified in all messages
transmitted by this group since group creation.
Recipients this MTA had no responsibility for should not
be counted."
::= {mtaGroupEntry 11}
mtaGroupOldestMessageStored OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time since the oldest message in this group's queue was
placed in the queue."
::= {mtaGroupEntry 12}
mtaGroupInboundAssociations OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of current associations to the group, where the
group is the responder."
::= {mtaGroupEntry 13}
mtaGroupOutboundAssociations OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of current associations to the group, where the
group is the initiator."
::= {mtaGroupEntry 14}
mtaGroupAccumulatedInboundAssociations OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION
mtaGroupAccumulatedInboundAssociations OBJECT-TYPE構文Counter32 MAX-ACCESS読み取り専用ステータス現在の説明
"The total number of associations to the group since
group creation, where the MTA was the responder."
::= {mtaGroupEntry 15}
mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of associations from the group since
group creation, where the MTA was the initiator."
::= {mtaGroupEntry 16}
mtaGroupLastInboundActivity OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time since the last time that this group had an active
inbound association for purposes of message reception."
::= {mtaGroupEntry 17}
mtaGroupLastOutboundActivity OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time since the last time that this group had a
successful outbound association for purposes of
message delivery."
::= {mtaGroupEntry 18}
mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time since the last time that this group attempted
to make an outbound association for purposes of
message delivery."
::= {mtaGroupEntry 34}
mtaGroupRejectedInboundAssociations OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of inbound associations the group has
rejected, since group creation. Rejected associations
are not counted in the accumulated association totals."
::= {mtaGroupEntry 19}
mtaGroupFailedOutboundAssociations OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number associations where the group was the
initiator and association establishment has failed,
since group creation. Failed associations are
not counted in the accumulated association totals."
::= {mtaGroupEntry 20}
mtaGroupInboundRejectionReason OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The failure reason, if any, for the last association this
group refused to respond to. An empty string indicates that
the last attempt was successful. If no association attempt
has been made since the MTA was initialized the value
should be 'never'."
::= {mtaGroupEntry 21}
mtaGroupOutboundConnectFailureReason OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The failure reason, if any, for the last association attempt
this group initiated. An empty string indicates that the last
attempt was successful. If no association attempt has been
made since the MTA was initialized the value should be
'never'."
::= {mtaGroupEntry 22}
mtaGroupScheduledRetry OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when this group is scheduled to next attempt to
make an association."
::= {mtaGroupEntry 23}
mtaGroupMailProtocol OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An identification of the protocol being used by this group.
For an group employing OSI protocols, this will be the
Application Context. For Internet applications, the IANA
maintains a registry of the OIDs which correspond to well-known
message transfer protocols. If the application protocol is
not listed in the registry, an OID value of the form
{applTCPProtoID port} or {applUDProtoID port} are used for
TCP-based and UDP-based protocols, respectively. In either
case 'port' corresponds to the primary port number being
used by the group. applTCPProtoID and applUDPProtoID are
defined in [8]."
::= {mtaGroupEntry 24}
mtaGroupName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A descriptive name for the group. If this group connects to
a single remote MTA this should be the name of that MTA. If
this in turn is an Internet MTA this should be the domain
name. For an OSI MTA it should be the string encoded
distinguished name of the managed object using the format
defined in RFC 1779 [9]. For X.400(1984) MTAs which do not
have a Distinguished Name, the RFC 1327 [12] syntax
'mta in globalid' should be used."
::= {mtaGroupEntry 25}
mtaGroupSuccessfulConvertedMessages OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of messages that have been successfully
converted from one form to another in this group
since group creation."
::= {mtaGroupEntry 26}
mtaGroupFailedConvertedMessages OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION
mtaGroupFailedConvertedMessages OBJECT-TYPE構文Counter32 MAX-ACCESS読み取り専用ステータス現在の説明
"The number of messages for which an unsuccessful
attempt was made to convert them from one form to
another in this group since group creation."
::= {mtaGroupEntry 27}
mtaGroupDescription OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A description of the group's purpose. This information is
intended to identify the group in a status display."
::= {mtaGroupEntry 28}
mtaGroupURL OBJECT-TYPE
SYNTAX URLString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A URL pointing to a description of the group. This
information is intended to identify and briefly describe
the group in a status display."
::= {mtaGroupEntry 29}
mtaGroupCreationTime OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time since this group was first created."
::= {mtaGroupEntry 30}
mtaGroupHierarchy OBJECT-TYPE
SYNTAX INTEGER (-2147483648..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Describes how this group fits into the hierarchy. A
positive value is interpreted as an mtaGroupIndex
value for some other group whose variables include
those of this group (and usually others). A negative
value is interpreted as a group collection code: Groups
with common negative hierarchy values comprise one
particular breakdown of MTA activity as a whole. A
zero value means that this MIB implementation doesn't
implement hierarchy indicators and thus the overall
group hierarchy cannot be determined."
::= {mtaGroupEntry 31}
mtaGroupOldestMessageId OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Message ID of the oldest message in the group's queue.
Whenever possible this should be in the form of an
RFC 822 [13] msg-id; X.400 may convert X.400 message
identifiers to this form by following the rules laid
out in RFC1327 [12]."
::= {mtaGroupEntry 32}
mtaGroupLoopsDetected OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A message loop is defined as a situation where the MTA
decides that a given message will never be delivered to
one or more recipients and instead will continue to
loop endlessly through one or more MTAs. This variable
counts the number of times the MTA has detected such a
situation in conjunction with something associated with
this group since group creation. Note that the
mechanism MTAs use to detect loops (e.g. trace field
counting, count of references to this MTA in a trace
field, examination of DNS or other directory information,
etc.), the level at which loops are detected (e.g. per
message, per recipient, per directory entry, etc.), and
the handling of a loop once it is detected (e.g. looping
messages are held, looping messages are bounced or sent
to the postmaster, messages that the MTA knows will loop
won't be accepted, etc.) vary widely from one MTA to the
next and cannot be inferred from this variable."
::= {mtaGroupEntry 33}
-- The mtaGroupAssociationTable provides a means of correlating -- entries in the network services association table with the -- MTA group responsible for the association.
-mtaGroupAssociationTableは相関する手段を提供します-ネットワークサービスアソシエーションテーブルのエントリ-アソシエーションに責任があるMTAグループ。
mtaGroupAssociationTable OBJECT-TYPE SYNTAX SEQUENCE OF MtaGroupAssociationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table holding information regarding the associations for each MTA group."
mtaGroupAssociationTableアクセスできないMtaGroupAssociationEntry MAX-ACCESSのOBJECT-TYPE構文シーケンスステータス現在の説明「各MTAグループの関連付けに関する情報を保持するテーブル」
::= {mta 3}
mtaGroupAssociationEntry OBJECT-TYPE
SYNTAX MtaGroupAssociationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The entry holding information regarding the associations
for each MTA group."
INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex}
::= {mtaGroupAssociationTable 1}
MtaGroupAssociationEntry ::= SEQUENCE {
mtaGroupAssociationIndex
INTEGER
}
mtaGroupAssociationIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reference into association table to allow correlation of
this group's active associations with the association table."
::= {mtaGroupAssociationEntry 1}
-- The mtaGroupErrorTable gives each group a way of tallying -- the specific errors it has encountered. The mechanism -- defined here uses RFC 1893 [14] status codes to identify -- various specific errors. There are also classes for generic -- errors of various sorts, and the entire mechanism is also -- extensible, in that new error codes can be defined at any -- time.
-mtaGroupErrorTableは各グループに集計方法を提供します-発生した特定のエラーメカニズム-ここで定義されているのは、RFC 1893 [14]ステータスコードを使用して識別します-さまざまな特定のエラー。ジェネリックのクラスもあります-さまざまな種類のエラーであり、メカニズム全体も-拡張可能であり、新しいエラーコードをいつでも定義できます-いつでも。
mtaGroupErrorTable OBJECT-TYPE
SYNTAX SEQUENCE OF MtaGroupErrorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table holding information regarding accumulated errors
for each MTA group."
::= {mta 5}
mtaGroupErrorEntry OBJECT-TYPE SYNTAX MtaGroupErrorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
mtaGroupErrorEntry OBJECT-TYPE構文MtaGroupErrorEntry MAX-ACCESS not-accessibleステータス現在の説明
"The entry holding information regarding accumulated
errors for each MTA group."
INDEX {applIndex, mtaGroupIndex, mtaStatusCode}
::= {mtaGroupErrorTable 1}
MtaGroupErrorEntry ::= SEQUENCE {
mtaGroupInboundErrorCount
Counter32,
mtaGroupInternalErrorCount
Counter32,
mtaGroupOutboundErrorCount
Counter32
}
mtaGroupInboundErrorCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of the number of errors of a given type that have
been accumulated in assocation with a particular group
while processing incoming messages. In the case of SMTP
these will typically be errors reporting by an SMTP
server to the remote client; in the case of X.400
these will typically be errors encountered while
processing an incoming message."
::= {mtaGroupErrorEntry 1}
mtaGroupInternalErrorCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of the number of errors of a given type that have
been accumulated in assocation with a particular group
during internal MTA processing."
::= {mtaGroupErrorEntry 2}
mtaGroupOutboundErrorCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of the number of errors of a given type that have
been accumulated in assocation with a particular group's
outbound connection activities. In the case of an SMTP
client these will typically be errors reported while
attempting to contact or while communicating with the
remote SMTP server. In the case of X.400 these will
typically be errors encountered while constructing
or attempting to deliver an outgoing message."
::= {mtaGroupErrorEntry 3}
-- Conformance information
-適合情報
mtaConformance OBJECT IDENTIFIER ::= {mta 4}
mtaGroups OBJECT IDENTIFIER ::= {mtaConformance 1}
mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2}
-- Compliance statements
-コンプライアンスステートメント
mtaCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities which
implement the Mail Monitoring MIB for basic
monitoring of MTAs."
MODULE -- this module
MANDATORY-GROUPS {mtaGroup}
::= {mtaCompliances 1}
mtaAssocCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities which
implement the Mail Monitoring MIB for monitoring of
MTAs and their associations."
MODULE -- this module
MANDATORY-GROUPS {mtaGroup, mtaAssocGroup}
::= {mtaCompliances 2}
mtaErrorCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities which
implement the Mail Monitoring MIB for monitoring of
MTAs and detailed errors."
MODULE -- this module
MANDATORY-GROUPS {mtaGroup, mtaErrorGroup}
::= {mtaCompliances 3}
mtaFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION
mtaFullComplianceモジュール準拠ステータス現在の説明
"The compliance statement for SNMPv2 entities which
implement the full Mail Monitoring MIB for monitoring
of MTAs, associations, and detailed errors."
MODULE -- this module
MANDATORY-GROUPS {mtaGroup, mtaAssocGroup, mtaErrorGroup}
::= {mtaCompliances 4}
-- Units of conformance
-適合の単位
mtaGroup OBJECT-GROUP
OBJECTS {
mtaReceivedMessages, mtaStoredMessages,
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
mtaTransmittedVolume, mtaReceivedRecipients,
mtaStoredRecipients, mtaTransmittedRecipients,
mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages,
mtaGroupReceivedMessages, mtaGroupRejectedMessages,
mtaGroupStoredMessages, mtaGroupTransmittedMessages,
mtaGroupReceivedVolume, mtaGroupStoredVolume,
mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
mtaGroupOutboundAssociations, mtaLoopsDetected,
mtaGroupAccumulatedInboundAssociations,
mtaGroupAccumulatedOutboundAssociations,
mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
mtaGroupLastOutboundAssociationAttempt,
mtaGroupRejectedInboundAssociations,
mtaGroupFailedOutboundAssociations,
mtaGroupInboundRejectionReason,
mtaGroupOutboundConnectFailureReason,
mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName,
mtaGroupSuccessfulConvertedMessages,
mtaGroupFailedConvertedMessages, mtaGroupDescription,
mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy,
mtaGroupOldestMessageId, mtaGroupLoopsDetected}
STATUS current
DESCRIPTION
"A collection of objects providing basic monitoring of MTAs."
::= {mtaGroups 1}
mtaAssocGroup OBJECT-GROUP
OBJECTS {
mtaGroupAssociationIndex}
STATUS current
DESCRIPTION
"A collection of objects providing monitoring of MTA
associations."
::= {mtaGroups 2}
mtaErrorGroup OBJECT-GROUP
OBJECTS {
mtaGroupInboundErrorCount, mtaGroupInternalErrorCount,
mtaGroupOutboundErrorCount}
STATUS current
DESCRIPTION
"A collection of objects providing monitoring of
detailed MTA errors."
::= {mtaGroups 3}
END
終わり
The only changes made to this document since it was issued as RFC 1566 [11] are the following:
このドキュメントがRFC 1566 [11]として発行されて以降、このドキュメントに加えられた唯一の変更は次のとおりです。
(1) A number of DESCRIPTION fields have been reworded, hopefully making them clearer.
（1）いくつかのDESCRIPTIONフィールドが書き直され、うまくいけばより明確になります。
(2) mtaGroupDescription and mtaGroupURL fields have been added. These fields are intended to identify and describe the MTA and the various MTA groups.
（2）mtaGroupDescriptionおよびmtaGroupURLフィールドが追加されました。これらのフィールドは、MTAおよびさまざまなMTAグループを識別および説明することを目的としています。
(3) The time since the last outbound association attempt is now distinct from the time since the last successfuol outbound association attempt.
（3）最後のアウトバウンドアソシエーション試行からの時間は、最後の成功したアウトバウンドアソシエーション試行からの時間とは異なります。
(4) Conversion operation counters have been added.
（4）変換演算カウンタを追加しました。
(5) A mechanism to explicitly describe group hierarchies has been added.
（5）グループ階層を明示的に記述するメカニズムが追加されました。
(6) A mechanism to count specific sorts of errors has been added.
（6）特定の種類のエラーをカウントするメカニズムが追加されました。
(7) A field for the ID of the oldest message in a group's queue has been added.
（7）グループのキューで最も古いメッセージのIDのフィールドが追加されました。
(8) Per-MTA and per-group message loop counters have been added.
（8）MTAごとおよびグループごとのメッセージループカウンターが追加されました。
(9) A new table has been added to keep track of any errors an MTA encounters.
（9）MTAで発生したエラーを追跡するために、新しいテーブルが追加されました。
This document is a work product of the Mail and Directory Management (MADMAN) Working Group of the IETF. It is based on an earlier MIB designed by S. Kille, T. Lenggenhager, D. Partain, and W. Yeong. The Electronic Mail Association's TSC committee was instrumental in providing feedback on and suggesting enhancements to RFC 1566 [11] that have led to the present document.
このドキュメントは、IETFのMail and Directory Management（MADMAN）ワーキンググループの成果物です。これは、S。Kille、T。Lenggenhager、D。Partain、およびW. Yeongによって設計された初期のMIBに基づいています。電子メール協会のTSC委員会は、現在の文書につながったRFC 1566 [11]に関するフィードバックを提供し、その機能強化を提案するのに役立ちました。
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996.
[1] SNMPv2ワーキンググループ、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「Structure of Management Information for Version 2 for the Simple Network Management Protocol（SNMPv2）」、RFC 1902、1996年1月。
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[2] SNMPv2 Working Group、Case、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「Textual Conventions for Version 2 for the Simple Network Management Protocol（SNMPv2）」、RFC 1903、1996年1月。
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[3] SNMPv2 Working Group、Case、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「Version 2 for the Simple Network Management Protocol（SNMPv2）」、RFC 1904、1996年1月。
[4] SNMPv2 Working Grou, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[4] SNMPv2 Working Grou、Case、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「Protocol Operations for Version 2 for the Simple Network Management Protocol（SNMPv2）」、RFC 1905、1996年1月。
[5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[5] SNMPv2 Working Group、Case、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「Transport Mappings for Version 2 for the Simple Network Management Protocol（SNMPv2）」、RFC 1906、1996年1月。
[6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1907, January 1996.
[6] SNMPv2 Working Group、Case、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「Version 2 for the Simple Network Management Protocol（SNMPv2）」の管理情報ベース、RFC 1907、1996年1月。
[7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework", RFC 1908, January 1996.
[7] SNMPv2ワーキンググループ、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「インターネット標準ネットワーク管理フレームワークのバージョン1とバージョン2の共存」、RFC 1908、1996年1月。
[8] Freed, N., and S. Kille, "The Network Services Monitoring MIB", RFC 2248, January 1998.
[8] Freed、N。、およびS. Kille、「The Network Services Monitoring MIB」、RFC 2248、1998年1月。
[9] Kille, S., "A String Representation of Distinguished Names", RFC 1779, March 1995.
[9] Kille、S。、「識別名の文字列表現」、RFC 1779、1995年3月。
[10] Berners-Lee, T., Masinter, L. and M. McCahill, Uniform Resource Locators (URL)", RFC 1738, December 1994.
[10] Berners-Lee、T.、Masinter、L。およびM. McCahill、Uniform Resource Locators（URL）」、RFC 1738、1994年12月。
[11] Freed, N. and S. Kille, "Mail Monitoring MIB", RFC 1566, January 1994.
[11] Freed、N。およびS. Kille、「Mail Monitoring MIB」、RFC 1566、1994年1月。
[12] Kille, S., "Mapping between X.400(1988) / ISO 10021 and RFC 822", RFC 1327, May 1992.
[12] Kille、S。、「X.400（1988）/ ISO 10021とRFC 822の間のマッピング」、RFC 1327、1992年5月。
[13] Crocker, D., "Standard for the Format of ARPA Internet Text Message", RFC 822, August 1982.
[13] Crocker、D。、「ARPAインターネットテキストメッセージのフォーマットの標準」、RFC 822、1982年8月。
[14] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893, January 1996.
[14] Vaudreuil、G。、「Enhanced Mail System Status Codes」、RFC 1893、1996年1月。
This MIB does not offer write access, and as such cannot be used to actively attack a system. However, this MIB does provide passive information about the existance, type, and configuration of applications on a given host that could potentially indicate some sort of vulnerability. Finally, the information MIB provides about network usage could be used to analyze network traffic patterns.
このMIBは書き込みアクセスを提供しないため、システムを積極的に攻撃するために使用することはできません。ただし、このMIBは、ある種の脆弱性を潜在的に示す可能性がある、特定のホスト上のアプリケーションの存在、タイプ、および構成に関する受動的な情報を提供します。最後に、MIBがネットワークの使用状況について提供する情報を使用して、ネットワークトラフィックパターンを分析できます。
Ned Freed Innosoft International, Inc. 1050 Lakes Drive West Covina, CA 91790 USA
Ned Freed Innosoft International、Inc. 1050 Lakes Drive West Covina、CA 91790 USA
Phone: +1 626 919 3600
Fax: +1 626 919 3614
EMail: ned.freed@innosoft.com
Steve Kille, MADMAN WG Chair ISODE Consortium The Dome, The Square Richmond TW9 1DT UK
Steve Kille、MADMAN WG議長ISODEコンソーシアムThe Dome、The Square Richmond TW9 1DT UK
Phone: +44 181 332 9091
EMail: S.Kille@isode.com
Copyright (C) The Internet Society (1998). All Rights Reserved.
Copyright（C）The Internet Society（1998）。全著作権所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
このドキュメントとその翻訳はコピーして他のユーザーに提供することができ、コメントまたはその他の方法で説明したり、その実装を支援する二次的著作物は、いかなる種類の制限なしに、全体または一部を準備、コピー、公開、および配布することができますただし、上記の著作権表示とこの段落は、そのようなすべてのコピーと派生物に含まれています。ただし、このドキュメント自体は、著作権に関する通知を削除したり、インターネットソサエティや他のインターネット組織への参照を削除したりするなど、いかなる方法でも変更できません。ただし、インターネット標準を開発する目的で必要な場合は除きます。インターネット標準のプロセスに従うか、または必要に応じて、それを英語以外の言語に翻訳する必要があります。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上記で付与された制限付きのアクセス許可は永続的であり、インターネットソサエティまたはその後継者または譲受人によって取り消されることはありません。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. RPO
このドキュメントとここに含まれる情報は「現状有姿」で提供され、インターネット社会およびインターネット技術タスクフォースは、明示または黙示を問わず、ここに記載されている情報の使用が保証するものに限定されない一切の保証を含みません。商品性または特定の目的への適合性に関する権利または黙示の保証を侵害すること。 RPO