# suppression.added / suppression.removed: who you must not mail
`suppression.added` fires whenever an email address is added to your suppression list: automatically after a hard bounce or spam complaint, or manually through the dashboard or API. `suppression.removed` fires when an address leaves the list.
## What to do on receipt
1. On `suppression.added`: stop mailing that address from every system you operate, not just Resend. The cause (bounce or complaint) applies to the address itself.
2. Record the reason alongside the address. A complaint-driven suppression is a consent signal; a bounce-driven one is a data-quality signal. They need different follow-ups.
3. On `suppression.removed`: confirm the removal was intentional and authorized. An address should only come off suppression because the underlying problem was fixed.
## The trap
Re-adding suppressed addresses casually, or letting a list import resurrect them. Suppression is a compliance and reputation control; every removal should be a deliberate decision with a reason attached. The other trap is partial compliance: honoring suppression in Resend while another tool keeps mailing the same address.