Email Feedback Loops Explained: Yahoo CFL, Microsoft JMRP and Gmail's FBL

An email feedback loop is a mailbox provider telling you, the sender, that one of its users marked your message as spam. Three providers matter most, and they work in three different ways. Yahoo's Complaint Feedback Loop (CFL) sends a report per complaint for mail signed with a DKIM domain you've enrolled. Microsoft's Junk Mail Reporting Program (JMRP) reports junk clicks for IP addresses you are responsible for. Gmail's Feedback Loop (FBL) never names a complainer; it shows spam rates per campaign identifier in Postmaster Tools. Knowing which ones you can use, and acting on what they tell you, is one of the cheapest ways to protect a sending domain.

The three loops side by side

	Yahoo CFL	Microsoft JMRP	Gmail FBL
Keyed to	Your DKIM domain	IP addresses you're responsible for	A Feedback-ID identifier in your headers
Sign-up	Yahoo sender hub: add and verify the domain, then enrol	SNDS, with a Microsoft account; request access to your IPs	Verify the DKIM domain in Postmaster Tools; add the header
Needs DKIM	Yes, only DKIM-signed mail is supported	Not stated by Microsoft	Yes, signed by a domain you own or control
What you get	A report per complaint, in ARF format	Reports when users junk your messages	Spam rates per identifier; no individual users
Where	Sent to the address you enrol	Through SNDS	Postmaster Tools FBL dashboard
Covers	Yahoo users	Microsoft's consumer mail (Outlook.com)	@gmail.com recipients only

Sources, all read 2 November 2026: Yahoo's Complaint Feedback Loop page and best practices; Microsoft's SNDS page (updated 22 September 2026); Google's Feedback Loop help page.

Yahoo's Complaint Feedback Loop

Yahoo's page is direct about what the CFL is for: "Once enrolled, you'll receive a report when recipients mark your emails as Spam." It is domain-based, and "The Complaint Feedback Loop program only supports DKIM-signed email." Reports use the Abuse Reporting Format (ARF), a standard format that mail software can parse automatically.

Yahoo treats it as part of normal sending. Its best practices page says "An active CFL is needed for all DKIM domains to make sure you're processing complaints quickly", and tells bulk senders to "Use the CFL to monitor your complaint rate, and ensure you are remaining below 0.3%."

How to enrol, in outline:

1. Create a sender profile on Yahoo's sender hub.
2. Add your domain and verify that you control it.
3. Enrol the domain in the CFL and give the address that should receive reports.
4. Make sure all your mail is DKIM-signed with that domain. Check it with the DKIM checker.

The key word is your DKIM domain. If a platform signs your mail with its own domain, the complaints go to that platform's CFL, not yours. Our Google Workspace DKIM and Microsoft 365 DKIM guides show how to sign with your own domain.

Microsoft's Junk Mail Reporting Program

Microsoft's SNDS page describes SNDS as including "our Junk Email Reporting Program, which lets you receive reports when users junk your messages." Access works through SNDS: you sign in with a Microsoft account and request access to the IP addresses you are responsible for.

That makes JMRP an IP-based program. It fits senders who run their own mail servers or have dedicated IPs. If your mail goes out through a sending platform's shared IPs, or through Microsoft 365 or Google Workspace mailboxes, those IPs belong to someone else, and they are the ones who can enrol them.

SNDS itself, which shows the reputation colours and trap hits for an IP, is the other half of the same programme. If you do control your IPs, set up both.

Gmail's Feedback Loop

Gmail's version is built differently. Google says it helps senders "identify campaigns in your traffic that are getting a high volume of complaints from Gmail users", and is "particularly useful to email service providers to detect abuse of their services."

You add a header to every message:

Feedback-ID: a:b:c:SenderId

SenderId is required: a "Mandatory unique Identifier (5–15 characters) chosen by the sender" that stays the same across your mail. a, b and c are optional, for things like a campaign ID, a customer ID or a mail type. Google reports spam rates for the identifiers that get enough volume and complaints in the Postmaster Tools FBL dashboard.

The requirements, per Google's page:

• Mail must be DKIM-signed by a domain you own or control, and that domain must be verified in Postmaster Tools.
• Sending IPs must be in the SPF records of your signing domains and have PTR records that resolve to a valid host name.
• "FBL data will only pertain to @gmail.com recipients."

Google doesn't say how much volume is needed, only that data appears for identifiers seen in "a certain volume of mails" with distinct user spam reports. And it never names individual recipients. For Gmail, the only per-person signal is the unsubscribe, which is one reason one-click unsubscribe matters.

The spam rate for the whole domain is in the main Postmaster Tools dashboards; our Postmaster Tools guide covers them.

Which loops can you actually use?

How you send	Yahoo CFL	Microsoft JMRP	Gmail FBL
An ESP or newsletter platform	Usually run by the platform; check whether it signs with your domain	Run by the platform	Run by the platform
Your own mail server on your own IPs	Yes	Yes	Yes
Cold email through Google Workspace or Microsoft 365 inboxes	Yes, if mail is DKIM-signed with your domain	No: the IPs are Google's or Microsoft's	Technically possible, but cold volume to @gmail.com rarely produces data
A cold email platform's own sending infrastructure	Depends on the DKIM domain	Run by the platform	Run by the platform

For most cold senders, then, the useful set is: the Yahoo CFL on each sending domain, Postmaster Tools for Gmail spam rates if volume allows, and your own reply and unsubscribe handling. Anyone who replies "remove me", "stop" or "not interested" is a complaint you got before the spam button.

What to do with the reports

1. Suppress every complainer at once

Add them to a suppression list that every tool and every sending domain respects. A person who complained about one domain will complain about the next. If your suppression lists live in several tools, the suppression list merger combines them. Our cold email suppression list guide covers how to run one.

2. Watch the rate, not just the count

Gmail's and Yahoo's guidance both use 0.3% as the line for bulk senders. Google adds a target to stay below 0.10%. The spam complaint rate calculator turns your numbers into a rate. Yahoo says its spam rate "is calculated in our system based on mail delivered to the inbox", so a small, engaged list and a big, cold one can produce very different rates from the same number of complaints.

3. Look for the cluster

Complaints rarely spread evenly. Look at which campaign, list source, segment or sequence step they came from. A cluster on one source usually means poorly matched targeting or an old list. A cluster on one step usually means the sequence went on too long.

4. Fix the list before the next send

People who never asked to hear from you are the main source of complaints, and old, unverified lists carry addresses that have become spam traps. Neither shows up in a feedback loop until the damage is done.

Where SimpleVerifier fits

A feedback loop tells you about complaints after they happen. Verification works on the other side: SimpleVerifier runs a live mailbox check on each address and returns safe to send, send with care, check again later or do not send, with the reason, so bounces and dead addresses don't add to the signals providers already count against you. Catch-alls stay risky, never guessed valid.

The first 100 checks are free with a Google sign-in on the verify page. Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off. See pricing.