What’s the actual difference between Feedback-ID and List-Unsubscribe headers?

You click “Unsubscribe” on an email, and it works. But behind the scenes, that one-click action doesn’t just remove you from a list — it’s part of a larger system designed to track sender behavior and protect inboxes.

Feedback-ID and List-Unsubscribe headers do not do the same thing. Confusing them is like equipping a car with a steering wheel but no brakes — both are essential, but they serve entirely different roles in email delivery.

Understanding this distinction isn’t just technical trivia. It’s the difference between keeping your emails in inboxes and triggering automatic spam complaints or blocklists.

Key takeaways

  • List-Unsubscribe is a user-facing opt-out mechanism; it must point to a working unsubscribe URL or form.
  • Feedback-ID is a system-facing header that enables senders to receive automated reports on spam complaints, blocks, and delivery issues.
  • Mixing up their roles leads to invalid feedback loops, broken unsubscribe paths, and degraded sender reputation.

Why do Gmail and other inboxes require both Feedback-ID and List-Unsubscribe headers?

You need both Feedback-ID and List-Unsubscribe headers because Gmail uses them together to validate sender legitimacy and improve user trust. List-Unsubscribe is mandatory for all marketing and transactional emails starting January 2024, directly enabling user opt-out. Feedback-ID isn't required, but Gmail strongly encourages it for high-volume senders to help track feedback loops and protect sender reputation. Without either header properly implemented, your messages risk stronger filtering or lower inbox placement, especially on Gmail’s systems.

The role of List-Unsubscribe: mandatory by Gmail

Starting January 2024, Gmail requires the List-Unsubscribe header for every marketing and transactional email. It’s not optional — even if you’re sending only one email a week. This header gives users a one-click way to unsubscribe, reducing spam complaints and helping Gmail identify valid senders. If you're sending to a large list, skipping this header means you’re likely violating current best practices and may face delivery penalties.

Why Feedback-ID matters — even if it's not required

Feedback-ID isn’t enforced by Gmail, but it’s a key part of the feedback loop system. When users mark your email as spam, Gmail can use the Feedback-ID to send that report back to you — helping you detect and fix problematic lists or content before they damage your sender reputation. High-volume senders benefit the most from this transparency. According to RFC 7889, which defines feedback handling, proper implementation helps maintain ecosystem trust.

If you’re sending at scale, skipping Feedback-ID means you’re flying blind on spam complaints. Even a small spike in complaints can impact deliverability. You can test whether your headers are correctly set using tools like inbox placement tests, which simulate real-world filters across Gmail, Outlook, and others.

Risk of skipping either header

Without correctly formatted List-Unsubscribe, Gmail may deprioritize your emails or move them to spam. Without Feedback-ID, you won’t know if your messages are triggering user complaints — making reputation management harder. Both headers together form a foundation of accountability.

Let’s be clear: Gmail isn’t asking for perfection, but for compliance. Your email quality matters. A small investment in header validation — like testing your list with bulk verification or checking individual addresses with the real-time API — can prevent bigger delivery issues down the line.

What does List-Unsubscribe do—and how does it work?

The List-Unsubscribe header tells email clients: "This message includes an unsubscribe link." When someone clicks it, the client sends a request to your specified endpoint. You must process it within 10 business days and remove the user. Properly implemented, this reduces spam complaints and shows ISPs you respect user choice. It’s a core part of maintaining sender reputation and inbox placement.

How the List-Unsubscribe header works in practice

  1. Include the header in your email. Add the List-Unsubscribe header with a URL pointing to your unsubscribe endpoint, like List-Unsubscribe: https://example.com/unsubscribe?email=placeholder. This signals to email clients that the message includes an unsubscribe option. Without it, clients won’t show the link.
  2. Ensure the endpoint handles requests securely. When a click occurs, the client sends a GET request to your endpoint with the user's email address. Your server must validate the request (e.g., check for tampering, confirm the email matches your records) and process the unsubscribe. A poorly secured endpoint risks abuse or data leaks.
  3. Remove the user in 10 business days. The RFC 8058 standard specifies this maximum. You don’t need to act instantly, but delays beyond 10 business days may be viewed as disregarding user intent—ISP signals can treat that as a red flag.
  4. Confirm the change. Return a response that clearly indicates the user has been unsubscribed. Though no strict format exists, a 204 or 200 with a confirmation message helps prevent confusion and client retries.

Why it matters for deliverability

Spam complaints are the #1 driver of email blocklists. A working List-Unsubscribe header lets users exit your list easily, which directly reduces complaints. Major ISPs like Gmail, Apple, and Yahoo monitor this behavior. When they see consistent, correct implementation, they’re more likely to accept your messages in the inbox.

For example, RFC 8058 outlines the standard and emphasizes that the header “should not be used to circumvent user choice” — meaning it must be genuine and not just a fake link to hide spam. Implement it correctly, and you're signaling trustworthiness to systems that govern inbox placement.

Use it across all transactional and marketing emails. If you’re doing list hygiene, a tool like MailTester's bulk verification can help you clean up old or invalid addresses before sending—ensuring your List-Unsubscribe recipients are real, not dormant or fake.

How does Feedback-ID actually work behind the scenes?

Feedback-ID tells email providers where to send spam complaints and delivery issues when a recipient marks your message as spam or blocks it. When that happens, the provider routes the feedback directly to the address listed in the Feedback-ID header, so you know exactly when and why your message was flagged. This real-time signal is essential for maintaining sender reputation with gatekeepers like Google and Microsoft.

Step-by-step: What happens when a user marks your email as spam?

  1. You include Feedback-ID in your email headers. You set up a dedicated mailbox (like [email protected]) to receive complaint data. This is the only address that gets these signals from major providers.
  2. The recipient marks your email as spam. When someone flags your message through their email client (like Gmail or Outlook), the system detects that and starts processing the feedback.
  3. The provider sends the complaint to the Feedback-ID address. Providers like Google and Microsoft use this mechanism to pass along structured data — including the original sender, timestamp, and reason — directly to the specified address.
  4. You receive the complaint and analyze it. The feedback arrives in your inbox as a standard email or through an API, depending on your setup. You can track how often it happens, which segments are most affected, and whether content or timing is triggering complaints.
  5. You act to improve sender reputation. If complaints spike, you can pause campaigns, remove problem recipients, or revise templates. This proactive response helps keep your IP and domain in good standing with providers.

Feedback-ID isn’t just a formality — it’s a direct line to the feedback loop that major gatekeepers use to judge sender trustworthiness. If you don’t have it, you're essentially blind to spam complaints. As Spamhaus notes, consistent spam complaints lead to blacklisting, and Feedback-ID is one of the few tools that lets you see those complaints before they escalate.

Why Feedback-ID matters beyond compliance

Without this header, even well-intentioned lists can silently degrade. High complaint rates can trigger automated blacklisting, especially if you're sending at scale. Feedback-ID lets you catch problems early — before they impact deliverability or hurt your brand’s perception.

You can test how your messages perform in real inboxes using MailTester’s inbox placement tester. It checks headers, spam score, and deliverability — including whether Feedback-ID is present and properly formatted. You can also verify your entire list before sending using our bulk verification tool, which confirms valid addresses and highlights risky or invalid ones. For integration with platforms like Mailchimp or SendGrid, explore our integrations to automate checks across your stack.

Can you use one without the other? What are the risks?

You can technically use List-Unsubscribe without Feedback-ID, but you’ll miss out on real-time delivery feedback. Using Feedback-ID alone meets compliance but ignores user expectations. Both headers together create a robust feedback loop that helps maintain inbox placement and sender reputation—especially important at scale. Gmail and other providers increasingly penalize senders who ignore either header.

Why List-Unsubscribe alone isn't enough

For small senders, List-Unsubscribe is often enough to meet basic standards. It lets users opt out with a single click, which improves compliance and reduces spam complaints. But without Feedback-ID, you can't track when bounces or complaints happen in real time. That delay means you won’t catch high-failure patterns until weeks later, hurting your sender reputation and inbox placement.

Without Feedback-ID, your data pipeline remains blind to key delivery signals. This is especially risky if you’re sending at scale or using autoresponders. Some mailbox providers, including those behind major inboxes, now correlate header presence with trustworthiness. Skipping one makes you a higher-risk sender, even if you're technically compliant.

Why Feedback-ID without List-Unsubscribe creates friction

Feedback-ID alone satisfies the technical side of DMARC and RFC specs—providers like Gmail and Yahoo expect it to be used with List-Unsubscribe. But if your list doesn't include a subscription-unsubscribe link, users will feel trapped. This can increase spam flags, even if the email is legitimate.

Think about it: a user who gets a newsletter and can’t easily unsubscribe might mark it as spam. That harms your domain reputation. It’s not about rules alone—it’s about trust. A sender who doesn’t give users control loses credibility, regardless of technical compliance. Gmail’s systems now use user behavior as a direct signal in spam filtering.

Studies on email sender trust show users are more likely to engage with senders who make unsubscribing effortless DMARC Analyzer. Even if your email is legitimate, ignoring user expectations harms deliverability. The combination of both headers isn’t optional—it’s a best practice for sustainable sending.

Use MailTester’s bulk verification to clean lists before sending, then test deliverability with our inbox placement tool to confirm your headers are working as intended.

What happens if your email lacks either header?

If your email misses the Feedback-ID or List-Unsubscribe header, your message may be flagged as suspicious, land in spam folders, or trigger automated filters that penalize your sender reputation—especially at scale. Without Feedback-ID, email providers see no way to measure user feedback, which hurts your reputation over time. Without List-Unsubscribe, users can’t opt out easily, leading to more spam complaints, even if your content is relevant. In extreme cases, repeated failures to include either header can result in domain blocks from major providers like Gmail or Microsoft.

How missing headers harm deliverability

  • You increase the risk of automated filtering: email providers use headers like Feedback-ID and List-Unsubscribe to assess sender trust. Omitting them means your messages lack signals that help distinguish legitimate senders from spammers.
  • High-volume senders without Feedback-ID are more likely to be flagged for reputation scoring issues—providers can’t correlate user feedback with your sending behavior, so they default to caution.
  • Lack of List-Unsubscribe reduces user control, which increases the chance a recipient marks your email as spam. Even if your content is valuable, a forced or awkward opt-out path raises complaint rates.
  • Multiple complaints or poor user signals can trigger domain-level blocks, especially when combined with other red flags like poor list hygiene or high bounce rates.

Real-world consequences over time

  • Providers like Microsoft and Gmail use feedback loops to assess sender behavior. Without Feedback-ID, you’re out of the loop—their systems can’t tell if your users are happy or annoyed.
  • According to RFC 6522, the List-Unsubscribe header is a standard mechanism to simplify opt-outs. Ignoring it reduces compliance with industry best practices, making your messages more likely to be treated as solicited.
  • MailTester’s inbox placement tests help identify if your emails are landing in spam folders due to missing or misused headers. Test your deliverability before sending to real users: try inbox placement testing.
  • Use the MailTester API to verify your list for headers that matter—validity, reputation, and compliance—before you send.
“Senders who ignore standard headers don’t just risk spam folders—they risk being blocked entirely.”

Let’s be clear: these aren’t best practices for optics. They’re requirements for reliable sending. If you’re sending anything beyond a few test emails, both headers should be part of your workflow.

How can you test if your email headers are configured correctly?

You can verify your email headers—especially List-Unsubscribe and Feedback-ID—by testing your messages in a real sending environment. Use tools like MailTester’s inbox placement tester to check header presence and correctness in live inboxes, then examine raw headers in Gmail or MxToolbox to confirm they’re properly formatted and functional. Both headers must be in the email’s SMTP-level headers, not just rendered in the HTML body.

Step-by-step verification process

  1. Use MailTester’s inbox placement tester to send a real email to multiple real inboxes. This gives you live header inspection across Gmail, Outlook, Yahoo, and others. The tool confirms whether both the List-Unsubscribe and Feedback-ID headers appear in the raw message headers, not just in rendered content. Test your headers live.
  2. Check the raw headers from a test inbox. In Gmail, open your email, click the three-dot menu, and select “Show original.” Copy the raw header section. Use MxToolbox’s Header Analyzer to validate presence and format. Both headers should appear in the SMTP header section, not embedded in HTML.
  3. Validate the List-Unsubscribe URI. The URI must be a working, publicly accessible endpoint. Send a test email with the header and verify it actually processes the unsubscribe request. A broken or unreachable endpoint renders the header unusable—even if it’s present.
  4. Verify the Feedback-ID address accepts feedback. The email address in the Feedback-ID header must be monitored and respond to bounces or complaints. Use a mailbox that receives feedback and confirm it’s delivered when a recipient marks your email as spam. A non-functional address breaks the feedback loop.
  5. Confirm headers are not buried in HTML or links. Some senders place these headers as clickable links in the body. This is invalid. Only SMTP-level headers are respected by receiving systems. Test via raw header inspection to ensure they’re not duplicated or hidden.

Why header correctness matters

Without a valid, properly placed List-Unsubscribe header, you risk violating CAN-SPAM and other email laws. The Feedback-ID header must be actionable—delivering feedback to a real mailbox. If both are present but misconfigured, recipients can’t unsubscribe or report spam, and your sender reputation suffers.

“Proper header implementation is a non-negotiable part of deliverability. Missing or broken headers increase inbox placement risk.”

Use the MailTester API to validate a large list before sending, or verify your list bulk for header compliance. These tools catch header issues before they hit the inbox.

How can MailTester help you verify and improve header compliance?

You can use MailTester to catch missing or malformed List-Unsubscribe and Feedback-ID headers before sending, ensuring your emails meet major inbox provider standards. Our inbox-placement tests simulate delivery to Gmail, Outlook, and others with real headers, revealing how your messages will behave in practice, not just in theory.

Real headers, real inbox simulation

When you run an inbox-placement test, MailTester doesn’t just check for syntax — it sends a real email through actual provider infrastructure, complete with headers like List-Unsubscribe and Feedback-ID. This means you see how your email is processed in live environments, including how providers interpret and act on them. RFC 8084 defines the Feedback-ID header as a tool to help ISPs and senders manage complaint feedback, while List-Unsubscribe is recognized by Gmail and others as a standard way to let users opt out with one click. You can verify your implementation aligns with these standards without guessing.

Our system flags missing or improperly formatted headers during both inbox-testing and bulk verification. If your List-Unsubscribe header is missing or malformed, or if Feedback-ID is absent from transactional messages, MailTester will highlight it — so you fix it before your campaign goes live.

Start with clean data, test the whole flow

Invalid or disposable addresses trigger feedback loops and hurt sender reputation. That’s why our bulk email verification checks not just syntax, but also domain validity, catch-all status, and disposable email patterns. The result? You’re not sending to addresses that can’t receive or will auto-report as spam. Learn more about how we validate list quality: bulk verification.

And once you have a clean list, test your full campaign stack. Using the real-time API, you can integrate MailTester with Mailchimp, SendGrid, Klaviyo, and HubSpot — checking every email before it leaves your system. This workflow catches header compliance issues early, before your first bounce or blocklist entry. Test your campaign in real time: inbox placement tester. All paid credits never expire, giving you flexibility when you need it: pricing details.

Is Feedback-ID necessary for small senders?

You don’t need Feedback-ID to send email at all. But if you're serious about long-term deliverability—even at small scale—it gives you real visibility into user actions that could hurt your sender reputation. Without it, you’re blind to complaints and suppression signals from individual inboxes. Even small senders using consistent volume can catch early warning signs of engagement drops or spikes in abuse reports.

Why small senders benefit from Feedback-ID

Feedback-ID isn’t required by Gmail, Yahoo, or any major email provider. But it’s still one of the most effective ways to track how your message is being received on a per-user level. When a user marks your email as spam, Feedback-ID lets you identify that action and correlate it with specific campaigns, segments, or content patterns. This is especially useful for detecting subtle issues before they become systemic.

Even if you only send 500 emails a week, you’re still exposed to feedback loops. A single complaint that goes unnoticed can trigger broader filtering. With Feedback-ID, you can integrate that data into your internal systems and monitor trends—like whether certain subject lines or send times correlate with higher complaint rates. It’s not a luxury; it’s damage control on a microscopic scale.

Setup is fast, and the payoff grows with scale

Implementing Feedback-ID takes minutes—just one DNS record and a small configuration change in your sending system. It doesn’t change your sending flow, but it unlocks a continuous stream of feedback from inbox providers. You won’t see results immediately, but over time, it helps you refine your list hygiene, content strategy, and sending cadence.

Without Feedback-ID, you’re sending blind. There’s no reliable way to know if users are actively marking your messages as spam—especially not at the account level. Over time, this lack of visibility erodes sender reputation. Even if you never send at scale, you’re still vulnerable to sudden inbox placement drops or IP blocklists when small issues snowball.

For a simple way to test how your messages land in real inboxes—including feedback loops and spam signals—try our inbox placement tester. It simulates real delivery across major providers and helps you catch deliverability risks before they hit your list.

Best practices: Implementing both headers correctly

The List-Unsubscribe header must point to a valid, responsive URI that handles GET requests. Invalid or unresponsive links break unsubscribe functionality and increase the risk of being flagged as spam.

The Feedback-ID header requires a dedicated, monitored email address. Using a shared inbox or unmonitored account undermines the feedback loop and prevents timely response to user complaints.

Keep unsubscribe links minimal—only one per message unless contextually justified. Multiple links confuse users and may trigger spam filters. Always test headers in every template using a validation tool before sending to live lists.

MailTester helps verify header compliance at scale, ensuring both headers are implemented correctly and consistently across campaigns.

Sources

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

Does Gmail require List-Unsubscribe for all emails?

Yes, Gmail requires List-Unsubscribe in all marketing and transactional messages starting January 2024 to improve user control.

Can Feedback-ID be a generic email address?

Yes, but it should be dedicated to feedback parsing and monitored daily to catch spam complaints early.

What happens if List-Unsubscribe is missing in a bulk email?

The email may be filtered as spam, especially if sent at scale, and could increase the risk of blacklisting.

Can you use the same email for Feedback-ID and List-Unsubscribe?

Technically yes, but avoid it—feedback responses are system-generated, while List-Unsubscribe is user-facing. Use separate addresses.

How often should I check Feedback-ID logs?

Check daily, especially for high-volume senders. Timely response to feedback prevents reputation damage.

Does MailTester detect incorrect List-Unsubscribe URIs?

Yes, MailTester’s inbox-placement tests analyze both header validity and endpoint functionality.

Are there penalties for missing Feedback-ID on large lists?

Not direct penalties, but lack of feedback data reduces visibility into user behavior, increasing long-term deliverability risk.

Is it possible to use only one header and still deliver successfully?

Yes for small senders, but best practices recommend using both to maintain compliance and reputation at scale.

What’s the difference between Feedback-ID and DMARC feedback?

Feedback-ID reports user actions like spam complaints. DMARC feedback reports authentication failures and alignment issues.

How accurate is MailTester at flagging missing headers?

With 98.9% accuracy, MailTester reliably detects missing or malformed List-Unsubscribe and Feedback-ID headers in real emails.

Do I need to test every email template?

Yes—each template with dynamic content should be tested to ensure headers are preserved and valid.

Can feedback data help reduce spam complaints?

Yes—by analyzing feedback, you can adjust content, sender frequency, or list sources to reduce unwanted actions.