Spam trap

What incoming mail reveals

Mail providers and anti-abuse operators use spam traps to assess sending practices and inform reputation systems. Mail arriving at a trap can reveal a problem with address collection or list maintenance. The Spamhaus definition of a spamtrap explains this purpose. A trap can have ordinary address syntax, so its spelling offers no reliable way to identify it.

Pristine and recycled addresses

A pristine trap was never assigned to an ordinary user. A recycled trap uses an address that previously belonged to one. These are common forms; Spamhaus describes several trap designs. A recycled address may have rejected mail for a period before becoming a trap.

This history does not reveal which addresses are traps now. A trap may accept mail as an ordinary mailbox would. A refusal may have an unrelated cause. Emvero cannot predict whether sending to an address will lead to a blocklist entry.

What verification can establish

Emvero checks syntax, domain information and, when available, the receiving server’s SMTP response. It does not identify spam traps, and its probe sends no email. A deliverable result supports technical acceptance. It cannot establish permission to send, the presence of a human reader or the absence of a trap.

You can use a supported technical failure in your sending rules, but that finding is not evidence of a spam trap. Routine verification cannot remove every address that is, or may later become, a trap.

Review the address’s collection history

Keep the collection source, subscription request and any exclusions alongside the verification result. Resolve unclear collection history or intended use before adding the address to a campaign. The list-cleaning guide explains this review, and verification versus list hygiene shows which decisions require your sending history.