MTA-MIB :: mtaReceivedMessages

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › MTA-MIB › mtaReceivedMessages

mtaReceivedMessages

Module: MTA-MIB

OID (symbolic): MTA-MIB::mtaReceivedMessages

OID (numeric): 1.3.6.1.2.1.28.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

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.

What is mtaReceivedMessages?

A running count of every message this Message Transfer Agent has received since it last initialized, whether relayed in from another MTA or submitted directly by a local user or app — an admin's basic inbound mail-volume counter.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.28.1.1.1
snmpwalk -v2c -c public <target> MTA-MIB::mtaReceivedMessages

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.28.1.1.1.1
snmpget -v2c -c public <target> MTA-MIB::mtaReceivedMessages.1

Start monitoring Vendor-neutral IETF standard (Message Transfer Agent mail-relay server) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the MTA-MIB::mtaReceivedMessages OID value, configure state conditions and alerts, and monitor any Vendor-neutral IETF standard (Message Transfer Agent mail-relay server) from a single console.

How to Use in IPNetwork Monitor

Select a device implementing MTA-MIB as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type mtaReceivedMessages into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of messages received since MTA initialization. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.28mtaMTA-MIB
1.3.6.1.2.1.28.1mtaTableMTA-MIB
1.3.6.1.2.1.28.1.1mtaEntryMTA-MIB
1.3.6.1.2.1.28.1.1.1mtaReceivedMessagesMTA-MIB