Why this header protects your deliverability
When unsubscribing is hard, recipients take the shortcut: the spam button. Every complaint damages your sender reputation — and reputation determines inbox placement for everyone else on your list.
A properly configured List-Unsubscribe header inverts that dynamic. It makes leaving easy, which keeps complaints low, protects deliverability and, paradoxically, preserves the value of your list.
An unsubscribe is recoverable. A spam complaint is not.
The two methods, explained
The header can declare two methods to unsubscribe. Declaring both gives every mailbox provider an option it supports — and the link method can be made one-click with a companion header.
A secure link that unsubscribes the recipient, pointing to your unsubscribe page or preference center.
A working email address that receives unsubscribe requests and processes them automatically.
A companion header tells mailbox providers that the link method can be triggered in a single action, without opening a page. Gmail and Yahoo expect it from bulk senders.
How to read a List-Unsubscribe check
5 best practices
- Declare both methods in the header: List-Unsubscribe: <mailto:…>, <https://…>.
- Use HTTPS links and addresses on your authenticated domain — never a third-party domain.
- Make the process one-click (RFC 8058): no login, no “are you sure?”, no dark patterns.
- Keep the visible unsubscribe link in the email body: the header is a complement, not a replacement.
- Process every request promptly — immediately where possible, within days at most — and keep SPF, DKIM and DMARC compliant alongside it.
Common mistakes
- Sending the HTTPS link to a page that requires a login or an extra confirmation.
- Declaring a mailto: address that nobody monitors and no system processes.
- Using a link on your platform's domain instead of your own sending domain.
- Assuming the header is present because it was configured once — a template or platform change can silently remove it.
- Removing the visible unsubscribe link from the body because “the header is enough”.
How Inbox Maestro checks it
Inbox Maestro reads the actual headers of the test email your platform sends and verifies both List-Unsubscribe methods. The header you configured is not always the header that ships — a real test email is the only way to be sure. The result appears in the Checkup section of your report, under Infrastructure, next to Authentication.
Frequently asked questions
What is the List-Unsubscribe header?
A standardized header that lets email clients display a native unsubscribe button in their interface. It complements — never replaces — the unsubscribe link in the email body.
Is List-Unsubscribe mandatory?
Gmail and Yahoo require it for high-volume senders since 2024, including support for one-click unsubscribe. Beyond the requirement, it helps reduce spam complaints.
Does an easy unsubscribe hurt my list?
It removes recipients who would otherwise complain or ignore you. An unsubscribe is a neutral exit; a spam complaint actively damages deliverability for your entire list.
What is one-click unsubscribe (RFC 8058)?
A standard that lets the recipient opt out with a single action, without loading a page or confirming. It relies on a companion header, List-Unsubscribe-Post, and Gmail and Yahoo reference it in their sender requirements.