Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallAn email passes through several stages after you press Send: it is assembled as a message, submitted to a mail server, transferred between systems, deposited in a recipient’s mailbox, and eventually retained or removed according to mailbox and server policy. SMTP handles submission and transport; IMAP provides access to stored mail. Acceptance into a mailbox is not proof that a person displayed or read the message.
What is an email before it is sent?
An Internet email has two related parts: its message contents and its transport envelope. RFC 5322 defines the message format: header fields, such as the sender, recipient, subject and date, followed by an optional body. The envelope is used to route the message between mail systems; it is not the same thing as the message’s visible headers.
MIME extensions allow the body to contain structured content, including multipart messages and attachments. The Date header records when the message creator considered it complete and ready to enter the delivery system. It does not necessarily show when a server later submitted, relayed or delivered it.
How does the message leave the sender?
A mail user agent (MUA)—for example, a desktop or mobile email app—submits the message to a message submission service. Authentication and submission policy apply at this boundary. RFC 8314 recommends TLS 1.2 or later for connections between an MUA and a submission server, using implicit TLS or correctly enforced STARTTLS.
#1 Best Overall
Submission is the handoff into the mail system, not the same event as inbox placement. From there, SMTP systems transfer the message onward. Depending on the route, one system may introduce mail, relay it to another server, or act as a gateway between different transport environments.
How does SMTP carry and relay an email?
Transfer between servers
SMTP clients establish a bidirectional connection with SMTP servers and transfer mail. A message may pass through multiple servers before reaching its destination. A relay normally forwards the message without changing its message data, while adding trace information about the path. A gateway may transform content when moving mail between different transport environments.
Rank #2
Trace fields
Each receiving SMTP server must add a Received trace field at the beginning of the message content. These fields can show aspects of the path a message took, but they are not, by themselves, proof that the final recipient read it or that every copy of the message has been preserved.
What does “delivered” mean?
Under RFC 5321, a delivery SMTP system receives mail from a transport environment and passes it to a mail user agent or deposits it in a message store that an MUA is expected to access. In practical terms, delivery means the mail entered the destination delivery path or store. It does not mean that the recipient’s app displayed it, that the recipient noticed it, or that a human read it.
Spam handling, filtering and other provider-specific processing can affect where accepted mail appears. A successful transport handoff alone does not establish that a message landed in the inbox a person normally checks.
How does a mailbox represent and expose stored mail?
IMAP lets a client access messages in a message store and work with mailbox-scoped attributes. For persistent identification, IMAP uses a message’s UID together with the mailbox’s UIDVALIDITY value. Message sequence numbers are positional and can change after messages are expunged, so they are not substitutes for that identity pair.
An IMAP message’s internal date is also distinct from its RFC 5322 Date header. The internal date reflects receipt or final delivery; for a message copied or moved with IMAP, it can instead reflect the source message’s date. The header date records the creator’s stated completion time, not necessarily the message’s later arrival.
What can delivery and read notifications tell you?
Delivery Status Notifications (DSNs) and Message Disposition Notifications (MDNs) report different events. A DSN concerns transport or recipient status; an MDN reports a user-agent disposition. Neither notification alone proves that a human read the message.
Recommended Free Tools
| Notification | What it reports | What it does not establish |
|---|---|---|
| DSN | A transport or recipient status for a message. One DSN describes one message and may include several recipients; delayed or split delivery can result in multiple DSNs after one submission. | That the recipient displayed or read the message. |
| MDN | A later action or disposition reported by a user agent, such as display, printing or deletion. | That a person actually saw or read the message. It reports a user-agent disposition, not conclusive evidence of a human action. |
What happens when an email is retained, expired or deleted?
There is no universal retention period. A message may remain in a mailbox under provider policy, be marked for deletion by a client, expire under server policy, or be expunged. RFC 5423 names server-policy expiration as MessageExpire and removal through expunge as MessageExpunge. After expunge, the message is no longer accessible through that mailbox.
That mailbox-level result does not guarantee destruction of every other copy. Backups, logs, legal holds, indexes and geographically replicated data depend on the service’s deployment and policies; an IMAP expunge is not proof that all such copies have been erased. POP3 behavior also depends on server policy: a server may advertise minimum retention or delete downloaded messages.
What records can explain an email’s history?
Different records preserve different parts of the lifecycle. Received fields record transfer trace information; submission accountability records concern the handoff; DSNs describe transport outcomes; MDNs report user-agent dispositions; IMAP UIDs identify messages within a mailbox context; and server event logs may record storage events. None is interchangeable with proof of message contents, final inbox placement, display or human reading.
TLS protects submission and mailbox-access connections in transit when properly used, but relay protection has separate requirements. A claim about how long a provider keeps messages, whether it retains deleted copies, or where data is stored must be checked against that provider’s own policy and the applicable organizational or geographic rules.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
