A spam trap is an email address not actually used by a person, planted or reactivated by mailbox providers and blocklist operators specifically to catch senders whose lists are stale, scraped, or poorly maintained.
Two versions of a spam trap show up in practice. A pristine trap never belonged to a real person at all, it exists purely to be found by a sender with a bad sourcing process, since there's no legitimate way that address ended up on any real list. A recycled trap used to be a real inbox, abandoned long enough that the provider reclaims it and turns it into a trap instead of deleting it outright. Either way, hitting one isn't bad luck. It's close to a self-diagnosis: something about how the list got built or maintained let a fake or dead address through.
The immediate cost isn't just one bad send. The real damage shows up in blast radius: if a mailbox lands in a spam trap, sending capacity gets pulled while the team figures out what happened and fixes it, and every other address on that mailbox's send queue waits in the meantime. That's a big part of why teams run more mailboxes than raw volume math alone would suggest, spreading that risk thinner instead of concentrating it on one address.
The defense against spam traps is upstream of sending: source lists from verified, legitimate providers instead of scraping, re-verify addresses on a real cadence rather than once at import, and prune anything that's gone dark for a long stretch instead of leaving it in rotation on the theory it might still be alive.
People treat a spam trap hit as random misfortune, an unlucky address in an otherwise clean list. It's rarely random. A trap only gets hit because a list included an address that no legitimate sourcing or verification process should have produced in the first place, which makes the hit a symptom of the sourcing process, not the cause of a bad day.
Tell us how your motion runs today. We'll show you what we'd engineer.
Contact us