How does Backscatter work?
Rejecting in the SMTP conversation puts the error on the connecting server, which knows who really sent the message. Accepting and bouncing later sends the error to whatever sender address the spammer typed. Backscatter damages the reputation of the server that sends it.
Avoiding it means making every decision you can before answering the final 250: whether the recipient exists, whether the message is spam or carries a virus, whether it fails the sender domain's DMARC reject policy.
How does nofeb use Backscatter?
- nofeb's MX checks each recipient when it is named and refuses unknown ones immediately. It verifies SPF, DKIM, ARC and DMARC and scans for spam and viruses before it answers, refusing what it will not deliver, so it never sends a bounce for mail it accepted.
- Mail it accepts but considers likely spam goes to Junk rather than being bounced.
Frequently asked questions
How do I stop my server causing backscatter?
Reject during the SMTP transaction: verify recipients at RCPT and run content checks before acknowledging DATA. Never accept and bounce later.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| Inbound mail server that checks mail at the door | nofeb's own MX receives mail for the shared domain and your custom domains, with STARTTLS. It checks every recipient before accepting any data, verifies SPF, DKIM, ARC and DMARC, and scans for spam and viruses before it answers. Mail that fails a DMARC reject policy, carries a virus or is clearly spam is refused during delivery instead of bounced later; likely spam and DMARC-quarantined mail is filed into Junk. Every message carries a security verdict with its authentication, spam, virus and TLS results. | Shipped |