> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Bounces, Spam Complaints, and Unsubscribes

> Review suppression types, import and export addresses, configure unsubscribe elements, and choose where bounce notifications go.

Use **Analytics** to investigate delivery events and **Suppressions** to review addresses excluded from future sending. A suppressed recipient can produce a dropped message even when your application submits a new send request.

## Understand delivery failures

A **hard bounce** is a permanent delivery failure, such as a nonexistent address. Remove invalid addresses from your active list.

A **soft bounce** is a temporary failure, such as a full mailbox or an unavailable receiving server. Review the reason and retry history before treating it as permanent.

A **spam complaint** records a recipient's report of unwanted mail when that report is available to turboSMTP. An **unsubscribe** records an opt-out. Keep your own contact database synchronized with these events.

## View and manage suppressions

Open **Suppressions** in your [dashboard](https://dashboard.serversmtp.com). The **Type** column identifies the source:

| Type | Meaning |
| - | - |
| **Manual** | Added through a manual import |
| **Bounced** | Added following a delivery failure |
| **Spam** | Added following a spam report |
| **Unsubscribed** | Added following an opt-out |
| **Validation failed** | Added following failed address validation |

Review the recipient, date, and reason when investigating an entry. Use **Import suppressions** to add addresses and **Export** to download suppression data.

Removing an entry allows another delivery attempt. Only remove it after resolving the original issue and confirming the recipient should receive your messages. See the [official dropped-email explanation](https://serversmtp.com/en/smtp/23-What-is-a-dropped-email/kb-3933.html).

## Configure unsubscribe links

Open **Settings → Email elements → Unsubscribe link** to configure the available unsubscribe element. The same tab contains **Footers** and **Templates**. Review opt-outs in **Suppressions** and honor them in your application before sending again.

See [email settings](/docs/account/email-settings.md) for related controls. Consult the [terms and conditions](https://serversmtp.com/terms-and-conditions/) for service requirements.

## Choose where bounce notifications go

Open **Settings → Notifications → Bounces Management**. The card explains:

> Enabling Bounce Notifications sends notifications about your bounced emails to us. To receive all your bounce notifications yourself, disable this option.

This setting controls the destination of bounce notifications. Manage suppressed addresses separately under **Suppressions**. See the [bounce notification instructions](https://serversmtp.com/en/smtp/31-How-can-I-get-notified-of-my-bounce/kb-4862.html).

## Export through the API

Use `GET /suppressions/csv` with a date range in `YYYY-MM-DD` format and a key with **Statistics & Management APIs** enabled:

```bash Terminal theme={"system"}
curl --get 'https://pro.api.serversmtp.com/api/v2/suppressions/csv' \
  -H "consumerKey: $TURBOSMTP_CONSUMER_KEY" \
  -H "consumerSecret: $TURBOSMTP_CONSUMER_SECRET" \
  --data-urlencode 'from=2026-10-01' \
  --data-urlencode 'to=2026-10-27' \
  --output suppressions.csv
```

Set the environment variables locally and choose your date range. For filters, imports, and removals, see the [suppressions API reference](/docs/api-reference/suppressions.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.