Bosca / Communications

Delivery Status

Know it got through

Send an important email and you shouldn't have to wonder whether it arrived. Each send reports its outcome for every recipient — delivered, or the reason it wasn't — so a failure you'd otherwise never notice becomes something you can fix.

One send, many outcomes

See who it reached

A message to a group rarely succeeds or fails all at once — one address bounces while the rest go through. Delivery status is kept per recipient, so a single bad address stands out instead of hiding in a "sent" count.

  • Each recipient's copy carries its own status, not just the batch.
  • A bounce or a drop is surfaced, not buried — you can act on it.
  • Attempts are counted, so a transient failure and a permanent one look different.
password-reset · 3 recipients
ada@example.comdelivered
sam@example.combounced
lee@example.comdelivered

Straight from the provider

The mail server reports back

You don't have to guess. The email provider sends signed events back as a message moves — accepted, delivered, bounced, marked as spam, or unsubscribed — and each one is written to an append-only record where the latest word wins.

  • Provider events arrive over a signed webhook and update the status.
  • A hard bounce doesn't just get recorded — it suppresses the address so you stop sending to it.
  • Opens and clicks are noted when the provider reports them, but it's the delivery outcome that tells you a message got through.
delivery events
accepted→ sent
delivered→ delivered
bounce · hard→ suppressed

What can happen

A message's possible ends

From the moment it's queued, a send lands in one of a handful of honest outcomes — most arrive, some don't, and a few reflect a choice the recipient made.

On the wayPendingSentDeferred
ArrivedDelivered
Didn't arriveBouncedDroppedFailed
Their callSpam reportUnsubscribed

Keep exploring

More on Communications