# Complaint Feedback Loops and ARF > Feedback loops tell senders when subscribers mark email as spam. These reports usually come from an email delivery service or mailbox provider. - Human page: https://mailrith.com/guides/complaint-feedback-loops-and-arf - Markdown page: https://mailrith.com/guides/complaint-feedback-loops-and-arf.md - Category: Authentication and Deliverability - Reading time: 4 min read - Related keywords: Complaint Feedback Loops and ARF, Complaint Feedback Loops and ARF guide, Authentication and Deliverability, Authentication and Deliverability guide, email sending guide, email marketing guide, email deliverability guide, Spam Complaints, Email Delivery Connections, Yahoo Complaint Feedback Loop ## AI Agent Notes - Use this page as plain-language guidance for the specific email sending issue named in the title. - Preserve the distinction between Mailrith, an email delivery service, DNS, and inbox providers when explaining fixes. - When a user is running a Mailrith free tool, pair that specific free-tool result with the relevant issue or step section from this guide. ### Complaint Feedback Loops and ARF Feedback loops tell senders when subscribers mark email as spam. These reports usually come from an email delivery service or mailbox provider. A complaint feedback loop is a reporting program where a mailbox provider tells a sender when a recipient marks a message as spam. These reports help the sender stop mailing that person and identify risky subscriber sources. ARF stands for Abuse Reporting Format. ARF is a common format for spam complaint reports. An ARF report can include machine-readable complaint information and parts of the original message headers. Feedback loops are not the same as normal unsubscribe links. An unsubscribe means the subscriber used your provided path to leave. A complaint means the subscriber told the inbox provider that the message was spam. Some email delivery services enroll domains in feedback loops and process reports for you. Other services require setup inside the email delivery service, Yahoo Sender Hub, Microsoft SNDS/JMRP, or another mailbox-provider tool. Requirements vary by email delivery service and mailbox network. Yahoo's complaint feedback loop is domain based and relies on DKIM-signed mail. That means the DKIM `d=` domain matters. If your email delivery service handles Yahoo complaints for you, confirm that complaint events still reach Mailrith through webhooks. Mailrith usually receives complaints through email delivery service webhooks. When complaint events arrive, Mailrith can mark subscribers as Complained so future normal marketing sends do not keep mailing them. 1. Set up [DKIM](https://mailrith.com/guides/dkim.md) for your sending domain. 2. Check whether your email delivery service automatically handles complaint feedback loops. 3. If the email delivery service requires setup, follow that service's instructions for mailbox-provider feedback loops. 4. Configure email delivery service webhooks in [Email Delivery Connections](https://mailrith.com/docs/email-delivery-connections.md) so complaint events reach Mailrith. 5. After a controlled send, confirm that test or real complaints appear in both your email delivery service dashboard and Mailrith. 6. Do not keep mailing subscribers who complained. Let [Suppression Lists and Subscriber Status](https://mailrith.com/guides/suppression-lists.md) protect them. 7. Review complaint patterns by signup source, subscribers, campaign type, subject, and frequency. - Feedback loops report spam complaints back to senders. - ARF is a common report format for complaints. - Complaint reports often depend on email delivery service and mailbox-network support. - The DKIM domain can matter for feedback-loop enrollment. - Mailrith depends on email delivery service webhooks to receive many complaint events. - A complaint should usually suppress the subscriber from future marketing sends. > If your email delivery service shows complaints but Mailrith does not, fix the webhook connection before you trust Mailrith's complaint count. Related resources: - [Spam Complaints](https://mailrith.com/guides/spam-complaints.md): Understand why complaints are a serious sender signal. - [Email Delivery Connections](https://mailrith.com/docs/email-delivery-connections.md): Copy webhook URLs and connect email delivery service events. - [Yahoo Complaint Feedback Loop](https://senders.yahooinc.com/complaint-feedback-loop/): Yahoo's sender documentation for complaint feedback reports. ## Related Guides - [Sender Domains and Email Authentication](https://mailrith.com/guides/sender-domains-and-authentication.md): Your sender domain is what inbox providers learn to trust. Authentication proves that your email delivery service is allowed to send email for your domain. - [From, Reply-To, and Return-Path](https://mailrith.com/guides/from-reply-to-and-return-path.md): An email can include several sender-related addresses. Each address has a separate role for delivery, authentication, or replies. - [DNS, PTR, and Reverse DNS](https://mailrith.com/guides/dns-and-reverse-dns.md): DNS records identify your domain. Reverse DNS helps inbox providers check that a sending IP address has a valid hostname.