Suppressions

A suppression stops Jumploon from sending to an address. Sending to addresses that bounce or don't want your mail hurts your reputation with mailbox providers, so Jumploon suppresses them for you.

Type	Added when
`bounce`	The recipient's server permanently rejected a message, for example because the mailbox doesn't exist
`unsubscribe`	The recipient clicked an unsubscribe link or used one-click unsubscribe
`spam_report`	Added by you, for recipients who reported your mail as spam
`invalid`	Added by you, for addresses you know are invalid

When you send to a suppressed address, that recipient is dropped (you'll see a dropped or email.suppressed event) and the rest of the message is delivered normally.

If the rejection came from a temporary problem or a misconfiguration on Jumploon's side rather than the recipient, the address isn't suppressed.

Manage suppressions

In the dashboard, open Suppressions to search, add and remove addresses. Through the API:

# List, optionally filtered
curl "https://api.jumploon.com/v3/suppressions?type=bounce&email=ada@example.org" \
  -H "Authorization: Bearer $JUMPLOON_API_KEY"
 
# Add up to 1,000 addresses at once
curl https://api.jumploon.com/v3/suppressions \
  -H "Authorization: Bearer $JUMPLOON_API_KEY" -H "Content-Type: application/json" \
  -d '{ "type": "unsubscribe", "emails": ["ada@example.org"], "reason": "Asked by phone" }'
 
# Remove one
curl -X DELETE https://api.jumploon.com/v3/suppressions/bounce/ada@example.org \
  -H "Authorization: Bearer $JUMPLOON_API_KEY"

Only remove a bounce if you're sure the address now works, and only remove an unsubscribe if the person asked to be resubscribed.

Bypassing suppressions

For critical transactional mail that must reach an address that once unsubscribed from marketing (a password reset, for example), the v3 API accepts:

"mail_settings": { "bypass_list_management": { "enable": true } }

Use it sparingly. It doesn't make a bouncing address deliverable.