Email delivery guide
Submitted vs delivered email
Submitted means an email provider accepted a message for processing. Delivered is a later provider-reported result. Learn what each email status confirms.
Reviewed September 6, 2026
The provider accepted the message for processing.
A later event says the recipient server accepted the message.
Submitted confirms a handoff. It does not confirm delivery.
Definitions
What each status confirms
These statuses describe two different points in the delivery process. Treating them as the same can hide delays and failures that occur after provider acceptance.
Submitted
Submitted means the delivery provider accepted the message from RouteKite for processing. The provider can still delay the message, encounter a failure, or receive a rejection from the recipient server.
Delivered
Delivered is a later provider-reported state. It means the recipient server accepted the message. It does not prove that the message appeared in the inbox, was displayed to the recipient, or was read.
Use Submitted to confirm handoff. Use Delivered to confirm the later recipient-server result.
RouteKite states
Read the complete route
A message can stop before submission, wait in RouteKite, reach the provider, and then receive one of several later results.
- Suppressed
- The message was stopped before provider submission.
- Queued
- RouteKite recorded the message and prepared it for submission.
- Submitted
- The receiving provider accepted the handoff for processing.
- Delivered
- A later provider event reported that the recipient server accepted the message.
- Delayed
- The provider reported a temporary delivery delay.
- Bounced
- The recipient server rejected the message.
- Failed
- Submission or delivery could not complete.
Troubleshooting
What to check when delivery is unclear
Start with the latest state, then use the message history to understand how and when it changed.
- Confirm the message ID
Make sure you are inspecting the record created for the exact recipient and send attempt.
- Read the current state
Check whether the message is still queued, submitted, delayed, or already terminal.
- Open the delivery history
Use timestamps and event order to see the path that produced the current state.
- Read the recorded explanation
For a bounce or failure, use the stored reason to decide whether the address or message needs attention.
Delivery analytics
Keep the latest state and its history together.
RouteKite connects workspace totals, campaign delivery, and the message record for each recipient.