How do ISPs report spam complaints differently from bounces?

Bounces and spam complaints both tell you something went wrong, but they travel back to you through completely different pipelines. Confusing them leads to fixing the wrong thing.

How bounces are reported

Bounces happen at the SMTP level, in real time. When a receiving server rejects your message (invalid address, full mailbox, policy block), it sends back a response code and a reason immediately. Your ESP catches this during the send and logs it as a hard or soft bounce. You see it within minutes.

How spam complaints are reported

Spam complaints travel through a completely separate system called a Feedback Loop (FBL). When a recipient hits "This is spam," the mailbox provider sends a complaint notification to your ESP through the FBL. This happens asynchronously, often hours after the original send, and only if the provider runs an FBL at all.

Not every mailbox provider does. Gmail, notably, doesn't send individual FBL complaints. They aggregate complaint data in Google Postmaster Tools instead. You won't get per-message complaint alerts from Gmail. Yahoo and Outlook both operate FBLs for qualified senders. Your ESP handles FBL registration, not you.

Why the distinction matters

Bounces tell you your list has bad addresses. Complaints tell you your list has people who don't want your mail. Both hurt sender reputation, but the fixes are different.

High bounces call for list cleaning: removing invalid and stale addresses. High complaints call for rethinking your permission model, frequency, or content relevance. If you treat complaint problems as bounce problems (or vice versa), you'll clean the wrong thing and the issue persists.

If your complaint rate is climbing and you can't figure out the source, the SOS hotline is free.