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."
View at oid-info.com
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.
Parsed from file rfc2789-Mail-Monitoring.mib.txt
Company: None
Module: MTA-MIB
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.
Parsed from file MTA-MIB.mib
Module: MTA-MIB
Automatically extracted from RFC2789
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}
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}
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.28.1.1.1 | mtaReceivedMessages | 0 | 0 | The number of messages received since MTA initialization. This includes messages transmitted to this MTA from other MTAs as well … |
| 1.3.6.1.2.1.28.1.1.2 | mtaStoredMessages | 0 | 0 | The total number of messages currently stored in the MTA. This includes messages that are awaiting transmission to some other MTA… |
| 1.3.6.1.2.1.28.1.1.3 | mtaTransmittedMessages | 0 | 0 | The number of messages transmitted since MTA initialization. This includes messages that were transmitted to some other MTA or ar… |
| 1.3.6.1.2.1.28.1.1.4 | mtaReceivedVolume | 0 | 0 | The total volume of messages received since MTA initialization, measured in kilo-octets. This volume should include all transfer… |
| 1.3.6.1.2.1.28.1.1.6 | mtaTransmittedVolume | 0 | 0 | The total volume of messages transmitted since MTA initialization, measured in kilo-octets. This volume should include all trans… |
| 1.3.6.1.2.1.28.1.1.7 | mtaReceivedRecipients | 0 | 0 | The total number of recipients specified in all messages received since MTA initialization. Recipients this MTA has no responsib… |
| 1.3.6.1.2.1.28.1.1.8 | mtaStoredRecipients | 0 | 0 | The total number of recipients specified in all messages currently stored in the MTA. Recipients this MTA has no responsibility … |
| 1.3.6.1.2.1.28.1.1.9 | mtaTransmittedRecipients | 0 | 0 | The total number of recipients specified in all messages transmitted since MTA initialization. Recipients this MTA had no respon… |
| 1.3.6.1.2.1.28.1.1.10 | mtaSuccessfulConvertedMessages | 0 | 0 | The number of messages that have been successfully converted from one form to another since MTA initialization. |
| 1.3.6.1.2.1.28.1.1.11 | mtaFailedConvertedMessages | 0 | 0 | The number of messages for which an unsuccessful attempt was made to convert them from one form to another since MTA initializati… |
| 1.3.6.1.2.1.28.1.1.12 | mtaLoopsDetected | 0 | 0 | A message loop is defined as a situation where the MTA decides that a given message will never be delivered to one or more recipi… |