The List-Unsubscribe header gives a mail client a machine-readable way to opt a recipient out, and since 2024 the one-click version defined by RFC 8058 is mandatory for bulk senders to Gmail and Yahoo, meaning anyone sending 5,000 or more messages a day to personal accounts at those domains.
The List-Unsubscribe header gives a mail client a machine-readable way to opt a recipient out, and since 2024 the one-click version defined by RFC 8058 is mandatory for bulk senders to Gmail and Yahoo, meaning anyone sending 5,000 or more messages a day to personal accounts at those domains.
One-click support needs two headers, not one: List-Unsubscribe with an HTTPS URL, and List-Unsubscribe-Post: List-Unsubscribe=One-Click. A mailto-only header does not satisfy the requirement. This post covers what the header does, whether cold email needs it, and the exact setup.
The List-Unsubscribe header is an email header that lets a recipient's mail client offer a built-in unsubscribe control. RFC 2369 defined the original header; RFC 8058 added one-click unsubscribe, where the client sends a single HTTP POST to opt the recipient out with no confirmation page. Bulk senders to Gmail and Yahoo must include both the List-Unsubscribe and List-Unsubscribe-Post headers and honor requests within two days.
A header the mail client reads to show an unsubscribe link at the top of the message, separate from anything in your email body. RFC 2369 introduced it with two methods: a mailto address and an HTTP URL. RFC 8058 added true one-click: the client sends an HTTP POST to the URL, the sender processes it immediately, and the recipient never leaves their inbox.
The client-rendered unsubscribe is what Gmail and Outlook show near the sender name. It is more visible and more trusted than a link buried in your footer.
Technically the bulk-sender mandate applies at 5,000 messages a day to personal Gmail or Yahoo accounts. A single cold mailbox sending 40 a day is well under that per mailbox.
Include it anyway, for three reasons. Your aggregate volume across a fleet of mailboxes can cross the threshold. Providers reward the header even below the mandate, treating it as a sign of a legitimate sender. And spam score checkers dock you for its absence. There is no downside to including it and a clear upside, so it belongs in every cold email. See google bulk sender requirements.
Three moving parts.
When both headers are present and valid, Gmail and Yahoo render a one-tap unsubscribe next to your name.
Most cold email platforms handle this for you.
What good looks like: both headers in the raw source, an HTTPS endpoint that processes opt-outs on the spot, and a suppression list that spans the fleet.
You want both, and they do different jobs.
The header powers the client's built-in one-click control, which is what machines and privacy-conscious recipients use. A visible unsubscribe line in your email body is for humans reading the message and is also part of staying compliant with commercial-email law, alongside a valid postal address. See cold email without opt in.
For genuine one-to-one cold email, a plain "reply STOP and I will not contact you again" line can serve as the human-visible opt-out, with the header handling the machine path. Higher-volume sequences should carry a proper unsubscribe link.
The same logic applies across providers. Yahoo's sender requirements mirror Gmail's on this point, and Microsoft has moved the same direction for its consumer domains. Building the two-header setup once satisfies all of them, so there is no per-provider work to do beyond getting it right in your sending platform.
Some opt-outs will happen that would not have otherwise, and that feels like a loss. It is not.
An unsubscribe removes a person who was never going to buy. A spam complaint from that same person, which is the alternative when they cannot find an easy opt-out, does roughly ten times the damage to your domain reputation. Trading complaints for unsubscribes is one of the best deals in cold email. See email domain reputation check.
Do not assume it is working because the platform toggle is on. Verify it on a real send.
If the header is missing, the platform may not have finished domain verification, or the unsubscribe feature is off for that specific campaign. Fix it before the campaign scales. See why are my emails going to spam and how to clean a B2B email list.
The Two-Header Rule: one-click unsubscribe requires both List-Unsubscribe with an HTTPS URL and List-Unsubscribe-Post: List-Unsubscribe=One-Click. One header without the other, or a mailto-only URL, does not count for Gmail and Yahoo.
The rule matters because partial setups are common and silently non-compliant. A sender adds List-Unsubscribe with a mailto address, sees the header in the source, and assumes they are covered. Gmail does not render one-click for that, the bulk-sender terms are not met, and the sender only finds out when placement drops.
Check the raw headers of a real sent email. You want to see the https:// URL in List-Unsubscribe and the exact string List-Unsubscribe=One-Click in List-Unsubscribe-Post. If either is missing or the URL is a mailto, the setup is incomplete. The quotable version: "One header is a suggestion. Two headers and an HTTPS URL is one-click."
Then confirm the endpoint actually unsubscribes the person and that the suppression applies across every mailbox you send from.
The List-Unsubscribe header keeps opt-outs from becoming spam complaints. The deeper fix is not emailing people who never wanted to hear from you in the first place.
InboundLabs is a sales intelligence platform built on a database of 280M verified B2B contacts with 98% email deliverability on verified contacts. It layers buyer intent signals on firmographic data and lets you filter by industry, headcount, region, and title, so your sends go to contacts with a real reason to be interested, which keeps both unsubscribe and complaint rates low. Monthly plans, no annual lock-in. Free to start, no credit card required.
See how InboundLabs finds verified contacts instantly → inboundlabs.app
The List-Unsubscribe header lets a mail client offer a built-in unsubscribe, and one-click support under RFC 8058 requires two headers: List-Unsubscribe with an HTTPS URL and List-Unsubscribe-Post: List-Unsubscribe=One-Click. It is mandatory for bulk senders to Gmail and Yahoo and worth including on every cold email regardless of volume. Enable it in your sending platform, verify both headers in a real message, make sure the endpoint honors opt-outs within two days, and suppress unsubscribed contacts across your whole fleet.
An email header that lets the recipient's mail client show a built-in unsubscribe control, separate from your email body. RFC 2369 defined the original version; RFC 8058 added one-click unsubscribe, where the client sends a single HTTP POST to opt the recipient out instantly with no confirmation page.
It is mandatory for bulk senders, defined as 5,000 or more messages a day to personal Gmail or Yahoo accounts. A single cold mailbox is usually under that, but you should include it anyway: aggregate fleet volume can exceed the threshold, providers reward it below the mandate, and spam score checkers penalize its absence.
Enable the unsubscribe feature in your sending platform, which injects both required headers and hosts the endpoint. Then verify a real sent email contains List-Unsubscribe with an HTTPS URL and List-Unsubscribe-Post: List-Unsubscribe=One-Click, confirm the URL actually processes opt-outs, and make suppression apply across every mailbox in your fleet.
Not for one-click compliance. A mailto address cannot guarantee instant automated processing, so Gmail and Yahoo require an HTTPS URL in the List-Unsubscribe header plus the List-Unsubscribe-Post header. You can include a mailto alongside the HTTPS URL, but mailto alone does not satisfy the requirement.
Slightly, yes. But an unsubscribe removes someone who was not going to convert, while the alternative, a spam complaint from a person who cannot find an easy opt-out, does roughly ten times more damage to your domain reputation. Trading complaints for unsubscribes is a strongly positive deal.
Within two days, per the Gmail and Yahoo bulk-sender requirements. Slow processing invites spam complaints and can breach the terms. Sending platforms process one-click unsubscribes automatically and immediately; if you self-host, your endpoint must record the opt-out and stop future sends within the two-day window.
LSI keywords: List-Unsubscribe-Post, RFC 8058, one-click unsubscribe, bulk sender requirements, HTTPS URI, opt-out, suppression list, Gmail Yahoo requirements, email headers, unsubscribe link, spam complaint, CAN-SPAM
Yes, open tracking hurts deliverability, mildly, and mostly through the tracking domain rather than the pixel itself. If the domain hosting your tracking pixel has a poor reputation from other senders sharing it, your email can inherit that spam classification. Practitioners report that disabling op
The best email warm up tool depends on one number: how many mailboxes you run. At 3 mailboxes, per-inbox pricing is fine and any tool works.
The best setup for cold email is not a traditional email service provider. It is real Google Workspace or Microsoft 365 mailboxes, on secondary domains, connected to a sending platform like Instantly, Smartlead, or lemlist.
A custom tracking domain is a subdomain of your sending domain, like track.get-yourco.com, that you point with a CNAME record to your sending platform's tracking endpoint. Once it is live, every tracked open pixel and click link in your emails uses your subdomain instead of the platform's shared...
No commitment. No credit card. Just 50 free verified contact lookups.