# Understand email statuses and logs

Prontuno records each transactional email and updates its status as the message moves through the delivery process.

## Status reference

- Status | Meaning | What to do
- Queued | Prontuno has the message and is preparing it for sending. | Wait briefly. Investigate if messages remain queued unusually long.
- Sent | Prontuno accepted the message for delivery. | No action unless the message does not progress.
- Delivered | The recipient’s mail server accepted the message. | No transport action. Ask the recipient to check spam or filtering if it is not visible.
- Deferred | The recipient’s server temporarily delayed delivery. | Prontuno will retry. Review the response if deferrals persist.
- Bounced | The recipient’s server rejected delivery. | Read the bounce reason. Correct bad addresses and do not repeatedly send to permanent failures.
- Rejected | Prontuno rejected the message before delivery. | Review the rejection reason, sender domain, recipient, suppression state, and account status.

## Delivered does not always mean inboxed

A Delivered event confirms that the destination mail server accepted the message. The provider can still place it in spam, quarantine it, route it through an inbox rule, or delay its appearance.

## Find a message

1. Open **Emails** in the Prontuno dashboard.
2. Search by recipient or subject.
3. Filter by status, sending domain, or date range.
4. Open the matching message.

The email detail page shows the public email ID, sender, recipient, UTC timestamps, delivery time, message size, status reason, content preview, plain text, HTML, and attachments when available.

## Investigate a failure

1. Copy the email’s public ID for support or internal tracking.
2. Read the rejection or bounce reason.
3. Confirm that the recipient address is valid and not suppressed.
4. Confirm the `From` address uses the credential’s verified domain.
5. Check whether the team, domain, API key, or SMTP credential is disabled.
6. Compare similar failures to see whether they affect one recipient, one provider, or all traffic.

## Use webhooks for application state

Dashboard logs are useful for investigation. For automated workflows, subscribe to webhooks and update your own records from `email.sent`, `email.delivered`, `email.deferred`, `email.bounced`, and `email.rejected` events.

Always verify webhook signatures and process each event ID once.

## Next steps

For corrective steps, see [Troubleshoot sending and delivery](https://prontuno.com/docs/category/deliverability/).