EXTENDED-MADMAN-MIB

All MIBs › EXTENDED-MADMAN-MIB

Category: Standard: IETF

Description: Extends the IETF MADMAN (Mail and Directory Management) MIB with additional objects for message transfer agent monitoring.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is EXTENDED-MADMAN-MIB?

EXTENDED-MADMAN-MIB extends the IETF MADMAN (Mail and Directory Management) MIB framework, adding supplementary objects for monitoring mail transfer agent (MTA) and directory-enabled application infrastructure, independent of any specific hardware vendor. It exposes application-level identification data (descriptions, contacts, desired operational status) via extendedApplTable, and mail-transfer-specific fault/performance counters via extendedMtaTable, covering message-processing health. It is explicitly used to monitor software/service status: administrators can track mtaFailedMessages, mtaFailedVolume, and mtaFailedRecipients as fault indicators, mtaLastMessageFailureReason for diagnosing delivery problems, and mtaLargestMessageStored for capacity/queue-related monitoring, rather than physical hardware sensors. As its name indicates, it directly depends on and extends the IETF's MADMAN MIB (APPLICATION-MIB/MTA-MIB, RFC 2249), inheriting its base application/MTA modeling. It is typically deployed on enterprise mail servers and directory-enabled messaging infrastructure, where this EXTENDED-MADMAN-MIB guide helps administrators track MTA queue health and message-delivery failures.

IPNetwork Monitor allows you to monitor SNMP objects defined in EXTENDED-MADMAN-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
mail transfer agent (MTA) / messaging server software

Monitoring Examples

An administrator would poll extendedApplTable/extendedApplEntry to check applDescr, applContact, and applDesiredOperStatus for a mail application instance, confirming the MTA service is intended to be running and identifying its owner. Polling extendedMtaTable/extendedMtaEntry surfaces mtaFailedMessages and mtaFailedVolume, a rising count of which signals a delivery problem such as a downstream mail relay being unreachable. mtaLastMessageFailureReason would then be checked to diagnose the specific cause, while mtaLargestMessageStored helps flag oversized messages clogging the queue.

What Can Be Monitored

failed message count
failed message volume
failed recipients
last message failure reason
largest message stored
application operational status

Imported Objects

From MTA-MIB

mtaGroupInboundRejectionReason	OBJECT-TYPE
mtaGroupIndex	OBJECT-TYPE
mtaGroupName	OBJECT-TYPE
mtaGroupOutboundConnectFailureReason	OBJECT-TYPE

From NETWORK-SERVICES-MIB

applIndex	OBJECT-TYPE
applLastChange	OBJECT-TYPE
applName	OBJECT-TYPE
applOperStatus	OBJECT-TYPE

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
Gauge
TimeTicks
enterprises

From RFC1213-MIB

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
lotus	1.3.6.1.4.1.334
notes	1.3.6.1.4.1.334.1
lcs	1.3.6.1.4.1.334.2
softswitch	1.3.6.1.4.1.334.3
common_mibs	1.3.6.1.4.1.334.3.1
extendedMADMAN	1.3.6.1.4.1.334.3.1.1
extendedApplTable	1.3.6.1.4.1.334.3.1.1.1		not-accessible	The table holding information specific to an Application for which extended information is available.
extendedApplEntry	1.3.6.1.4.1.334.3.1.1.1.1		not-accessible	The entry associated with each application for which extended information is available.
STR applDescr	1.3.6.1.4.1.334.3.1.1.1.1.1	DisplayString	read-only	A textual description for the application. This should identify the type of application as well as any other pertinent details regarding its implementation.
STR applContact	1.3.6.1.4.1.334.3.1.1.1.1.2	DisplayString	read-only	The textual identification of the contact person for this application, together with information on how to contact that person..
INT applDesiredOperStatus	1.3.6.1.4.1.334.3.1.1.1.1.3	INTEGER	read-write	Indicates the intended operational state of the application up - application is operational and available down - application is not operational halted - application is operational, but not available.
extendedMtaTable	1.3.6.1.4.1.334.3.1.1.2		not-accessible	The table holding information specific to an MTA for which extended information is available.
extendedMtaEntry	1.3.6.1.4.1.334.3.1.1.2.1		not-accessible	The entry associated with each MTA for which extended information is available.
CTR mtaFailedMessages	1.3.6.1.4.1.334.3.1.1.2.1.1	Counter	read-only	(EMA compliant) The total number of messages that have 'failed' MTA processing since the MTA was initialized. Possible 'failures' include encode/decode errors, translate errors, unable to route, etc. Protocol/association errors are specifically excluded as they are accounted for in other MADMAN MIB variables.
CTR mtaFailedVolume	1.3.6.1.4.1.334.3.1.1.2.1.2	Counter	read-only	(EMA compliant) The total volume of messages that have 'failed' MTA processing, measured in kilo-octets. This volume should include all data that is logically above the mail transport level.
CTR mtaFailedRecipients	1.3.6.1.4.1.334.3.1.1.2.1.3	Counter	read-only	The total number of recipients included in messages that have 'failed' MTA processing since the MTA was initialized.
STR mtaLastMessageFailureReason	1.3.6.1.4.1.334.3.1.1.2.1.4	DisplayString	read-only	The failure reason, if any, for the last message to fail in the MTA. An empty string indicates that the last attempt was successful. If no message has failed since the MTA has been initialized, the value should be 'never'.
GAU mtaLargestMessageStored	1.3.6.1.4.1.334.3.1.1.2.1.5	Gauge	read-only	(EMA compliant) The size, in kilo-octets of the largest message currently stored in the MTA.
TIK mtaOldestMessageStored	1.3.6.1.4.1.334.3.1.1.2.1.6	TimeTicks	read-only	The time since the oldest message currently stored in the MTA was first safe-stored.
INT mtaInputInhibited	1.3.6.1.4.1.334.3.1.1.2.1.7	INTEGER	read-write	Indiciates whether or not this MTA is in the 'input inhibited' state, meaning that the MTA will process stored messages, but will not accept new inbound associations.
INT mtaType	1.3.6.1.4.1.334.3.1.1.2.1.8	INTEGER	read-only	Indiciates the type or primary/native protocol used by this MTA.
extendedMtaGroupTable	1.3.6.1.4.1.334.3.1.1.3		not-accessible	The table holding information specific to each MTA group for which extended information is available.
extendedMtaGroupEntry	1.3.6.1.4.1.334.3.1.1.3.1		not-accessible	The entry associated with each MTA group for which extended information is available.
STR mtaGroupIdOfOldestMessage	1.3.6.1.4.1.334.3.1.1.3.1.1	DisplayString	read-only	(EMA compliant) A string representation for the ID of the oldest message stored by this mtaGroup.
TIK mtaGroupLastOutboundAssociationAttempt	1.3.6.1.4.1.334.3.1.1.3.1.2	TimeTicks	read-only	(EMA compliant) The value of sysUpTime when this group last attempted an outbound association.
GAU mtaGroupMaxInboundAssociations	1.3.6.1.4.1.334.3.1.1.3.1.3	Gauge	read-only	The configured or resource-determined maximum number of possible inbound associations available to this group.
GAU mtaGroupMaxOutboundAssociations	1.3.6.1.4.1.334.3.1.1.3.1.4	Gauge	read-only	The configured or resource-determined maximum number of possible outbound associations available to this group.
INT mtaGroupCurrentState	1.3.6.1.4.1.334.3.1.1.3.1.5	INTEGER	read-only	Indicates the internal operational state of the MTA Group. stopped - group is not currently active initializing - group is in the process of starting configurable - group may be configured,but is not processing mail input_disabled - group is running, but not accepting input output_disabled - group is running, but not initiating outbound associations running - group is active and processing mail stopping - group is in the process of shutting down unknown - state does not apply or cannot be determined
TIK mtaGroupLastChange	1.3.6.1.4.1.334.3.1.1.3.1.6	TimeTicks	read-only	The value of sysUpTime at the time this group entered its current operational state.
INT mtaGroupLargestMessageStored	1.3.6.1.4.1.334.3.1.1.3.1.7	INTEGER	read-only	The size, in kilo-octets of the largest message currently stored in this group's queue.
CTR mtaGroupInboundRejectSecurityViolations	1.3.6.1.4.1.334.3.1.1.3.1.8	Counter	read-only	(Potential addition to MADMAN) The total number of inbound associations to this group that were rejected due to a security violation (incorrect MTA password, etc).
CTR mtaGroupOutboundFailSecurityViolations	1.3.6.1.4.1.334.3.1.1.3.1.9	Counter	read-only	(Potential addition to MADMAN) The total number of outbound associations from this group that failed due to a security violation (incorrect MTA password, etc).
CTR mtaGroupInboundRejectResourceFailures	1.3.6.1.4.1.334.3.1.1.3.1.10	Counter	read-only	(Potential addition to MADMAN) The total number of inbound associations to this group that were rejected due to a lack of resources.
CTR mtaGroupOutboundFailResourceFailures	1.3.6.1.4.1.334.3.1.1.3.1.11	Counter	read-only	(Potential addition to MADMAN) The total number of outbound associations from this group that failed due to a lack of resources.
CTR mtaGroupFailedVolume	1.3.6.1.4.1.334.3.1.1.3.1.12	Counter	read-only	The total volume of messages that have 'failed' group processing, measured in kilo-octets. This volume should include all data that is logically above the mail transport level.
CTR mtaGroupFailedRecipients	1.3.6.1.4.1.334.3.1.1.3.1.13	Counter	read-only	The total number of recipients included in messages that have 'failed' group processing since this group was initialized.
lms	1.3.6.1.4.1.334.3.2

RFC description

Lotus extensions to MADMAN MTA (Mail Transfer Agent) monitoring for messaging systems.

Start monitoring Mail transfer agent / messaging server software, any vendor (vendor-neutral IETF MADMAN extension) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download EXTENDED-MADMAN-MIB

What Is EXTENDED-MADMAN-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description