Message history and exports
Open your project, then Message history. The list shows each message with its
submission state, recipient outcome, transport (API or SMTP) and up to three of its tags. Filter by
message ID, state, outcome, transport, time, an exact tag (key:value) or the current reason.
Select a message to see its timeline, or Diagnostics for its attempts and a support summary.
Three facts are kept apart, and none of them proves the message reached the inbox:
- Accepted: weneed.email stored your message (
202or250). - Submitted: weneed.email handed it to the recipient’s mail server.
- Recipient outcome: what that server reported, at the time or later.
Submission states
Section titled “Submission states”| State | Meaning | Do |
|---|---|---|
queued |
Accepted, waiting to be sent. | Nothing. |
dispatching |
Being delivered now. | Nothing. |
retry_wait |
The recipient’s server asked to try later. weneed.email will retry. | Nothing. |
submitted |
The recipient’s server took the message. | Nothing. |
submission_unknown |
The connection failed at a point where weneed.email can’t tell whether the server took the message. It’s never resent automatically. | Don’t resend with a new key. Wait for a bounce or contact support with the message ID. |
held |
Sending is stopped for this message, for example because sending is paused or its credential was revoked. | Contact support. You can’t release a hold yourself. |
suppressed |
The recipient is on your suppression list. Recorded, not sent. | Fix the address in your app. See Bounces. |
expired |
Its expires_at passed before it could be sent. |
Send a new message if it’s still needed. |
cancelled |
You cancelled it before it was sent. | Nothing. |
rejected |
It couldn’t be sent and won’t be retried. | Check the reason code in the timeline. |
Recipient outcomes
Section titled “Recipient outcomes”| Outcome | Meaning |
|---|---|
| …pending | No answer from the recipient’s server yet. |
| ✓delivered_to_server | The recipient’s server accepted the message. It may still filter it, for example into spam. |
| ?delivery_unknown | It’s unclear whether the server accepted it. |
| ✕bounced | The server rejected it, at once or later in a bounce report. |
| ○suppressed | Not sent because the address is suppressed. |
The timeline also shows whether a bounce or a complaint was recorded.
Why a message is in its state
Section titled “Why a message is in its state”When a message is held, waiting to retry, rejected, expired, suppressed or unknown, its page shows Reason for this status: what happened, what to do, and the reason code. The code is recorded at the moment the state changes, so it explains that change, not just today’s situation. If no reason was recorded, the page says so. Every code is listed under Reason codes.
When a reason says not to resend, don’t: the message may already have arrived, or it may still be sent once released. Control never offers to resend a message.
Route and delivery trace
Section titled “Route and delivery trace”Each message page shows its route, oldest first, with who reported each step:
- Accepted for sending: API or SMTP, and the name of the credential.
- Holds and retries, each with its reason.
- Sending attempts, with the attempt number, the route (
weneed.email direct route) and the result. - Relay acceptance.
- The recipient’s mail server: acceptance, bounce, delay, and the enhanced status code of any delivery report.
- Afterwards: a spam complaint, or a block on the address.
A step without evidence is shown as Not observed; it is never filled in by guessing. The page also lists what weneed.email can’t see: the final TLS connection and the recipient’s mail server name, inbox placement, opens and reads, and spam complaints on the direct route.
The timeline
Section titled “The timeline”Each message shows:
- Origin and transport: whether it came from your application or a setup test, over API or SMTP.
- Attempts: each delivery attempt with its time, kind and reason code. The newest 25 are shown; ask support for older ones.
- Current blockers: what currently stops this message, or the project, from sending. This is today’s state, not necessarily why the message stopped back then.
Inspect and export an email
Section titled “Inspect and export an email”Open a message, then Inspect email and headers. You can download the full email as .eml,
export its headers as text, or export content and message details as JSON. HTML is shown as source
inside Control; download the email to view it in a mail application.
A signed copy is the exact email prepared for its latest sending attempt. It does not prove that attempt succeeded. If a signed copy was not recorded, Control labels the export as a reconstruction from the accepted content. Headers added by a receiving server can only be inspected in the recipient’s mailbox.
Export this page as CSV downloads the currently filtered page of message history. Use the page-size control or move to the next page for more records.
What is kept
Section titled “What is kept”Message history, full email content and recorded outbound headers are available for 30 days from acceptance. Content that was already deleted under the previous policy is unavailable. After the window ends, the email disappears from customer history and exports. Finished-message content is removed by the cleanup worker. Content still needed for pending processing is kept until that processing ends. Internal accounting, suppression and security records have separate lifecycles; the history window does not erase them.