# Delivery, suppression, and troubleshooting

> Understand real provider-backed email states and resolve domain or recipient problems safely.

## Delivery states

| State | Meaning | 
| Queued | Accepted by Beam and reserved against the workspace cap. | 
| Accepted or sent | The transport accepted the outbound attempt. | 
| Delivered | A provider delivery event was recorded. | 
| Delayed | Delivery is still being attempted; Beam does not create a second send. | 
| Bounced, complained, suppressed, or failed | A real terminal provider event was recorded. | 
| Delivery unknown | The transport result was uncertain. Beam holds for review and never blindly retries. | 

## Suppressions
Beam blocks a suppressed recipient before sending. Bounce and complaint events update the workspace event ledger and delivery health. Agencies see only their clients; clients see only their workspace.

## Verified does not mean inboxed
A verified domain has the required sending authentication, but mailbox providers also score domain history, sending patterns, recipient engagement, content, and complaints. Start a new domain at low, consistent volume, use a recognizable sender identity, send relevant person-to-person content, and increase volume gradually. If a recipient finds a wanted Beam message in spam, they should mark it not spam rather than repeatedly resending it.

## Attachments
Outbound email accepts approved file types within the per-file and total limits. Inbound files are fetched only from the approved transport host, stored tenant-scoped, and downloaded through an authorized Beam route.

## Troubleshooting
- Check domain sending and receiving health.- Confirm the mailbox is active.- Check plan pause, monthly usage, hard cap, and recipient suppression.- Read the exact timeline event. Do not resend a delivery-unknown message.