Email delivery statuses
Every email has a status. It starts as QUEUED and ends in a status that says whether the inbox took it. A team webhook gets email.sent, email.delivered, email.bounced, email.complained and email.failed.
What each status means
| Status | Meaning | Charged? |
|---|---|---|
| Queued | Ponitor accepted it and is sending it. | Yes |
| Sent | It's on its way to the inbox. | Yes |
| Delivered | The recipient's mail server accepted it. | Yes |
| Delayed | The recipient's mail server isn't taking email right now. It's tried again. | Yes |
| Bounced | The address doesn't exist or wouldn't take it. | Yes, not refunded |
| Complained | It was delivered, then the recipient marked it as spam. | Yes |
| Failed | It couldn't be sent. | No, refunded |
BOUNCED,COMPLAINEDandFAILEDare final.DELIVEREDis final unless the recipient later marks the email as spam.- An email can fail after it's
SENT, if it never reaches the recipient's mail server. It's refunded then too. - We may add statuses. Treat a status you don't recognize as not final.
Webhook events
| Event | When |
|---|---|
email.sent | An email left Ponitor for the inbox. |
email.delivered | The recipient's mail server accepted it. |
email.bounced | It bounced. |
email.complained | The recipient marked it as spam. |
email.failed | It couldn't be sent, and its cost was refunded. |
DELAYED sends no event. The email sends email.delivered or email.bounced when it settles. The events cover every email your team sends: from the API, from Email › Send, and a template's Send Test. Each event carries the email, as Webhook events shows.
Why an email failed
A FAILED email has a failureReason in plain words that you can show your users:
failureReason | What happened |
|---|---|
The email was refused, so it was never sent. Check the address and the sender. You were refunded. | The address or the sender was refused at once. |
The email couldn't be sent after several tries. You were refunded. | Ponitor tried for about five minutes. |
The email couldn't be sent within a day. You were refunded. | It waited a day without going out. |
The sender's domain wasn't verified when the email went out. You were refunded. | The domain was no longer verified. See Domain statuses. |
Sending was paused before this email went out. You were refunded. | Your team's sending was paused. See below. |
The email couldn't be sent. You were refunded. | Any other failure. |
A BOUNCED email isn't failed: its bounce event's detail says why. See Get an email.
Following an email
- In production, use a webhook. A team webhook gets each
email.*event. - For a one-off check, call Get an email. It returns the current
status,failureReasonandcost, and every event so far. Don't call it in a loop.
Most emails are DELIVERED within a minute. Stop sending to an address that bounced or marked your email as spam.
When sending is paused
Mail servers judge senders by how many of their emails bounce or are marked as spam. Every team's emails go out together, so one team's bounces can hurt every team's mail. Ponitor pauses a team's sending before that happens.
Your team is warned, then paused, when one of these crosses its line:
| Sent in 30 days | Counted | Warning | Paused |
|---|---|---|---|
| 200 or more | The share that bounced | 2% | 3% |
| 200 or more | The share of those delivered that were marked as spam | 0.04% | 0.06% |
| Fewer than 200 | Emails that bounced | 10 | 20 |
| Fewer than 200 | People who marked an email as spam | 1 | 2 |
Whatever your team sends, a spike in the last 24 hours also pauses it, with no warning first: 50 or more bounces that are at least 3% of that day's emails, or 3 or more spam reports that are at least 0.06% of those delivered.
- Email › Overview shows your team's Sending Health: Healthy, At Risk past a warning, or Paused, and what crossed the line.
- While sending is paused, every send is refused with
403(E02017), from the API and from the app, and nothing is charged. Emails still waiting to go out fail and are refunded. - Contact us to resume sending. Once it's resumed, the counts start again from then.
Send only to people who asked for your emails, and stop sending to an address that bounced, to keep bounces and spam reports low.
Try it in the sandbox
| Send to | What happens |
|---|---|
delivered@example.com | It ends as DELIVERED. |
bounced@example.com | It ends as BOUNCED, and isn't refunded. |
complained@example.com | It's delivered, then ends as COMPLAINED. |
failed@example.com | It ends as FAILED, and is refunded. |
| Any other address | It stays SENT. |
Bounces and spam reports in the sandbox never pause your sending. See Test email with test addresses.