> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/spam-complaints/how-batch-collects-spam-complaints.md).
# How Batch Collects Spam Complaints?
Learn how Batch uses feedback loops from 20+ mailbox providers to automatically reduce recipient frustration, protect your sender reputation, and give you actionable insight into your sends.
Spam complaints are **one of the most important signals** a sender can receive, and they should be a top priority. They help you:
* Detect anomalies in your emails, such as a broken or missing unsubscribe link
* Identify the emails that frustrate your audience
* Spot when your marketing pressure is too high
* Prevent your sender reputation from degrading over time
This article explains how Batch collects spam complaints for the emails you send, and which mailbox providers are covered.
## Understanding Feedback Loops and ARF Reports
Some mailbox providers and anti-spam organizations, share spam complaint data with senders through a **feedback loop (FBL)**.
When a recipient marks one of your emails as spam, the mailbox provider emails a report to the sender in the standard Abuse Reporting Format (ARF). Each report includes information such as:
* The complainant's email address
* The date and time of the complaint
* Details about the message that triggered the complaint
Batch processes these reports to:
* **Display a spam complaint rate** for each campaign and automation
* **Unsubscribe complainants from marketing emails immediately**, so they stop receiving messages they don't want
* **Log each complaint as an event** you can export via the API, so you can analyze the context and understand why the user complained
## Supported Feedback Loops
Not all mailbox providers offer an FBL.
Senders must discover them and register with each one individually. Gmail, for example, does not send individual complaint reports. Instead, it provides aggregated spam rate data through Google Postmaster Tools (see [Google Postmaster Tools](/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/monitoring-and-third-party-tools/mastering-email-deliverability-with-google-postmaster-tools.md)).
At Batch, we are committed to reducing spam and helping senders improve their CRM programs with reliable data. That's why we are registered with most of the feedback loops available today:
* Microsoft and Yahoo FBLs
* [Validity Universal Feedback Loop](https://fbl.validity.com/)
* [Signal Spam feedback loop](https://www.signal-spam.fr/)
#### Supported mailbox providers
{% hint style="info" %}
The list below is not exhaustive.
{% endhint %}
{% tabs %}
{% tab title="Global Mailbox Providers" %}
* Microsoft (Hotmail, Outlook, Live, etc.)
* Yahoo (Yahoo, AOL, etc.)
{% endtab %}
{% tab title="Local Mailbox Providers" %}
**Europe**
* Telenet, Belgium (telenet.be, pandora.be)
* Seznam, Czech Republic (seznam.cz, email.cz, post.cz)
* Free, France (free.fr)
* La Poste, France (laposte.net)
* Orange, France (orange.fr, wanadoo.fr), only for recipients who have agreed to share reports with third parties from the Orange webmail.
* SFR, France (sfr.fr, neuf.fr, cegetel.net)
* Italia Online, Italy (libero.it, virgilio.it, inwind.it)
* Telecom Italia, Italy (tim.it, alice.it, tin.it)
* Ziggo, Netherlands (ziggo.nl, home.nl, casema.nl)
* Telenor, Norway (online.no, telenor.com)
* Swisscom, Switzerland (bluewin.ch, bluemail.ch)
* Virgin Media, UK (virginmedia.com, ntlworld.com, blueyonder.co.uk)
* Liberty Global, multiple countries (chello.at, upc.ch, unitymedia.de)
**North America**
* Comcast, US (comcast.net)
**Latin America**
* Terra, Brazil and Latin America (terra.com.br, terra.com)
* UOL, Brazil (uol.com.br, bol.com.br)
**Asia-Pacific**
* Telstra, Australia (bigpond.com, bigpond.net.au, telstra.com)
{% endtab %}
{% tab title="Specialized Mailbox Providers & Other" %}
* Signal Spam
* Fastmail (fastmail.com, fastmail.fm)
* Gandi (hosted email on custom domains)
* Rackspace (hosted email on custom domains)
* OpenSRS (hosted email on custom domains)
* Locaweb (hosted email on custom domains)
* BlueTie (hosted business email)
* SilverSky (secure hosted email, financial sector)
* Synacor (white-label webmail for ISPs and media companies)
{% endtab %}
{% endtabs %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://doc.batch.com/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/spam-complaints/how-batch-collects-spam-complaints.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
