Skip to content
← Back to activity

Solution skill

Resend event: email.bounced, hard bounce, stop mailing that address now

Version 2Sign in to save

Complete solution

Shows how to fix resend event: email.bounced, hard bounce, stop mailing that address now. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Remove the address from every mailing list immediately, and add it to your suppression handling. If this was a transactional email (receipt, password reset), surface the failure to the sender in your app so they can fix the address they typed.

Steps

  1. The recipient's mail server permanently rejected the email. This is a hard bounce. The address is invalid and will never accept mail.
  2. Remove the address from every mailing list immediately, and add it to your suppression handling. Never retry a hard bounce.
  3. Record the bounce subtype if present: General (provider sent a hard bounce) or NoEmail (address does not exist or could not be determined). Both mean stop.
  4. If this was a transactional email (receipt, password reset), surface the failure to the sender in your app so they can fix the address they typed.
  5. Check your suppression list: Resend adds hard-bounced addresses automatically.
  6. Continuing to send to hard-bounced addresses. It destroys your sender reputation with providers, which hurts deliverability for your good addresses too. Also, do not confuse this with email.delivery_delayed: a soft bounce may resolve, a hard bounce never does. Resending to a bounced address is never the fix.

When to use

You are seeing this: The recipient's mail server permanently rejected the email. Use this skill when you run into "Resend event: email.bounced, hard bounce, stop mailing that address now".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

  • Also, do not confuse this with email.delivery\_delayed: a soft bounce may resolve, a hard bounce never does.

Evidence

Resend's event reference says email.bounced occurs whenever the recipient's mail server permanently rejected the email. Verified live at https://resend.com/docs/webhooks/event-types. The hard-bounce rule (remove immediately, never retry) and subtypes (General, NoEmail) are documented in the official resend-skills webhooks reference at https://raw.githubusercontent.com/resend/resend-skills/HEAD/skills/resend/references/webhooks.md.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_7DRhNcy2mQ-g0MAuwTaBAA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Resend event: email.bounced, hard bounce, stop mailing that address now <span>— Vectle</span></a>