Separate SMTP envelope state from message content while relaying mail

Keep this document to one review outcome: Separate SMTP envelope state from message content while relaying mail. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 5321 — Simple Mail Transfer Protocol from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• An SMTP mail object has an envelope containing the reverse path, recipient paths, and extension parameters, plus separately transmitted message content. The research record locates this support at Section 2.3.1 (Mail Objects).
• MAIL starts a transaction and sets the reverse path, RCPT adds each forward path, and DATA transfers the header section and body after recipients are accepted. The research record locates this support at Section 3.3 (Mail Transactions).
• SMTP keeps reverse path, forward paths, and mail data in distinct transaction buffers until the end-of-data indication commits the transaction. The research record locates this support at Section 4.1.1 (Command Semantics and Syntax).

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving sending domains, receiving domains, message agents, headers, authentication results, policy records, and failure handling and the conditions the source actually describes.

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.3.1 (Mail Objects), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 3.3 (Mail Transactions), which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 4.1.1 (Command Semantics and Syntax), 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. Use a two-person review for the source interpretation and the resulting operational decision. 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

Tie each conclusion back to Section 2.3.1 (Mail Objects); Section 3.3 (Mail Transactions); Section 4.1.1 (Command Semantics and Syntax) and to observable material such as sanitized messages, DNS records, SMTP transcripts, authentication results, policy evaluation, and delivery or rejection logs. Preserve provenance and stable identifiers without copying secrets into the evidence set.

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

Official references

• RFC 5321 — Simple Mail Transfer Protocol — RFC Editor / Internet Engineering Task Force