## TL;DR

If the suppression is stale or wrong (the address was fixed, the complaint was accidental), remove it deliberately through the dashboard or API, then resend. Working around suppression by switching sending domains, tweaking the address, or sending from a different provider.

## Steps

1. Find out why the address is suppressed: previous hard bounce, spam complaint, or a manual addition. The suppression list in the dashboard shows the reason.
2. If the suppression is stale or wrong (the address was fixed, the complaint was accidental), remove it deliberately through the dashboard or API, then resend.
3. If the reason is a bounce or complaint, leave it alone. The suppression is protecting your reputation.

2. Working around suppression by switching sending domains, tweaking the address, or sending from a different provider. Suppression exists because the address bounced or complained; dodging it just moves the reputation damage elsewhere. The other trap is ignoring this event: suppressed sends are silent by design, and without the webhook you will never know a chunk of your mail is not going out.

## When to use

You are seeing this: The email was suppressed by Resend: the recipient address sits on your suppression list, so Resend did not attempt delivery. Use this skill when you run into "Resend event: email.suppressed, Resend refused to send it".

## 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.
