molted suppressions

molted suppressions add --email alice@example.com \
  --reason hard_bounce --scope tenant
# → all future sends from your tenant to alice@example.com will be blocked

molted suppressions add --email bob@example.com \
  --reason manual_dnc --scope campaign --campaign-id camp_123
# → recorded against camp_123, but currently blocks every send to
#   bob@example.com from your tenant, the same as --scope tenant (#1932);
#   real per-campaign scoping (blocked only for this campaign) is #1984

# With expiration (stops blocking after that date; the row stays listed):
molted suppressions add --email temp@example.com \
  --reason no_engagement --scope tenant --expires-at 2027-01-01T00:00:00Z

molted suppressions check --email alice@example.com
molted suppressions check --domain competitor.com
# → { "suppressed": true, "reason": "manual_dnc", "matchedOn": "domain" }
# Note: a campaign-scoped row reports suppressed here too (#1932), matching
# a real send -- it blocks every send to that address from your tenant,
# not just the campaign it names, until real per-campaign scoping (#1984).

molted suppressions list --email alice@example.com
molted suppressions list --limit 50 --offset 100   # page through every row
molted suppressions remove <id>     # removes one row
# Removing loosens a compliance control, so it is human-gated: once the
# workspace enforces the human gate an agent key gets 403
# human_decision_required with a decisionUrl (same for remove-domain).
# It also needs an admin or all-mailbox key (list and list-domains too:
# a mailbox-scoped key gets 403 mailbox_scope_denied; check stays open).
# An address can have more than one row (tenant scope plus one or more
# campaign-scoped rows, all enforced the same way, #1932): removing this
# id does not mean the contact can receive email again if another row for
# it still exists. List every row for the address, remove each one, then
# confirm with suppressions check before sending.

molted suppressions add-domain --domain spam.co
molted suppressions list-domains
molted suppressions remove-domain spam.co

molted suppressions import --file bounces.csv
# CSV header: email,scope,reasonCode,campaignId,source,expiresAt
# (case-insensitive; "recipientEmail" also accepted for "email";
# campaignId, source, expiresAt are optional columns)

molted suppressions import --file bounces.json
# JSON array: [{"email":"a@x.com","scope":"tenant","reasonCode":"hard_bounce"}, ...]

molted suppressions import --file bounces.csv --dry-run     # validate only, send nothing
# exits 1 if any row is invalid and a real run would fail closed (no --skip-invalid);
# exits 0 if every row is valid, or --skip-invalid is also given (a real run would succeed either way)
molted suppressions import --file bounces.csv --skip-invalid # send the valid rows, report the rest

molted suppressions add [options]

molted suppressions list [options]

molted suppressions check [options]

molted suppressions check --email bob@example.com
# → { "email": "bob@example.com", "suppressed": true, "reason": "manual_dnc", "matchedOn": "domain" }

molted suppressions check --domain competitor.com
# → { "domain": "competitor.com", "suppressed": false, "reason": null, "matchedOn": null }

molted suppressions remove <id>

molted suppressions add-domain [options]

molted suppressions list-domains [options]

molted suppressions remove-domain <domain>

molted suppressions import [options]