--- title: "One-Click Unsubscribe Explained: Meeting Gmail and Yahoo’s RFC 8058 Rule | AutoSPF" description: "Understand RFC 8058 one-click unsubscribe requirements and learn how to meet Gmail and Yahoo’s email compliance standards." image: "https://autospf.com/og/blog/one-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule.png" canonical: "https://autospf.com/blog/one-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule/" --- Quick Answer RFC 8058 defines how email senders implement one-click unsubscribe using List-Unsubscribe and List-Unsubscribe-Post headers. Gmail and Yahoo require qualifying bulk senders to support this feature for marketing emails, helping reduce spam complaints and protect sender reputation. Share [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fautospf.com%2Fblog%2Fone-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule%2F "Share on LinkedIn") [ ](https://twitter.com/intent/tweet?text=One-Click%20Unsubscribe%20Explained%3A%20Meeting%20Gmail%20and%20Yahoo%E2%80%99s%20RFC%208058%20Rule&url=https%3A%2F%2Fautospf.com%2Fblog%2Fone-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule%2F "Share on X/Twitter") [ ](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fautospf.com%2Fblog%2Fone-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule%2F "Share on Facebook") [ ](https://reddit.com/submit?url=https%3A%2F%2Fautospf.com%2Fblog%2Fone-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule%2F&title=One-Click%20Unsubscribe%20Explained%3A%20Meeting%20Gmail%20and%20Yahoo%E2%80%99s%20RFC%208058%20Rule "Share on Reddit") [ ](mailto:?subject=One-Click%20Unsubscribe%20Explained%3A%20Meeting%20Gmail%20and%20Yahoo%E2%80%99s%20RFC%208058%20Rule&body=Check out this article: https%3A%2F%2Fautospf.com%2Fblog%2Fone-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule%2F "Share via Email") ![RFC 8058 One-Click Unsubscribe Guide](https://media.mailhop.org/autospf/create-spf-record-9209-1793949093906.jpg) # **One-Click Unsubscribe Explained: Meeting Gmail and Yahoo’s RFC 8058 Rule** ## What RFC 8058 One-Click Unsubscribe Means and Why It Matters RFC 8058 is an [Internet Engineering Task Force (IETF)](https://www.digicert.com/faq/compliance/what-is-the-internet-engineering-task-force) standard that explains how email senders can support one-click unsubscribe through specific email header fields. It provides a standardized method for making the unsubscribe process simple, secure, and reliable. The standard builds on **RFC 2369** by introducing the List-Unsubscribe-Post header field. _This allows a receiving mail system to send an automated POST request to the unsubscribe endpoint without requiring users to visit a website, log in, or complete additional steps._ [RFC 8058](https://glockapps.com/blog/rfc-8058-explained/) improves the email experience by making subscription removal faster and easier. It also helps reduce spam complaints, **protect sender reputation**, and maintain better email deliverability. For email senders, implementing one-click unsubscribe supports a more reliable and user-friendly mailing process. ![Spf Flattening 3780](https://media.mailhop.org/autospf/spf-flattening-3780-1793950226415.jpg) ## Gmail and Yahoo’s Sender Requirements: Who Must Comply and What’s Required Gmail and Yahoo require qualifying bulk senders to provide one-click unsubscribe functionality for marketing and [promotional emails](https://www.activecampaign.com/glossary/promotional-email). Both providers recognize the RFC 8058 approach, although their **sender policies and eligibility** requirements are not identical. [Transactional emails](https://useinbox.com/transactional-email), such as password resets and order confirmations, are generally excluded from this specific one-click unsubscribe requirement. A compliant mail sender should provide: - A functioning List-Unsubscribe [email header](https://proton.me/blog/what-are-email-headers) - A List-Unsubscribe-Post email header with the value `List-Unsubscribe=One-Click` - An HTTPS URI that accepts an unsubscribe request - No login, password, preference center requirement, or confirmation step - Timely subscription removal after the unsubscribe request - Proper domain authentication through [SPF](https://autospf.com/blog/what-is-spf-email-a-guide-to-sender-validation-technology/), DKIM, and **DMARC alignment** _Mail receivers can use these headers, together with authentication and other sender eligibility signals, to offer a native unsubscribe option in the recipient’s mailbox._ However, displaying the button depends on the provider’s additional eligibility checks. ### Bulk Sender Scope and Practical Impact The rule is most relevant to any mailing list operator sending newsletters, promotions, product updates, or automated marketing campaigns. A transactional message such as a password reset may not need the same unsubscribe mechanism, but a [broadcast marketing](https://voicesofcourage.us/what-is-broadcast-marketing/) list generally does. Gmail and Yahoo require automated unsubscribe requests to work reliably, as delays or failures can increase spam complaints and damage sender reputation. Tools such as [Autospf.com](https://autospf.com/) can support broader domain authentication hygiene, which matters because Gmail and Yahoo evaluate authentication alongside RFC 8058 compliance. ## How List-Unsubscribe and List-Unsubscribe-Post Headers Work ![Spf Lookup 6108](https://media.mailhop.org/autospf/spf-lookup-6108-1793950388843.jpg) The two critical headers are List-Unsubscribe and List-Unsubscribe-Post. Together, they make one-click unsubscribe possible. A simplified example looks like this: ``` List-Unsubscribe: List-Unsubscribe-Post: List-Unsubscribe=One-Click ``` The [List-Unsubscribe header](https://www.twilio.com/en-us/blog/insights/list-unsubscribe) provides the HTTPS URI for sending unsubscribe requests, while List-Unsubscribe-Post indicates that the URI supports RFC 8058-compliant POST requests. _Without this header, the mail receiver may display an unsubscribe option but cannot ensure one-click processing._ The HTTPS URI should use an **opaque identifier** to validate the subscriber or mailing list without exposing private information, such as a raw email address. ### Header Syntax, DKIM, and Trust The email headers must follow valid syntax under [RFC 5322](https://www.suped.com/blog/what-rfc-5322-says-vs-what-actually-works) to ensure proper recognition by the mail receiver. Malformed headers may be ignored. DKIM authentication is also important, as a valid signature under RFC 6376 helps verify that the [List-Unsubscribe](https://www.mailneo.co/glossary/list-unsubscribe) and List-Unsubscribe-Post headers were added by an authorized mail sender and remained unchanged during transit. ### Why Mail Receivers Prefer POST Over GET RFC 8058 uses POST requests instead of GET actions to prevent accidental unsubscriptions. Since web browsers and **automated security system**s may scan or prefetch URLs, using GET could unintentionally remove subscribers from mailing lists. _Requiring List-Unsubscribe-Post with a specific POST request body allows trusted mail receivers to process unsubscribe requests safely._ ## Implementation Checklist: Technical Setup, Testing, and Common Mistakes A solid RFC 8058 implementation requires coordination between marketing platforms, mail software, **DNS authentication**, and the unsubscription server. ### Technical Setup Steps Start with the email header. Every eligible **marketing message** should include a List-Unsubscribe header containing an HTTPS URI. The same message should include: ``` List-Unsubscribe-Post: List-Unsubscribe=One-Click ``` The unsubscribe endpoint must accept HTTPS POST requests using the request body specified by RFC 8058\. _The receiving mail system should send the request as multipart/form-data or may use application/x-www-form-urlencoded._ The endpoint must process the request without relying on cookies, HTTP authorization, or other session context. ![Email Spf 3714](https://media.mailhop.org/autospf/email-spf-3714-1793950434554.jpg) ### Testing Before Production Testing should confirm that: - The List-Unsubscribe header is present and contains an HTTPS URI - The List-Unsubscribe-Post header is present and correctly formatted - The POST request triggers subscription removal - The unsubscribe process does not require manual intervention - The recipient mailbox receives mail authenticated with **DKIM, SPF, and DMARC** - The To header, List-Unsubscribe header, and [DKIM-Signature](https://autospf.com/dkim/dkim-signature/) are not corrupted by downstream systems _You should test with real Gmail and Yahoo recipient mailbox accounts and inspect the raw email header._ Many teams also use internal QA tools to validate header syntax, **ABNF expectations**, DKIM results, and domain authentication. ### Common Mistakes to Avoid Another important implementation mistake is returning an HTTPS redirect from the unsubscribe endpoint. RFC 8058 specifies that the endpoint must not return an HTTPS redirect because redirected POST requests may not work reliably. The original [HTTPS endpoint](https://beeceptor.com/docs/concepts/http-endpoints/) should process the unsubscribe request directly. ## Compliance Benefits: Deliverability, User Trust, and Long-Term Email Program Health Proper RFC 8058 support improves [email deliverability](https://autospf.com/blog/optimizing-email-deliverability-strategies-for-success/) by giving recipients an easy way to unsubscribe instead of reporting [messages as spam](https://cybernews.com/news/microsofts-breach-notification-emails-end-up-in-spam-folder/). _A reliable one-click unsubscribe process helps reduce spam complaints, protect sender reputation, build user trust, and maintain a positive email experience._ It also improves mailing list quality by removing uninterested subscribers, increasing engagement, and **keeping marketing data accurate**. Following RFC 8058 requirements helps email senders maintain compliance, respect user preferences, and support long-term email program health. ![Brad Slavin](https://media.mailhop.org/autospf/images/authors/brad-slavin.jpg) [ Brad Slavin ](/authors/brad-slavin/) General Manager General Manager of DuoCircle. Product strategy and commercial lead for AutoSPF's 2,000+ customer base. [LinkedIn Profile →](https://www.linkedin.com/in/bradslavin) ## Ready to get started? Try AutoSPF free — no credit card required. [ Book a Demo ](/book-a-demo/) Scan Your Domain Now Instantly scan your domain for DKIM, SPF, and DMARC issues Check My Domain Share this article [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fautospf.com%2Fblog%2Fone-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule%2F) [ ](https://twitter.com/intent/tweet?text=One-Click%20Unsubscribe%20Explained%3A%20Meeting%20Gmail%20and%20Yahoo%E2%80%99s%20RFC%208058%20Rule&url=https%3A%2F%2Fautospf.com%2Fblog%2Fone-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule%2F) [ ](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fautospf.com%2Fblog%2Fone-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule%2F) Copy Related Articles - [ ![DIY-ing SPF](https://media.mailhop.org/autospf/images/2024/04/spf-record-example-5874.jpg) 10 Reasons Why DIY-ing SPF isn’t a Good Choice for Companies Intermediate ](/blog/10-reasons-diy-ing-spf-isnt-good-choice-for-companies/) - [ ![phishing actors](https://media.mailhop.org/autospf/images/2025/11/spf-record-checker-0096.jpg) The 12.4 billion shield for your email communications: Why DMARC software is the unsung hero in the war against phishing actors! Intermediate ](/blog/12-4-billion-dmarc-software-shield-protecting-email-from-phishing-actors/) - [ ![421 Error SMTP Guide](https://media.mailhop.org/autospf/spf-lookup-1607-1785756872932.jpg) 421 Error SMTP Survival Guide: Fix the 4.4.2 Connection Dropped Issue Intermediate ](/blog/421-error-smtp-survival-guide-fix-connection-dropped-email-issue/) - [ ![DNS vulnerabilities affecting email authentication](https://media.mailhop.org/autospf/spf-lookup-9081-1790592336407.jpg) 5 Common DNS Vulnerabilities Affecting Email Authentication Intermediate ](/blog/5-common-dns-vulnerabilities-affecting-email-authentication/) ## Related Articles [ Intermediate 6m 10 Reasons Why DIY-ing SPF isn’t a Good Choice for Companies Apr 4, 2024 ](/blog/10-reasons-diy-ing-spf-isnt-good-choice-for-companies/)[ Intermediate 5m The 12.4 billion shield for your email communications: Why DMARC software is the unsung hero in the war against phishing actors! Nov 19, 2025 ](/blog/12-4-billion-dmarc-software-shield-protecting-email-from-phishing-actors/)[ Intermediate 421 Error SMTP Survival Guide: Fix the 4.4.2 Connection Dropped Issue Aug 3, 2026 ](/blog/421-error-smtp-survival-guide-fix-connection-dropped-email-issue/)[ Intermediate 5 Common DNS Vulnerabilities Affecting Email Authentication Sep 28, 2026 ](/blog/5-common-dns-vulnerabilities-affecting-email-authentication/) ```json {"@context":"https://schema.org","@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com","logo":{"@type":"ImageObject","url":"https://autospf.com/images/autospf-logo.png"},"description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138897474","https://www.linkedin.com/company/autospf","https://x.com/autospf01","https://www.g2.com/products/autospf/reviews"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://autospf.com/contact-us/"},"knowsAbout":["SPF Record Flattening","Sender Policy Framework","Email Authentication","DNS Management","DMARC","DKIM"]} ``` ```json {"@context":"https://schema.org","@type":"WebSite","name":"AutoSPF","url":"https://autospf.com","description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","publisher":{"@type":"Organization","name":"AutoSPF","url":"https://autospf.com","logo":{"@type":"ImageObject","url":"https://autospf.com/images/autospf-logo.png"},"description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]}}} ``` ```json {"@context":"https://schema.org","@type":"BlogPosting","headline":"One-Click Unsubscribe Explained: Meeting Gmail and Yahoo’s RFC 8058 Rule","description":"Understand RFC 8058 one-click unsubscribe requirements and learn how to meet Gmail and Yahoo’s email compliance standards.","url":"https://autospf.com/blog/one-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule/","datePublished":"2026-11-06T00:00:00.000Z","dateModified":"2026-11-06T00:00:00.000Z","dateCreated":"2026-11-06T00:00:00.000Z","author":{"@type":"Person","@id":"https://autospf.com/authors/brad-slavin/#person","name":"Brad Slavin","url":"https://autospf.com/authors/brad-slavin/","jobTitle":"General Manager","description":"Brad Slavin is the General Manager of DuoCircle, the company behind AutoSPF, DMARC Report, Phish Protection, and Mailhop. He founded DuoCircle in 2014 to solve the SPF 10-DNS-lookup problem at scale and has led the company's growth to 2,000+ customers. Brad's focus is product strategy, customer relationships, and the commercial and compliance side of email authentication (DPAs, SLAs, enterprise procurement) rather than hands-on DNS engineering.","image":"https://media.mailhop.org/autospf/images/authors/brad-slavin.jpg","knowsAbout":["Email Security Strategy","SaaS Product Management","Enterprise Compliance","Customer Success","Email Deliverability Business"],"worksFor":{"@type":"Organization","name":"AutoSPF","url":"https://autospf.com"},"sameAs":["https://www.linkedin.com/in/bradslavin"]},"publisher":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com","logo":{"@type":"ImageObject","url":"https://autospf.com/images/autospf-logo.png"},"description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138897474","https://www.linkedin.com/company/autospf","https://x.com/autospf01","https://www.g2.com/products/autospf/reviews"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://autospf.com/contact-us/"},"knowsAbout":["SPF Record Flattening","Sender Policy Framework","Email Authentication","DNS Management","DMARC","DKIM"]},"mainEntityOfPage":{"@type":"WebPage","@id":"https://autospf.com/blog/one-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule/"},"articleSection":"intermediate","keywords":"","image":{"@type":"ImageObject","url":"https://media.mailhop.org/autospf/create-spf-record-9209-1793949093906.jpg","caption":"RFC 8058 One-Click Unsubscribe Guide"},"speakable":{"@type":"SpeakableSpecification","cssSelector":[".answer-block","h1"]}} ``` ```json {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://autospf.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://autospf.com/blog/"},{"@type":"ListItem","position":3,"name":"Intermediate","item":"https://autospf.com/intermediate/"},{"@type":"ListItem","position":4,"name":"One-Click Unsubscribe Explained: Meeting Gmail and Yahoo’s RFC 8058 Rule","item":"https://autospf.com/blog/one-click-unsubscribe-rfc-8058-compliance-guide-gmail-yahoo-rule/"}]} ```