Email deliverability glossary: 40 terms every sender should know
Forty email deliverability terms defined in one or two sentences each: bounces, SPF, DKIM, DMARC, spam traps, greylisting, sender reputation, inbox placement and verification.
Spam traps are addresses that exist only to catch senders with bad lists. The three types, how they end up on your list, what verification can and cannot detect, and how to stay clear.
A spam trap is an email address that is not used by a real person and exists only to identify senders who mail addresses they should not have. Mailbox providers, blocklist operators and anti-spam vendors run them, and a single message to a trap can get a sending IP or domain blocklisted. You avoid them by never buying or scraping addresses, by removing contacts who have not engaged in 12 months, and by verifying lists so that recycled and typo traps are caught before a send.
Traps work because they can only receive mail sent without permission. Nobody signed up with a trap address, so any sender who mails one has harvested it, bought it, or kept it long after it stopped belonging to a person. The operator logs the sender and feeds the data into reputation systems and blocklists such as Spamhaus. One or two trap hits in a large send might only dent your reputation; repeated hits can block delivery to a whole provider.
| Type | How it is created | Who it catches | Can verification detect it? |
|---|---|---|---|
| Pristine | A brand new address published only where scrapers look, never used by anyone | Senders who scrape or buy harvested lists | No. It is a real, working mailbox |
| Recycled | An abandoned address that bounced for a year or more, then reactivated as a trap | Senders who keep old, unengaged contacts | Partly. The dead period is visible, the reactivation is not |
| Typo | Domains such as gmial.com or hotmal.com registered by trap operators | Senders who do not validate at the form | Yes. The domain is known and the address is flagged |
A pristine (or pure) trap has never belonged to a person. The operator creates it and seeds it where only automated harvesters look: hidden in page source, forum signatures, public comment fields. Any mail it receives was sent to a scraped or purchased list, which is why pristine traps are the most damaging: they mean this sender is mailing addresses they were never given.
A recycled trap starts life as a real mailbox. The user abandons it, the provider closes it, and for 12 months or more every message to it hard bounces with 550 5.1.1. Then the provider quietly reopens the address as a trap. Senders still mailing it through a year of bounces, or importing an old list unchecked, land in it. Recycled traps catch list hygiene problems rather than theft, and they are the type most legitimate marketers hit.
Trap operators register domains one keystroke away from the big providers and point their mail servers at a trap. An address like j.smith@gmial.com was never deliverable, but it looks fine in a CSV, and a sender who never validated the form keeps mailing it. Our email typo fixer catches these at the form by suggesting the intended domain.
The common thread is time and consent. Addresses given to you directly and mailed regularly almost never become traps: a recycled trap requires a bounce period you would have noticed, and a pristine trap was never given to anyone. The decay side is covered in email list decay.
You cannot see a trap directly: operators never publish them. But the addresses that turn into traps share a profile, and you can screen for it.
Honesty matters here because some vendors claim to "remove spam traps", and that is not quite true.
Verification can:
Verification cannot:
So verification is one layer. It removes typo traps and dead weight, but the only protection against pristine traps is never to acquire addresses you were not given.
One hit to a recycled trap usually means a reputation dip and more mail in spam for a while. Repeated hits, or any hit to a pristine trap, can get your IP or domain blocklisted until you show the list has been cleaned.
No. Operators never publish them, because a published trap stops working. Anyone selling a "spam trap list" is selling guesses.
It removes typo traps and the invalid, role and dead addresses that accompany them. It cannot detect pristine traps, which are deliverable by design.
Related reading
@Forty email deliverability terms defined in one or two sentences each: bounces, SPF, DKIM, DMARC, spam traps, greylisting, sender reputation, inbox placement and verification.
@Real-time email validation checks an address as it is typed: syntax, typos, disposable domains, role accounts, MX and an optional mailbox check. Here is how it works.
@Gmail, Outlook and Yahoo addresses carry no company signal, so B2B teams segment them. When free addresses are legitimate, how the free and role flags route them, and bulk detection.
Photos: Freepik