What the suppression list does
The suppression list is the account-wide block list of addresses EuroMail will not send to. Before every send, the recipient is checked against it; a suppressed address is skipped rather than mailed. This is the single most important safeguard for your sender reputation. It stops you from repeatedly hitting addresses that bounce, complain, or have opted out.
For the full endpoint reference, see the Suppressions API reference.
What gets suppressed automatically
EuroMail adds addresses for you when:
| Source | When |
|---|---|
| Hard bounce | The address is invalid / does not exist. See Bounce & Feedback Loops. |
| Spam complaint | The recipient marks your mail as spam (via the feedback loop). |
| Unsubscribe | A recipient uses a one-click unsubscribe link. |
You do not have to do anything for these. The point is that a single bad signal permanently protects you from re-sending to that address.
Adding a suppression manually
Suppress an address yourself, for example when a customer asks by phone, or you learn an address is problematic:
curl -X POST https://api.euromail.dev/v1/suppressions \
-H "X-EuroMail-Api-Key: em_live_your_key_here" \
-H "Content-Type: application/json" \
-d '{
"email_address": "[email protected]",
"reason": "customer request"
}'The reason is free text for your own records and shows up when you list
suppressions.
Listing suppressions
curl "https://api.euromail.dev/v1/suppressions?page=1&per_page=100" \
-H "X-EuroMail-Api-Key: em_live_your_key_here"Each entry records the address, the reason/type, and when it was added. Use this to audit why a particular recipient stopped receiving mail.
Transactional vs. marketing suppression
Unsubscribes apply to marketing mail. Critical transactional mail (password
resets, receipts, security alerts) is the recipient's own account activity and
is generally not subject to an unsubscribe. Mark such sends with
"transactional": true (see Sending Emails).
Bounces and complaints, however, suppress an address for all mail: if an
address hard-bounces, continuing to send even transactional mail to it only
damages your reputation.
Removing a suppression
Suppressions are deliberately sticky. They exist to protect you. Remove one only when you are certain the underlying problem is resolved (for example, a customer fixed their mailbox and explicitly asked to resume). Manage removals from the Suppressions page in the dashboard, which records the change in your audit log.
Never bulk-clear suppressions to "reach more people." Every entry is a recipient who bounced, complained, or opted out. Re-mailing them is the fastest route to a blocklisting.
Related
- Bounce & Feedback Loops. How bounces and complaints are detected and fed in.
- Signup Forms. Unsubscribe handling that writes here automatically.
- Deliverability Insights. Monitor your bounce and complaint rates over time.