Understand why a send stopped.
Read the suppression reason and applicable category. A manual restriction, a complaint and a bounce can have different origins; preserve the information needed to review the decision.
Read suppression behavior ↗Email抑制
Email suppressions.
Remember what matters.
Keep delivery restrictions with the sending decision. Understand why a recipient is suppressed and avoid repeating a known ineligible send.
A stopped send should have a clear reason.
Understand why an address is excluded before the next send. Review its history alongside the message category and the customer’s preferences.
HISTORY / alex@example.com
- Campaign membership
The address belongs to the selected example audience.
- Restriction recorded
A bounce, complaint or manual migration record carries its own reason and scope.
- Eligibility evaluated
Customer preference and suppression are evaluated separately.
{
"recipient": "alex@example.com",
"reason": "hard_bounce",
"applies_to": "all",
"category": "marketing",
"preference": "allowed",
"replayed_decision": false
}ELIGIBILITY / CURRENT SELECTIONRead suppression scope and removal ↗
Inspect the record.Exclude the recipient.This record allows the category.
No current decision. Trace this reason, category and preference; changing inputs clears the previous result.
Customer policy excludes this recipient even if this suppression record allows the category.
The scope is unrecognized. Keep the recipient excluded and inspect the documented policy; unknown scope is not sending permission.
The recorded restriction blocks this category. Audience membership and a repeated event do not erase it.
This complaint record alone does not block the transactional example. Other suppressions, preferences and account policy still need checking before a send.
Repeated evaluation: the same restriction remains authoritative. No new record or send was created.
Companies that trust Bird across their communications.
Read Bird customer storiesSending policy with a clear history.
Carry valid restrictions forward.
A migration needs recipient restrictions as well as addresses. Keep contact permission and unsubscribe preferences separate, and investigate incomplete exports before moving a cohort.
Prepare the migration ↗影响你声誉的最大单一杠杆。
抑制功能内置于 Bird Email API 中。硬退信记录会阻止向无效地址发送邮件，投诉记录会阻止非事务性邮件。您可以查看拒绝原因和触发消息，了解收件人被拒绝的原因。
抑制保护你的五种方式。
自动、可撤销、可查询。
退信 + 投诉时自动触发。
硬退信和垃圾邮件投诉会自动创建抑制记录。退订请求显示在偏好设置中。
可撤销。
移除抑制前请先调查原因。其他阻止记录和退订偏好仍然有效。
手动添加条目。
你也可以自行添加地址：比如从其他服务商导入的一份已知无效地址清单。
可通过 API 查询。
查看完整列表、按地址或原因筛选、添加条目，或通过记录 ID 删除条目，让您的系统始终保持同步。
类别感知检查。
硬退信和手动抑制会阻止所有类别的邮件。投诉会阻止非事务性邮件。收件人的偏好会单独检查。
默认自动运行，掌控权在你手中。
无需手动操作，列表即可自动生效；退信和投诉会自动触发抑制。当您确实需要操作时，整个列表就是一个 API：添加已知的无效地址、按地址或原因筛选，或删除记录以恢复已修复的收件人。Bird CLI 支持读取和删除操作，AI 代理也可通过 MCP 执行相同的操作。
suppressions.sh
bird CLI
# Look up why an address is on the list.
$ bird email suppressions list --email ada@example.com \
| jq -c '.data[] | {id, reason, applies_to}'
{"id":"sup_01krdgeqcxet5s7t44vh8rt9mg","reason":"hard_bounce",
"applies_to":"all"}
# Reinstate one that recovered, by record id.
$ bird email suppressions remove sup_01krdgeqcxet5s7t44vh8rt9mg --yes
Look up a suppression with CLI or MCP before changing it. Review the reason and the recipient’s consent before deciding whether to resume sending.
三种抑制原因。独立的偏好设置。
硬退信和手动条目会阻止所有邮件。投诉会阻止非事务性邮件。退订会创建单独的偏好记录；移除抑制不会清除该偏好。
| 原因 | 触发方式 | 拦截范围 |
|---|---|---|
| hard_bounce | 永久性退信 | 所有邮件（事务性 + 营销） |
| complaint | 垃圾邮件投诉 | 仅营销邮件 |
| manual | 由你通过 API 或仪表盘操作 | 所有邮件（事务性 + 营销） |
关于邮件抑制的常见问题
哪些收件人会被自动抑制？
硬退回会为所有邮件创建抑制；投诉会为非事务性邮件创建抑制。手动抑制会阻止所有类别。软退回和延迟不会创建永久的收件人抑制。
退订算是抑制吗？
退订会在偏好设置选项卡中记录收件人的偏好。它与抑制列表是分开的。在决定是否投递时两者都会被检查，删除联系人不会清除其退出记录。
我可以移除或测试屏蔽记录吗？
在查明原因后，您可以通过控制面板或 API 移除屏蔽记录。移除一条屏蔽记录不会移除其他拦截记录或退订偏好。suppressed@messagebird.dev 沙盒地址允许您在不更改列表的情况下测试被拒收件人。
保护下一次发送
与我们的邮件团队交流
将收件人偏好融入您的发送流程。
讨论退订、抑制列表导入和应用级别控制。我们将帮助您规划收件人偏好如何随邮件流转。
创建您的账户，然后查看或导入需要排除的收件人。