MTA-MIB :: mtaLoopsDetected

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › MTA-MIB › mtaLoopsDetected

mtaLoopsDetected

Module: MTA-MIB

OID (symbolic): MTA-MIB::mtaLoopsDetected

OID (numeric): 1.3.6.1.2.1.28.1.1.12

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

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.

What is mtaLoopsDetected?

A count of times this MTA has detected a message stuck in an endless delivery loop between MTAs since initialization; any nonzero and climbing value is a signal for an admin to investigate a routing misconfiguration.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.28.1.1.12
snmpwalk -v2c -c public <target> MTA-MIB::mtaLoopsDetected

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.28.1.1.12.1
snmpget -v2c -c public <target> MTA-MIB::mtaLoopsDetected.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::mtaLoopsDetected OID value, configure state conditions and alerts, and monitor any Vendor-neutral IETF standard (Message Transfer Agent mail-relay server) from a single console.

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.12mtaLoopsDetectedMTA-MIB