Backscatter (email)
What is Backscatter (email)?
Backscatter is the bounce traffic a mail server generates when it accepts a message and only later finds it can't be delivered, sending the bounce to whatever forged address the message claimed as sender -- landing in an innocent party's inbox. AdminKit's guide to email bounces covers spotting it.
By AdminKit team, Netbase JSC · Updated
Backscatter is the unwanted bounce or auto-reply traffic a mail server generates when it accepts a message and only later discovers, after the original sender’s connection has already closed, that the message can’t actually be delivered — so it sends the bounce notification to whatever address the message claimed as its sender. When that claimed sender address was forged, which is common with spam and phishing sent under a spoofed-from address, the bounce lands in an innocent third party’s inbox who never sent the original message at all. The Postfix Backscatter Howto describes the same effect from the victim’s side — when a spammer or worm forges sender addresses, innocent sites are flooded with undeliverable-mail notifications — and shows how to filter them. A domain can receive a flood of backscatter if spammers happen to forge it as the sender on messages that later bounce elsewhere, and receiving servers increasingly treat unsolicited bounce traffic itself as a spam signal, the pattern M3AAWG’s abuse-desk guidance documents. VERP takes the opposite, deliberate approach to the envelope sender address — encoding the original recipient into it on purpose, for a legitimate bulk sender to match a bounce back to the exact subscriber that caused it, rather than a forged address an attacker chose. Validating the recipient during the SMTP (also tracked on the IETF Datatracker) conversation, before accepting the message, is what avoids generating backscatter in the first place — the same principle RFC 3834’s guidance on automatic email responses warns against skipping. A domain running a catch-all address is especially exposed to this, since it accepts mail to any address instead of rejecting an unknown recipient outright.
AdminKit groups backscatter (email) under its email authentication cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
Why does backscatter land in an innocent person's inbox?
Because the receiving server accepts a message and only later discovers it can't be delivered, by which point it sends the bounce to whatever sender address the message claimed -- if that address was forged, as is common with spam and phishing, the bounce lands with whoever was spoofed, not the real sender.
What makes a domain especially exposed to backscatter?
Running a catch-all address -- since it accepts mail to any address instead of rejecting an unknown recipient outright, it ends up generating or routing more undeliverable mail that turns into backscatter.
How does VERP relate to backscatter?
VERP takes the opposite, deliberate approach to the envelope sender address, encoding the original recipient into it on purpose so a legitimate bulk sender can match a bounce back to the exact subscriber that caused it, rather than a forged address an attacker chose.
What's the actual fix for generating backscatter?
Validating the recipient during the SMTP conversation itself, before accepting the message -- the same principle RFC 3834's guidance on automatic email responses warns against skipping.