Parse enhanced mail status codes into class, subject, and detail

Keep this document to one review outcome: Parse enhanced mail status codes into class, subject, and detail. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 3463 — Enhanced Mail System Status Codes from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• An enhanced mail status code contains three dot-separated fields: delivery class, problem subject, and specific detail. The research record locates this support at Section 2 (Status Code Structure).
• Class 2 means success, class 4 means a persistent transient failure that may succeed later, and class 5 means a permanent failure requiring a change. The research record locates this support at Section 2 (Status Code Structure), class sub-codes.
• A client that does not recognize a detail code still reports the recognized subject, and if the subject is also unknown it reports the general class. The research record locates this support at Section 2 (Status Code Structure), extensibility behavior.

The source support ends with the statements listed above. Use them to examine sending domains, receiving domains, message agents, headers, authentication results, policy records, and failure handling in the applicable environment, not to imply a wider guarantee.

What the source does not establish

This RFC evidence supports only the named mail-protocol decision; it does not prove provider support, deliverability, or compliance for a particular flow. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine authoritative DNS, certificates, time, gateways, identity stores, reputation services, and third-party mail providers before translating the source into an operational decision.

Applicability questions

• For source statement 1 at Section 2 (Status Code Structure), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 2 (Status Code Structure), class sub-codes, which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 2 (Status Code Structure), extensibility behavior, which observable configuration, record, or test can confirm applicability here?
• Within sending domains, receiving domains, message agents, headers, authentication results, policy records, and failure handling, which versions, roles, and configuration states define the review population?
• Could authoritative DNS, certificates, time, gateways, identity stores, reputation services, and third-party mail providers invalidate the test, hide a failure, or change applicability?
• Who owns the decision, and which observation requires stopping, escalation, or rollback?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of sending domains, receiving domains, message agents, headers, authentication results, policy records, and failure handling, observed and expected states, owner, and reason for deviation.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for authoritative DNS, certificates, time, gateways, identity stores, reputation services, and third-party mail providers and sanitize protected material before retention.

Verification and evidence

A reviewer should be able to retrace the decision from Section 2 (Status Code Structure); Section 2 (Status Code Structure), class sub-codes; Section 2 (Status Code Structure), extensibility behavior through sanitized messages, DNS records, SMTP transcripts, authentication results, policy evaluation, and delivery or rejection logs. Record what was collected, where, when, by whom, and which system or role it represents.

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

Official references

• RFC 3463 — Enhanced Mail System Status Codes — RFC Editor / Internet Engineering Task Force