Article
Suppressions · Docs - Bird
bird.com
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
Only a hard-class bounce suppresses, and the classification table shows which bounce_class values count as hard. Two outcomes that look like failures leave the address sendable: “Soft bounces and deferrals (email.deferred, or email.bounced with bounce_type: "soft"): transient failures like a full mailbox. We retry.” Send-side rejections: generation failures and policy rejections are problems with the send rather than the address. They produce email.rejected events and no suppression.
Remove an address “Be deliberate about removing a hard_bounce record, because an address that still does not exist bounces on the next send and re-suppresses itself.” What happens when you send to a suppressed address
Each record has a reason saying why the address is listed, and an applies_to policy controlling which categories it blocks: “hard_bounce all Blocked Blocked” The split follows from what each reason means:
An unsubscribe, whether through the in-body link or the one-click button, does not appear here: it records a preference on the Preferences tab instead of adding a row to this list. “Only a hard-class bounce suppresses” Soft bounces and deferrals (email.deferred, or email.bounced with bounce_type: "soft"): transient failures like a full mailbox. We retry.
Remove an address “Be deliberate about removing a hard_bounce record, because an address that still does not exist bounces on the next send and re-suppresses itself.” What happens when you send to a suppressed address
Your workspace owns a suppression list: a set of email addresses we do not deliver to. Hard bounces and spam complaints land on it on their own, and you can add addresses yourself. Repeatedly mailing addresses that bounce or report spam can get your domain blocked by mailbox providers, so we stop those sends before they leave the platform. “It records the recipient's own stated preference rather than a deliverability fact, so it lives on the Preferences tab instead.” Manage the list in Email > Suppressions, through the suppressions API, or with bird email suppressions.
“Your workspace owns a suppression list: a set of email addresses we do not deliver to.” An unsubscribe is not on this list. It records the recipient's own stated preference rather than a deliverability fact, so it lives on the Preferences tab instead. See Unsubscribe links for how that works.
Your workspace owns a suppression list: a set of email addresses we do not deliver to. Hard bounces and spam complaints land on it on their own, and you can add addresses yourself. Repeatedly mailing addresses that bounce or report spam can get your domain blocked by mailbox providers, so we stop those sends before they leave the platform. “An unsubscribe is not on this list.” Manage the list in Email > Suppressions, through the suppressions API, or with bird email suppressions.
The three reasons and what they block “Each record has a reason saying why the address is listed, and an applies_to policy controlling which categories it blocks:” Reason applies_to Marketing category Transactional category hard_bounce all Blocked Blocked complaint non_transactional Blocked Allowed manual all Blocked Blocked
“so we stop those sends before they leave the platform.” An unsubscribe is not on this list. It records the recipient's own stated preference rather than a deliverability fact, so it lives on the Preferences tab instead. See Unsubscribe links for how that works.
“Hard bounces and spam complaints land on it on their own, and you can add addresses yourself.” An unsubscribe is not on this list. It records the recipient's own stated preference rather than a deliverability fact, so it lives on the Preferences tab instead. See Unsubscribe links for how that works.
“Repeatedly mailing addresses that bounce or report spam can get your domain blocked by mailbox providers” An unsubscribe is not on this list. It records the recipient's own stated preference rather than a deliverability fact, so it lives on the Preferences tab instead. See Unsubscribe links for how that works.
Trigger Resulting suppression Hard bounce (email.bounced) reason: hard_bounce, origin: bounce_event, applies_to: all Out-of-band hard bounce (email.out_of_band_bounce) reason: hard_bounce, origin: bounce_event, applies_to: all Spam complaint (email.complained) reason: complaint, origin: complaint_event, applies_to: non_transactional “An unsubscribe, whether through the in-body link or the one-click button, does not appear here: it records a preference on the Preferences tab instead of adding a row to this list.” Only a hard-class bounce suppresses, and the classification table shows which bounce_class values count as hard. Two outcomes that look like failures leave the address sendable:
Only a hard-class bounce suppresses, and the classification table shows which bounce_class values count as hard. Two outcomes that look like failures leave the address sendable: “Soft bounces and deferrals (email.deferred, or email.bounced with bounce_type: "soft"): transient failures like a full mailbox. We retry.” Send-side rejections: generation failures and policy rejections are problems with the send rather than the address. They produce email.rejected events and no suppression.
An unsubscribe is not on this list. It records the recipient's own stated preference rather than a deliverability fact, so it lives on the Preferences tab instead. See Unsubscribe links for how that works. “Manage the list in Email > Suppressions, through the suppressions API, or with bird email suppressions.” The three reasons and what they block
The three reasons and what they block “Each record has a reason saying why the address is listed, and an applies_to policy controlling which categories it blocks:” Reason applies_to Marketing category Transactional category hard_bounce all Blocked Blocked complaint non_transactional Blocked Allowed manual all Blocked Blocked
“Your workspace owns a suppression list: a set of email addresses we do not deliver to.” An unsubscribe is not on this list. It records the recipient's own stated preference rather than a deliverability fact, so it lives on the Preferences tab instead. See Unsubscribe links for how that works.
The split follows from what each reason means: “Sending is pointless in any category, so it blocks everything.” complaint: a statement about unwanted mail. Someone who reported your newsletter as spam may still need a password reset or an order confirmation, so it blocks only non-transactional sends.
“Hard bounces and spam complaints land on it on their own, and you can add addresses yourself.” An unsubscribe is not on this list. It records the recipient's own stated preference rather than a deliverability fact, so it lives on the Preferences tab instead. See Unsubscribe links for how that works.