How a feedback loop works

A sender enrolls with a mailbox provider’s FBL program, proving control of a sending domain or IP range and naming an address to receive reports. When a recipient at that provider clicks “Report spam” or “Junk” on a message that matches the enrollment, the provider sends a report to that address.

Most per-complaint FBLs use the Abuse Reporting Format (ARF) defined in RFC 5965. An ARF report is a multipart/report message with report-type=feedback-report, containing:

  1. A short human-readable summary.
  2. A machine-readable message/feedback-report part with fields such as Feedback-Type: abuse, the reporting provider, and the arrival date.
  3. A copy of the original message or its headers, which lets the sender match the complaint to a campaign and recipient.

Providers often redact the recipient’s address to protect privacy, so senders typically embed their own identifier, such as a subscriber ID in a custom header or the List-Unsubscribe URL, to map a complaint back to a contact.

How major providers differ

  • Yahoo runs a DKIM-based Complaint Feedback Loop. You enroll a DKIM signing domain, and when a recipient marks a message signed by that domain as spam, Yahoo sends an ARF report so you can suppress the recipient.
  • Microsoft runs the Junk Mail Reporting Program (JMRP) for Outlook.com and Hotmail, enrolled by IP alongside its SNDS reputation data.
  • Gmail does not send per-complaint reports. Its feedback loop, aimed at high-volume senders and ESPs, uses a Feedback-ID header (in the form a:b:c:SenderId) on DKIM-signed mail and shows aggregate complaint rates for those identifiers in Postmaster Tools when a campaign draws an unusual rate of spam reports.

Why it matters

Complaints are one of the strongest negative signals in sender reputation. Google asks senders to keep user-reported spam below 0.1% and never reach 0.3%, and Yahoo also uses 0.3% as its ceiling. Every additional message to someone who already complained raises the chance of another complaint, so continuing to mail complainers compounds damage quickly. Sustained high complaint rates can lead to spam-folder placement, throttling, and contributions to blocklist listings.

FBL data is also diagnostic. A spike in complaints tied to one campaign, list segment, or acquisition source tells you exactly where the problem is.

How to handle FBL reports

RFC 6449, written by MAAWG (now M3AAWG), sets out practical recommendations for senders that receive complaint reports:

  1. Treat a complaint like an unsubscribe. Suppress the address from marketing mail automatically and promptly.
  2. Scope suppression sensibly. Suppress across your own related lists, but an ESP should not necessarily block the address for every customer on its platform.
  3. Use a dedicated reporting address for each FBL so you can tell which provider sent each report, and route program notices to a team alias rather than one person’s inbox.
  4. Find the cause. Group complaints by campaign, segment, and signup source to see what is driving them.
  5. Measure the rate correctly. Compare complaints with delivered mail over the same period.

Complaint rate vs. unsubscribe rate

These measure different behavior. Unsubscribes come from people using the opt-out you provide. Complaints come from people who found “Report spam” easier, often because the unsubscribe link was hidden, slow, or ignored a previous request. A high complaint-to-unsubscribe ratio points to friction in your opt-out flow. One-click unsubscribe headers (RFC 8058), now required by Gmail and Yahoo for bulk marketing mail, reduce that friction because the mailbox interface shows an unsubscribe button next to the spam button.

Where RocketVerifier helps

Complaints often come from contacts who never meant to subscribe, such as mistyped addresses, throwaway signups, and stale imported data. RocketShield checks addresses on signup forms in real time, and bulk email verification flags risky, disposable, and do-not-mail addresses before a campaign, so fewer of your messages reach people likely to complain.