List-Unsubscribe header
What is List-Unsubscribe header?
The List-Unsubscribe header is an email header that lets a sender publish a mailto or HTTPS link so a mail client can unsubscribe a recipient without them opening the message, with RFC 8058 adding a one-click POST option. AdminKit's blacklist check shows how to spot the listing that skipping it can cause.
By AdminKit team, Netbase JSC · Updated
The List-Unsubscribe header is an email header, originally defined in RFC 2369 and extended by RFC 8058’s one-click mechanism (current document status at its IETF Datatracker entry), that lets a sender publish a mailto or HTTPS link a mail client can use to unsubscribe a recipient without them ever opening the message or hunting for a link in the body. RFC 8058 adds a paired List-Unsubscribe-Post header so a client can fire a one-click POST request instead of just opening a mailto link, which is now effectively required by Gmail and Yahoo’s bulk-sender rules alongside authentication requirements like SPF and DKIM alignment for anyone sending high volumes of mail — Google spells out the one-click requirement directly in its own email sender guidelines. Yahoo’s sender best practices set the same expectation: a functioning list-unsubscribe header that supports one-click unsubscribe, with the RFC 8058 POST method highly recommended, the mailto method acceptable, and unsubscribes honored within 2 days. Omitting it, or publishing it but letting the link fail, pushes frustrated recipients toward the spam-complaint button instead, and complaint rate is one of the reputation signals that feeds into whether a sending domain or IP ends up on a blocklist. AdminKit’s blacklist check reports that downstream outcome, even though it doesn’t parse the header itself.
AdminKit groups list-Unsubscribe header under its email authentication cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
What does RFC 8058 add on top of the original List-Unsubscribe header?
A paired List-Unsubscribe-Post header, so a client can fire a one-click POST request instead of just opening a mailto link -- a mechanism now effectively required by Gmail and Yahoo's bulk-sender rules.
What happens if a sender omits the header or lets its link fail?
Frustrated recipients get pushed toward the spam-complaint button instead, and complaint rate is one of the reputation signals that feeds into whether a sending domain or IP ends up on a blocklist.
Can a recipient unsubscribe without opening the message?
Yes -- that's the point of the header: the sender publishes a mailto or HTTPS link the mail client can act on directly, without the recipient ever opening the message or hunting for an unsubscribe link in the body.
Why do major mailbox providers require this header now?
Because bulk-sender rules from providers like Gmail and Yahoo now require a working one-click unsubscribe, alongside authentication requirements like SPF and DKIM alignment, for anyone sending high volumes of mail.