What are the requirements for one-click unsubscribe with Yahoo and Google, and how does RFC 8058 fit in?
Summary
What email marketers say8Marketer opinions
Email marketer from Email Marketing Forum explains that testing the one-click unsubscribe implementation is important to make sure it is working and quick for the user. They suggest using tools to validate the setup.
Email marketer from Mailjet shares that Google and Yahoo's new requirements include one-click unsubscribe, which is implemented using RFC 8058. This allows users to unsubscribe directly from the email interface without needing to visit a separate webpage.
Email marketer from SparkPost explains that one-click unsubscribe, now a requirement from Google and Yahoo, is achieved by using the List-Unsubscribe header with an HTTPS endpoint as specified in RFC 8058. This offers a seamless unsubscribe experience for recipients.
Email marketer from Email on Acid advises email marketers to prepare for Google and Yahoo's one-click unsubscribe requirements by implementing RFC 8058. They suggest auditing current unsubscribe processes and ensuring the system can handle automated unsubscribe requests efficiently.
Email marketer from GMass explains that compliance with Google and Yahoo's new rules, particularly one-click unsubscribe via RFC 8058, is essential for maintaining deliverability and avoiding spam filters. They also recommend checking with your ESP about their implementation plans.
Email marketer from SenderList shares that the new requirements from Yahoo and Gmail mean you need to manage your lists efficiently. A properly implemented one-click unsubscribe process using RFC 8058 is a huge part of this.
Email marketer from Litmus emphasizes that one-click unsubscribe, driven by Google and Yahoo, is vital for maintaining good sender reputation. Implementing RFC 8058 ensures compliance and improves user engagement by making it easier for recipients to manage their subscriptions.
Email marketer from Reddit explains that even though RFC 8058 is the standard, some older clients might still rely on the 'mailto:' option in the List-Unsubscribe header. It's a good idea to support both for maximum compatibility, at least for now.
What the experts say6Expert opinions
Expert from Email Geeks clarifies that RFC 8058 is required for compliance everywhere, including Google, regarding one-click unsubscribe.
Expert from Email Geeks mentions that mailto links can still be included in the List-Unsubscribe header alongside the https one, and for existing ESPs, it's practical to continue supporting mailto until its usage diminishes significantly.
Expert from Spamresource.com explains that Bulk email senders must implement one-click unsubscribe functionality and this is to reduce spam and unwanted emails, and failing to comply can affect deliverability. This is achieved using RFC 8058.
Expert from Email Geeks provides a canned response and resource link (<https://wordtothewise.com/2024/01/one-click-unsubscribe/>) for the Yahoo/Google one-click unsubscribe question.
Expert from Email Geeks clarifies that Google and Yahoo's 'one-click unsubscribe' refers to RFC 8058 List-Unsubscribe headers, while others often refer to the unsub link in the body of the email related to legal requirements like CAN-SPAM, and that they are almost entirely separate.
Expert from Word to the Wise explains the new one-click unsubscribe requirements from Gmail and Yahoo, noting that the new requirements necessitate the use of RFC 8058 and emphasizes that processing of the requests must occur within 24 hours.
What the documentation says5Technical articles
Documentation from RFC Editor defines the List-Unsubscribe header as a way to provide users with an easy and automated way to unsubscribe from mailing lists, linking to either an email address or a web URL. While RFC 8058 builds on this, this describes the core concept. (RFC2369)
Documentation from Google Workspace Updates explains that senders must support one-click unsubscribe, requiring a List-Unsubscribe header with either mailto: or https: options and mandating that unsubscribe requests are processed within 24 hours. This aligns with RFC 8058 for the HTTP unsubscribe method.
Documentation from Microsoft describes that emails need to adhere to industry best practices for sending. This includes one-click unsubscribe options and ensuring mail meets industry standards.
Documentation from Yahoo Mail Help states that bulk email senders must implement one-click unsubscribe functionality, making it easy for users to opt out of receiving emails. This is to reduce spam and unwanted emails, and failing to comply can affect deliverability. This is achieved using RFC 8058.
Documentation from RFC Editor provides the technical specifications for RFC 8058, which defines a standardized method for one-click unsubscription using the HTTP POST method. This allows email recipients to unsubscribe directly from within their email client, improving user experience and simplifying the unsubscription process.