A spam trap is not a grouchy subscriber. It is an address monitored by a blocklist operator or a mailbox provider. Mail to that address is evidence you do not have permission, or that you ignore hygiene. Hitting traps is one of the fastest ways to turn a normal sending domain into a listed one.
Pristine vs recycled traps
Pristine traps were never used by a human. They exist to catch list appends, scrapes, and purchased files. Recycled traps used to belong to someone and were later converted after a long quiet period. The first type punishes data you never should have had. The second punishes mailing ancient files you never sunset.
You cannot tell them apart from the SMTP conversation. You only see the aftermath: listings, a sudden junk placement, or a partner who names trap hits in a ticket.
How senders step on them
- Buying or appending emails because a vendor promised “verified” data.
- Scraping contact pages, WHOIS, and GitHub profiles.
- Never removing hard bounces, so directory-style retries keep going.
- Reactivating a five-year-old export “just this once” after a tool migration.
How to stay off them
Collect addresses yourself, confirm them, and remove persistent failures. Do not send to the full historical database because a new ESP made import easy. Confirm-at-capture beats cleaning-after-the-blast.
For B2B, a business card is not a license to newsletter someone until they quit the industry. Use a first-touch that is easy to refuse, then require a clear opt-in for recurring mail.
If you already hit traps
Stop the campaign. Do not “warm through it”. Identify which list, which form, which vendor, or which year of export those recipients came from. Purge that source. Recheck authentication so you are not compounding a content problem with an alignment problem. Then resume only on recently confirmed, engaged mail, at lower volume.
If a blocklist listing names you, follow their published removal process after the source is gone. Asking for delisting while the same file is still in production is how you stay listed.
Vendors who “verify”
A verification API can tell you an MX exists and a mailbox might accept mail. It cannot tell you the person asked to hear from you. It cannot tell you the address is not a recycled trap. Use verification to drop syntax junk and obvious dead domains. Do not use it as a moral license to buy a file.
If a vendor will not explain how they got the names, you already know. Walk away. The cost of a listing is higher than the cost of building the list yourself.
