Manage recipients that Email Service must not contact. For suppression triggers and expiration rules, refer to Suppression lists.
The dashboard and API are account-scoped. Entries apply to every sending domain and subdomain in the account.
-
In the Cloudflare dashboard, go to Compute > Email Service > Email Sending.
Go to Email Sending ↗ -
Select Suppressions.
The table displays each recipient, reason, creation time, and expiration. Never means the entry has no scheduled expiration.
- In Suppressions, enter the recipient email address.
- Select an expiration preset, a custom future time, or Never.
- Select Add.
Entries created in the dashboard have the manual reason. They apply to every sending domain in the account.
You can paste addresses or upload .csv, .json, or .txt files. Supported file contents are:
.csvor.txt: Put one entry on each line as<EMAIL_ADDRESS>or<EMAIL_ADDRESS>,<EXPIRATION_TIMESTAMP>. Use an RFC 3339 ↗ timestamp and omit the header row..json: Use an array of address strings or objects. Each object requiresemailand can include an RFC 3339expires_attimestamp.
- In Suppressions, select Import.
- Upload a supported file or paste the addresses.
- Choose a default expiration for entries that omit one.
- Select Import. Larger imports run in batches, so keep the dialog open until every batch finishes.
To remove a mutable entry, select Delete for that recipient. Read-only entries do not provide a delete action.
Deleting an entry permits future delivery attempts. Verify that the recipient should receive mail before deleting an automatic suppression.
The account Email Sending suppression management REST API supports listing, adding, importing, updating, and deleting entries. Requests require an API token with the Email Sending: Edit permission.
API clients must use read_only to determine whether an entry is mutable. Do not infer mutability from the reason value.
Each account can have one active entry per address. For page size, import, and rate limits, refer to Suppression list limits.