A suppression is an address Deloosh will not mail because it bounced, complained, unsubscribed, or otherwise needs protecting from you. A send to a suppressed recipient is denied with the suppression code — and some suppressions can never be undone from inside the product, on purpose.
Where suppressions come from
Three kinds of event put someone on the list:
- They said no. An unsubscribe link click, a one-click unsubscribe from the mailbox header, or a preferences-page toggle.
- The mailbox said no. A hard bounce — the address is broken or does not exist.
- They reported you. A spam complaint fed back from the mailbox provider.
An operator or the address’s owner can also request a manual block.
Sticky versus reversible — the distinction that matters
This is the part people get wrong, so Deloosh is deliberate about it.
Reversible (consent) suppressions come from a person exercising a choice: an unsubscribe link, a one-click unsubscribe header, a preferences-page opt-out. If that same person genuinely opts in again, the suppression lifts. They changed their mind; the product respects that in both directions.
Sticky suppressions survive a re-opt-in. These are spam complaints, hard bounces, and manual blocks. Re-opting in does not clear them, and you cannot remove them yourself — clearing one takes an administrator.
The reasoning is that these are not preferences. A spam complaint is a mailbox provider telling you that mailing this person damages your reputation; a hard bounce is a dead mailbox that will keep bouncing. A form submission cannot repeal either fact — and if it could, the easiest way to defeat your own suppression list would be to put a checkbox in front of it.
How the rules differ by send type
- Marketing sends are blocked by any consent-class or deliverability-class suppression. The denial reads: “marketing-suppressed: {recipient} ({sources})”.
- Cold outreach is stricter. Any suppression row blocks it, and so does any prior contact at all — Deloosh will not have a stranger’s first impression of you be the third email they never asked for. You will see either “cold-outreach: {recipient} has suppression rows {sources}” or “cold-outreach hygiene: {recipient} already contacted by this tenant”.
- Sticky suppressions block everything, regardless of send type.
Where to see them
- The Suppressions count in a send plan is the total number of suppression rows in your workspace. It provides context; it is not the number excluded from that audience. See SEND-11, Reading a send plan.
- A recipient dossier shows an amber
suppressed:line naming the exact sources for one person. See SEND-14, Recipient dossiers.
Why this protects you
Suppressions prevent sends to recipients who opted out or produced a deliverability-class event. Respecting those records reduces complaint and bounce risk and protects the rest of the audience. See SEND-16, The sending-health light.
Approving a send does not override it. See SEND-1, Nothing sends without your approval.