Skip to main content
The suppression list is the set of email addresses your organization will not send to. Campaigns, API sends and SMTP relay mail all skip a suppressed address, whichever sending domain the mail comes from.

​
Why addresses are suppressed

Most addresses land here on their own. Sending to a mailbox that has rejected you, or to someone who reported you as spam, damages your sending reputation, so Brudcast stops it for you. Soft bounces, the temporary kind, don’t suppress an address. The Added By column shows where each entry came from: Automatic, API, Dashboard or Import.
The suppression list covers email addresses only. SMS opt-outs are handled separately; see SMS overview.

​
Find an address

Type the full email address into the search box. Search matches whole addresses only, not part of one: addresses are stored encrypted, so there’s nothing to match a fragment against. Use the All reasons filter to show one reason at a time.

​
Suppress an address

1

Open the dialog

Go to Contacts > Suppressions and select Suppress Address.
2

Enter the address and a reason

Enter the Email address and choose Added manually or Invalid address as the Reason.
3

Confirm

Select Suppress Address. From now on no campaign, API or SMTP send reaches it.
Suppressing an address also cancels any signup-form confirmation still waiting for that address. If the address is already on the list, adding it again keeps the original entry and its reason. A manual add never overwrites a recorded hard bounce or complaint.

​
Remove an address

Select the bin icon on the address’s row, then Remove. The address starts receiving campaigns and API sends again.
Removing an address that hard-bounced or complained puts your sender reputation at risk. It’s suppressed again on the next bounce or complaint. Only remove one when you have a reason to believe the problem is fixed, such as the recipient asking to be sent to again.
When you remove a hard bounce or complaint, the matching email address on your contacts goes back to Unverified. Removing an entry doesn’t undo an unsubscribe. A contact who unsubscribed keeps the email status Suppressed on their record, and campaigns keep skipping them. See Unsubscribes and consent. Suppression and unsubscribing are different mechanisms. Suppression protects your sending reputation after a bounce or a complaint. An unsubscribe records a choice the person made. An unsubscribe is organization-wide, not limited to the list the campaign went to. Someone who unsubscribes is asking to stop hearing from you, not to be moved to your other list. Campaign emails carry the link, and you can place it yourself with the {{unsubscribe_url}} merge tag. It opens a page where the person confirms with a button, so mail scanners that follow links can’t unsubscribe anyone by accident. When they confirm:
  • every list they’re subscribed to changes to Unsubscribed
  • every email address on their contact changes to Suppressed, which campaigns skip
  • any signup-form confirmation still waiting for them is cancelled
  • their activity shows Unsubscribed from with the campaign’s name
For SMS, texting an opt-out keyword such as STOP changes that number to Opted Out on every contact in your organization that holds it. Campaigns stop sending to it, and you aren’t charged for skipped messages. The person opts back in by texting an opt-in keyword. See SMS overview. When someone joins a list through a signup form, Brudcast writes a consent record in the same step that subscribes them, so one never exists without the other. See Double opt-in and consent for what the record holds and how long its wording survives.

​
Re-subscribing someone

An unsubscribe is an instruction from the person, so it’s hard to undo by accident. The only way to make an unsubscribed address receive campaigns again is to update the email identity’s status through the API. Only do that when the person has asked to hear from you again, and keep a record of their request.

​
When a contact is deleted

Deleting a contact doesn’t lift the suppression on their address. Brudcast keeps the entry so the address stays blocked, but erases the address itself from it. The row then shows - in the Email Address column.

Bounces, complaints and suppression

How bounces and complaints are classified.

Create a form

Collect consent you can prove.

Platform API

Read and write suppressions from your own systems.