The List-Unsubscribe header (RFC 8058) is the email header that powers a one-click unsubscribe button in the inbox, required by Google and Yahoo on bulk mail and honored within 48 hours, as distinct from a text link buried in the message body.
The List-Unsubscribe header, defined in RFC 8058, is what puts a one-click unsubscribe button directly in the mailbox interface, next to reply and forward, instead of requiring a recipient to find and click a link somewhere in the body of the message. Google and Yahoo both require it on bulk mail, and both require the opt-out it triggers to be honored within 48 hours.
Google's and Yahoo's bulk-sender rules bundle the List-Unsubscribe requirement together with SPF, DKIM, and DMARC authentication and a spam-rate ceiling. None of it reads what a message says. All of it checks whether a sender behaves like a legitimate one: proven identity, a working opt-out, low complaint volume. A message without a working List-Unsubscribe header fails this check regardless of how relevant or well-written it is.
The threshold that triggers the requirement is the same one that triggers the rest of the bulk-sender rules: more than 5,000 messages a day to Gmail addresses, with Yahoo's guidance asking for the same baseline. Most real cold outbound programs cross that line faster than expected once several mailboxes are sending at real volume, which makes the header worth setting up well before it's technically mandatory.
Confirm the sequencer actually implements the List-Unsubscribe header correctly rather than assuming it. A header that's present but misconfigured, or an unsubscribe request that isn't honored inside 48 hours, fails the same requirement a missing header does.
Teams treat a text unsubscribe link at the bottom of the email as equivalent to the header requirement. It isn't the same mechanism, and mailbox providers score them differently: the header puts the option in front of the recipient before they even open the message, which is exactly why Google and Yahoo require it specifically rather than accepting any opt-out method a sender happens to include.
Tell us how your motion runs today. We'll show you what we'd engineer.
Contact us