Email Events Guide
Understand the statuses and activity shown for an email in the Simply Send Email Events page.
How to read the timeline
Events describe different stages and outcomes of a send. Sent means the message was handed to a provider; Delivered means the destination mail server accepted it. Opens and clicks are engagement signals, while bounces, complaints, suppressions, and failures describe issues or recipient choices.
Email event types
| Event | Meaning |
|---|---|
| Sent | Simply Send accepted the message and handed it to the sending provider. This confirms submission, not acceptance by the recipient server. |
| Delivery Delay | Delivery is temporarily delayed and may still complete. A later event can confirm delivery or a final failure. |
| Delivered | The recipient server accepted the message. This does not guarantee inbox placement or that the recipient has read it. |
| Opened | An open-tracking request was recorded. Image proxies and privacy features can affect open detection. |
| Clicked | A click on a tracked link was recorded. |
| Bounced | The recipient server rejected the message. The event may include a permanent or temporary bounce type and a server diagnostic. |
| Complaint | The recipient reported the message as spam or abuse. |
| Unsubscribed | The recipient opted out through an unsubscribe action. |
| Suppressed | Simply Send intentionally blocked the send before handoff because the recipient matched an active suppression rule. |
| Reject | The sending provider refused the message before delivery. Review the event details for any available diagnostic. |
| Rendering Failure | The message could not be rendered, commonly because required template data was missing or invalid. |
| Fail | A send attempt failed. Review the event details for the reported error or diagnostic. |
| Queue | The message is waiting in a processing queue; it has not yet been confirmed as delivered. |
| Subscription | Subscription-related activity was recorded. New subscription opt-out activity is generally represented as Unsubscribed. |
| Other | A provider or platform event that does not use one of the standard event types above. |
Suppression and rejection
Suppressed
Simply Send intentionally stopped the send before handoff because the recipient matched an active suppression rule. This protects recipients, sender reputation, and deliverability.
- The address previously returned a permanent or hard-bounce result.
- The recipient reported a previous message as spam or abuse.
- The recipient unsubscribed from the workspace, sender domain, or relevant subscription group.
- The address is covered by an administrator-managed, imported, or platform-level protection rule.
When available, the event details show a suppression reason, bounce type, or diagnostic code.
Reject
The sending provider refused the message before delivery. Unlike a suppression, which is applied by Simply Send before handoff, a rejection is the provider’s refusal to continue with the send.
- Message content, headers, or an attachment did not meet sending requirements.
- Address or message data was malformed or unsupported.
- A security or sending-policy check stopped the message.
- An account, sender, recipient, or domain restriction prevented the send.
A rejection is different from a bounce: it means delivery was refused before the destination mailbox server produced a delivery outcome.
Common delivery delay causes
A Delivery Delay means the destination has not confirmed delivery yet and another delivery attempt may still be in progress. Common causes include:
- The recipient mailbox server is temporarily unavailable, restarting, or under maintenance.
- The recipient mailbox is full or the account is temporarily unable to accept mail.
- The receiving system is throttling senders or limiting the number of simultaneous delivery attempts.
- Greylisting or additional spam, malware, or content scanning is delaying acceptance.
- A transient network, DNS, or connectivity issue is preventing the receiving system from accepting the message.
- Only one or some recipients on a multi-recipient send are delayed; the event details may identify the affected recipients.
When supplied, the details popup can include a delay type, retry expiration time, affected recipient, or diagnostic code. The timeline may later show Delivered, Bounced, or another final outcome.