Definition
The List-Unsubscribe header is an email header that provides a direct mechanism for recipients to unsubscribe from a mailing list without composing a message or visiting a website. The header supports two methods: a mail-to URI that triggers an automated unsubscribe email, and an HTTPS URI that processes the unsubscribe via a web request. RFC 8058 introduced the one-click unsubscribe standard, which adds a List-Unsubscribe-Post header and requires the HTTPS endpoint to process the request without requiring additional user interaction.
In 2024, Gmail and Yahoo made the one-click List-Unsubscribe header mandatory for senders who send more than 5,000 messages per day to their respective domains. The mandate requires both the List-Unsubscribe header with an HTTPS URI and the List-Unsubscribe-Post header. Compliance failures can result in delivery throttling or rejection. The header must appear in the message headers, not in the body, and the HTTPS endpoint must process unsubscribe requests immediately.
Best Practices
Implement both the HTTPS URI and the mail-to URI in the List-Unsubscribe header. The HTTPS method provides instant processing via RFC 8058 one-click, while the mail-to method serves as a fallback for mail clients that do not support the HTTPS method.
Ensure your HTTPS unsubscribe endpoint complies with RFC 8058 by returning a 200 OK status or a 303 See Other redirect after processing the unsubscribe. The endpoint must not present a confirmation page, ask for a password, or require any action beyond the initial click. Instant processing is required.
Include both List-Unsubscribe and List-Unsubscribe-Post headers in every bulk message. The List-Unsubscribe-Post header is the signal that tells the mail client this endpoint supports one-click unsubscribe. Omission of this header means the client will not show the one-click unsubscribe button.
Monitor your unsubscribe rates by domain and by campaign. A sudden spike in unsubscribe requests may indicate a deliverability problem, a change in sending frequency that recipients find excessive, or a mismatch between subscriber expectations and email content.
Test your unsubscribe endpoint regularly. Broken or slow unsubscribe endpoints are a common cause of spam complaints and deliverability issues. If a subscriber cannot unsubscribe immediately, they are likely to mark the message as spam instead, which damages sender reputation.
Related Glossary Terms
Bounce Classification
Bounce classification uses SMTP codes (550, 551, 552, 553, 554, 450, 451, 452) and enhanced status codes to categorise permanent and transient delivery failures.
DMARC Alignment
DMARC identifier alignment determines whether the domain in the From header matches the domains used in SPF and DKIM authentication. Strict or relaxed.
Email Active Subscriber
An active email subscriber has opened or clicked an email within a defined recency period, typically 30-90 days by industry. Active subscriber rate of 40-60% is typical for healthy email lists.
Australia Spam Act
Australia's Spam Act 2003 regulates commercial electronic messages including email. It requires consent, functional unsubscribe mechanisms within 5 working days, and sender identification. Penalties reach AUD $2.22 million per day.
Email Blacklist
An email blacklist (DNSBL) is a real-time database of IP addresses or domains known for sending spam or unwanted email.
Email Bounce
The return of an undelivered email to the sender, categorized as hard, soft, or transient with distinct handling rules for each.
Frequently Asked Questions
A typical List-Unsubscribe header is `List-Unsubscribe:
For bulk senders sending more than 5,000 messages per day to Gmail or Yahoo addresses, the List-Unsubscribe header with one-click HTTPS support is mandatory as of February 2024. Other mailbox providers are increasingly enforcing similar requirements. For lower-volume senders, it remains a best practice.
If your HTTPS endpoint does not process the unsubscribe within seconds, the mailbox provider may consider your implementation non-compliant. Repeated non-compliance can lead to delivery throttling, spam classification, or complete blocking of your sending IP addresses by the mailbox provider.
Yes, most email service providers offer built-in List-Unsubscribe headers that point to their own unsubscribe processing endpoints. Using your ESP's infrastructure ensures the endpoint is properly maintained, scalable, and compliant with RFC 8058 requirements.
Most major email clients, including Gmail, Outlook, Yahoo Mail, and Apple Mail, recognise the List-Unsubscribe header and display an unsubscribe button in the UI. The presentation varies by client, but the underlying header is widely supported across web, desktop, and mobile email applications.