Suppression management
Your workspace has a suppression list. Any send to an address on it is skipped. This is the single most common reason a message you believe you sent never appears anywhere.
The four reasons
| Reason | Added by |
|---|---|
bounce |
Automatically, on a permanent failure |
complaint |
Automatically, when a feedback loop reports your mail as spam |
unsubscribe |
Automatically, when a recipient uses the one-click unsubscribe link |
manual |
By you, through the API or the console |
In practice today, effectively everything on a real suppression list is a
bounce. The complaint path is built and no feedback loop currently delivers
to it, and unsubscribe entries only appear if you opt messages into the
managed header with "unsubscribe": true.
Reading the list
curl -s "https://api.lockally.com/v1/suppressions?reason=bounce" \
-H "Authorization: Bearer $LOCKALLY_API_KEY"
{
"data": [
{
"email": "nobody@example.com",
"reason": "bounce",
"source": "stalwart",
"created_at": "2026-10-11T08:02:19Z"
}
]
}
source says which mechanism added it, which is how you tell an automatic
entry from one of your own. GET /v1/suppressions/{email} checks a single
address. Both need suppressions:read.
Adding and removing
# Add
curl -X POST https://api.lockally.com/v1/suppressions \
-H "Authorization: Bearer $LOCKALLY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"email":"someone@example.com","reason":"manual"}'
# Remove
curl -X DELETE https://api.lockally.com/v1/suppressions/someone@example.com \
-H "Authorization: Bearer $LOCKALLY_API_KEY"
Both need suppressions:write.
A complaint suppression should essentially never be removed. Somebody pressed a spam button.
Which reasons block which sends
This is the detail that decides whether a given message goes out, and it is not uniform across the four reasons.
| Reason | Blocks transactional sends | Blocks opt-in (unsubscribe: true) sends |
|---|---|---|
bounce |
Yes | Yes |
complaint |
Yes | Yes |
unsubscribe |
No | Yes |
manual |
No | Yes |
So a hard bounce from a marketing send does block that address for your password resets and receipts, because an address that does not exist does not exist for those either. Someone unsubscribing from your newsletter does not, which is correct: they opted out of marketing, not out of their own account.
If a password reset is not arriving for one user and everything else looks healthy, check their address against the list before anything else, and check the reason.
Every recipient suppressed is a success, not an error
A send whose recipients are all suppressed returns 200, not an error:
{
"status": "suppressed",
"warning": "All recipients are on your suppression list; nothing was sent."
}
No message is created and nothing is queued. Treating this as a failure and
retrying is pointless; treating it as a success and assuming delivery is
worse. Check status rather than only the HTTP code.
It is a filter, not a fix
A suppressed send does not fail loudly, and it does not improve your numbers.
- Your bounce rate is computed from what went out and failed, so suppressing an address stops the next bounce but does not undo the last one.
- Your application keeps asking. Nothing tells it the address is dead unless it checks.
- Your list stays dirty. The suppression list is a record of damage already taken, not a cleaning service.
Export it periodically and reconcile it against your own database. That is the step that actually moves your bounce rate.
curl -s "https://api.lockally.com/v1/suppressions" \
-H "Authorization: Bearer $LOCKALLY_API_KEY" \
| jq -r '.data[] | [.email, .reason, .created_at] | @csv'
A second, separate list exists
The platform also keeps a system-wide suppression list for its own transactional mail, the account notifications we send you. It is operated by Lockally, is not your list, is not visible through this API, and never affects your sends. It is mentioned only so the two are not confused if support refers to it.