Email glossary · Practical guide
Envelope sender: the SMTP identity outside the visible message
The envelope sender is supplied during SMTP transport. It can differ from the From header inside the message and is relevant to delivery-failure routing and SPF evaluation.
Reviewed · Examples are illustrative
Who this helps: Readers checking a term before making an outreach or mailbox decision.
Meaning and common confusion
An operator should distinguish transport identity from presentation. A provider may choose or rewrite the envelope according to its service configuration. The visible campaign sender alone therefore cannot establish the exact envelope domain used on the receiving side.
Source: RFC 5321: SMTP envelope context
Worked example
This is a synthetic illustration, not a customer result or a live configuration to copy.
Transport: MAIL FROM uses [email protected]
Message header: From uses [email protected]
Question: which identity passed SPF?
The answer requires message or transport evidence, not the display name.Checks to make
- Inspect a controlled delivered message and provider records.
- Avoid confusing an SMTP username with the envelope address.
- Verify the provider's custom bounce-domain options before planning alignment changes.
Next step and limits
Use the Return-Path and alignment guides to trace the identity through delivery. Keep empty-envelope system messages and ordinary campaign messages separate during analysis; do not apply one sample's assumptions to every mail flow.
Source: RFC 5321: SMTP envelope context
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.
Related guides
- Return-Path: the recorded route for delivery failures →
- Custom Return-Path alignment: verify the envelope your provider uses →