Feedback LoopFeedback Loop (FBL)

Definition

A feedback loop (FBL), also called a complaint feedback loop, is a service from a mailbox provider that tells a sender when its recipients mark a message as spam. When someone hits “Report Spam,” a registered sender receives a copy of the complaint so it can suppress that recipient at once. It is how you find out about complaints you would otherwise never see, and acting on it is essential to protecting your reputation.

  • Reports back which recipients marked your mail as spam
  • You must register with each provider to receive its reports
  • Most reports arrive in the standard ARF format (RFC 5965)
  • Gmail gives only aggregate complaint rates, not individual complainers
At a glance
Also called Complaint feedback loop (CFL)
Reports Recipients who hit “Report Spam”
Format ARF (RFC 5965) for most providers
Yahoo CFL, requires DKIM signing
Microsoft JMRP (set up via SNDS)
Gmail Aggregate rates only (Postmaster Tools)

How a feedback loop works

When a recipient clicks “Report Spam,” “Junk,” or the equivalent button, their mailbox provider records a spam complaint against the sender. Without a feedback loop, that complaint is invisible to you; it quietly damages your reputation while you keep mailing the person who reported you. A feedback loop closes that gap: a sender who has registered with the provider receives a copy of each complaint, typically by email.

The point of the loop is action. The moment a complaint comes in, you should add that recipient to your suppression list and stop mailing them, because continuing to send to someone who has already reported you is the fastest way to rack up more complaints and sink your reputation. A working FBL turns invisible damage into a list you can act on.

The ARF format

Most feedback loops deliver complaints in the Abuse Reporting Format (ARF), standardised in RFC 5965. An ARF report is a structured email with three parts: a human-readable summary, a machine-readable section with the complaint details, and a copy of the original message (or at least its headers) so you can identify the recipient and campaign.

The machine-readable part of an ARF complaint report
Content-Type: message/feedback-report

Feedback-Type: abuse
User-Agent: SomeProvider-FBL/1.0
Version: 1
Original-Mail-From: bounce@example.com
Original-Rcpt-To: reporter@mailbox.example
Arrival-Date: Wed, 10 Jun 2026 09:14:00 +0000

How the providers differ

Each major mailbox provider runs its feedback program a little differently, and the differences matter:

  • Yahoo (CFL). Yahoo’s Complaint Feedback Loop sends individual complaints in ARF. You apply for it, and because Yahoo keys the loop on your DKIM signature, your mail must be DKIM-signed to enrol.
  • Microsoft (JMRP). The Junk Mail Reporting Program forwards a copy of each message a user marks as junk. You configure it through Microsoft’s SNDS portal, registering the sending IPs you want covered.
  • Gmail. Google does not provide a traditional per-complaint FBL for most senders. Instead, Postmaster Tools reports an aggregate spam rate, with no individual complainer data, to protect user privacy. A separate Gmail FBL for ESPs reports per-campaign rates, again in aggregate.

The practical upshot: with Yahoo and Microsoft you can identify and suppress the exact people who complained, while with Gmail you can only watch the overall rate and react to trends. Google asks bulk senders to keep that rate under 0.3% in Postmaster Tools.

How a complaint travels through a feedback loop

A recipient hits “Report Spam” on your message
Their mailbox provider records the complaint
Has the sender registered for the provider’s FBL?
Yahoo / Microsoft: individual ARF report Gmail: aggregate rate only Not registered: nothing sent back
You receive the report and suppress the recipient
Acting fast protects your reputation

Feedback loops by provider

Yahoo (CFL) Microsoft (JMRP) Gmail
Report type Individual Individual Aggregate rate
Format ARF ARF Postmaster Tools
Identifies complainers Yes Yes No
Keyed on DKIM domain Sending IP (via SNDS) Domain / IP
Sign-up CFL application SNDS then JMRP Postmaster Tools

By the numbers

0.3%
The spam-complaint rate Google asks bulk senders to stay under in Postmaster Tools.
RFC 5965
The standard that defines the Abuse Reporting Format used by most feedback loops.
3
Major programs to register for: Yahoo CFL, Microsoft JMRP, and Google Postmaster Tools.

Common mistakes

Receiving complaints but not acting
An FBL is only useful if you suppress complainers immediately. Letting ARF reports pile up unprocessed means you keep mailing people who already reported you, which compounds the damage.
Skipping registration
Feedback loops are opt-in per provider. If you never enrol in Yahoo’s CFL or Microsoft’s JMRP, those complaints stay invisible while still hurting your reputation.
Expecting individual data from Gmail
Gmail does not name individual complainers; it reports an aggregate spam rate in Postmaster Tools. Plan to watch the trend rather than suppress specific Gmail reporters.
Not DKIM-signing for Yahoo
Yahoo keys its CFL on your DKIM signature, so unsigned mail cannot enrol. Sign with your own domain before applying.

Frequently asked questions

What is a feedback loop in email?
It is a service from a mailbox provider that tells a registered sender when one of its recipients marks a message as spam. The provider forwards a copy of the complaint, usually in the standard ARF format, so the sender can suppress that recipient straight away and avoid further complaints. It is the main way senders learn about spam complaints they would otherwise never see.
How do I set up a feedback loop?
Register separately with each provider. Apply to Yahoo’s Complaint Feedback Loop (your mail must be DKIM-signed), set up Microsoft’s JMRP through its SNDS portal for your sending IPs, and enrol in Google Postmaster Tools for Gmail’s aggregate reporting. Then point each loop at an address your team monitors and suppress complainers automatically.
Does Gmail have a feedback loop?
Not a traditional one for most senders. Rather than naming individual complainers, Gmail exposes an aggregate spam rate through Postmaster Tools, and runs a separate aggregate FBL for some ESPs, to protect user privacy. You can track your complaint trend and Google asks bulk senders to keep it under 0.3%, but you cannot suppress specific Gmail reporters the way Yahoo and Microsoft allow.
Reviewed by Jennifer Jackson, Email Deliverability Analyst · June 2026 ← Back to glossary