Guides
Blocklist
Blocklist enforcement, automatic entries, and compliance.
Blocklist
The blocklist prevents emails from being sent to specific addresses or domains.
Automatic Blocklist Entries
Pipelime automatically adds entries to the blocklist when:
- An email bounces (hard bounce) — the email address is blocklisted
- A contact unsubscribes — the email address is blocklisted
- A complaint is received — the email address is blocklisted
Manual Blocklisting
Add entries manually:
# Block a specific email
Pipelime blocklist add --email spam-trap@example.com
# Block an entire domain
Pipelime blocklist add --domain competitor.comVia API:
curl -X POST https://app.Pipelime.io/api/blocklist \
-H "Authorization: Bearer ki_your_key" \
-H "Content-Type: application/json" \
-d '{"email": "spam-trap@example.com"}'Blocklist Enforcement
Before every email send, Pipelime checks the blocklist:
- Is the recipient's email address blocklisted?
- Is the recipient's domain blocklisted?
If either check matches, the send is skipped and the contact is marked as blocklisted in the campaign.
Removing from Blocklist
Blocklist entries can only be removed by organization admins:
Pipelime blocklist remove --email previously-blocked@example.comCompliance
CAN-SPAM
- Every email includes an unsubscribe link (auto-appended if not present)
- Unsubscribe requests are processed immediately
- Physical address is required before campaign activation
GDPR
- Contacts can request data export
- Contacts can request hard deletion of all data
- Blocklist entries are maintained even after contact deletion
