Interpret mailbox email history¶
An email activity entry is supporting evidence about an outgoing mailbox action. It is useful for understanding who initiated recorded work, but it is not a delivery receipt, proof of reading or a complete copy of the message.
Draft scope: This page explains the inspected mailbox service's recording and recovery boundaries. It does not establish connected mailbox screens, provider readiness or complete mailbox setup and sending instructions. The personal mailbox connection guide now explains the inspected connection and recovery journey. The reading guide and personal sending guide now describe their inspected Final Screens and source boundaries. The work-linked explanation now distinguishes source verification and corrections from ordinary sending activity. Full connector/runtime coverage and connected delivery remain unfinished. Official-letter delivery uses a separate delivery path and evidence; these mailbox rules must not be applied to that process automatically.
What a sent entry means¶
The mailbox service attempts to record sent activity after its provider reports that the send was accepted or verified. The activity entry labels the recorded action Completed. Interpret that label with the underlying send result:
| Send result | What the inspected implementation establishes |
|---|---|
| Accepted | The outgoing-mail provider accepted the send. This does not establish arrival in every recipient's mailbox or reading. |
| Verified | After an uncertain send, a search in the sender's Sent folder found a matching item. This is evidence from the sender's mailbox, not an acknowledgment from the recipient. |
| Unknown | The service could not establish the send outcome. This path does not produce the same sent activity. Absence of that entry does not establish that no email left the provider. |
| Failed or awaiting retry | The inspected attempt does not produce sent activity through this path. Support must check the actual attempt and any scheduled recovery before another send is requested. |
A connection interruption or cancellation during sending can leave an uncertain result. Do not interpret that interruption as proof the message was never sent. A problem updating the Sent folder can also occur separately from a successful provider send.
Who and what appears in history¶
The recording process resolves the sender's saved user information, or requests it from its source when no local user is found. A locally available name and email are not necessarily a fresh directory lookup. The actor in history is the supplied sender profile; it is not a new confirmation that the person is currently authorized to use the mailbox.
The related context uses the primary recipient's display name, or “Outgoing email” when no usable name is supplied. This entry does not contain the full message body, subject, copied-recipient list or provider delivery proof. Its related-item identity is also separate from the send request identity used by support.
Only an identified internal primary recipient is added to the affected-person list. Copied recipients and direct external addresses are not expanded into that list. An empty or short list must not be used to count all recipients or infer who received or read the email.
Why an accepted send can have no activity entry¶
After updating the send result, the service tries to record activity and then supporting reporting evidence. It treats failures during those supporting steps as warnings. If sender information is missing or cannot be resolved, both are skipped. If activity recording fails, the later reporting-evidence call is not reached. If reporting evidence fails, activity may already have been attempted.
These stages can therefore disagree. A missing entry or report does not mean the provider rejected the email. A diagnostic showing a publication attempt does not prove that the entry reached history. Use the actual send result and original request when investigating.
For an already accepted, verified or uncertain result, processing the same send request again does not repair missing supporting history through this path. Do not create a new email merely to make history or reporting appear. Support needs to distinguish sending, saving the result and recording the supporting evidence.
Investigate without causing another send¶
| Observation | What to establish |
|---|---|
| The send was accepted but activity is absent | Check whether sender resolution or supporting publication failed, and whether the source result was saved. |
| A sent entry exists but the recipient reports nothing | Use the provider and recipient delivery evidence available to authorized support. Activity alone does not resolve receipt, filtering or reading. |
| The outcome is uncertain | Retain the original send reference and ask support to reconcile it. A fresh request may send another copy. |
| Reporting is missing while activity exists | The two supporting publications are separate steps; investigate reporting without repeating the send. |
| Connection history is missing | Verify the mailbox's actual connection state. Normal connection-history publication is not established by the inspected source, even though a connection action definition exists. |
Provide the organization, original send reference, approximate time, intended recipient and observed result through an approved support channel. Share message content only when needed and authorized. Activity counts are not delivery rates, readership measures or verified work outcomes. General history access and retention/data-request rules still apply; this page adds no retention guarantee or permission to inspect another person's mailbox.