AboutMy.Email reports RFC 8058 failures for one-click unsubscribe due to a multitude of reasons related to List-Unsubscribe header implementation, unsubscribe endpoint configuration, server-side processing, and compliance with the one-click unsubscribe standard. Root causes include: AboutMy.Email itself having a bug (expecting 200 OK instead of accepting 202 Accepted), issues with 202 Accepted responses not resulting in actual unsubscribes, incorrect header syntax, non-functional unsubscribe endpoints, lack of server support for POST requests, server errors, authentication requirements violating RFC 8058, and the failure to properly log and action unsubscribe requests. Maintaining consistent and reliable unsubscribe processing is crucial for preserving sender reputation.
8 marketer opinions
AboutMy.Email reports RFC 8058 failures for one-click unsubscribe primarily due to issues with the List-Unsubscribe header configuration and the handling of the unsubscribe POST request. Common problems include incorrect header syntax, server errors, authentication requirements on the unsubscribe endpoint (violating RFC 8058), the server not processing the POST request correctly, and failure to actually unsubscribe the user or log the unsubscribe action.
Marketer view
Email marketer from Reddit discusses the need for thoroughly testing the one-click unsubscribe process. They mention potential issues where the unsubscribe request isn't properly processed, leading to RFC 8058 failures.
1 Feb 2022 - Reddit
Marketer view
Email marketer from Email Marketing Tips explains a common cause for one-click unsubscribe failure is improper configuration of the List-Unsubscribe header or issues with the endpoint that receives the unsubscribe POST request. This can include server errors or authentication requirements on the unsubscribe endpoint.
1 Nov 2023 - Email Marketing Tips
7 expert opinions
AboutMy.Email reports RFC 8058 failures for one-click unsubscribe due to various reasons related to header implementation, server response, and unsubscribe processing. These include AboutMy.Email's bug in expecting a 200 response instead of accepting a 202, the server not actually unsubscribing users after accepting the POST request, incorrect header implementation, non-functional unsubscribe endpoints, authentication requirements (403 error) which violate the standard, and the overall importance of reliable unsubscribe processing for maintaining sender reputation. ESP users generally need to trust that their provider is handling unsubscribes correctly.
Expert view
Expert from Email Geeks identifies the AboutMy.Email issue as a bug, explaining that it expects a 200 response from the unsubscribe process but isn't configured to accept a 202 response.
24 May 2022 - Email Geeks
Expert view
Expert from Email Geeks clarifies that a 202 response to an unsubscribe request means the POST was accepted but no action has been taken, while Marketer from Email Geeks, Marcel Becker, advises to ensure users are actually unsubscribed, as neglecting to do so can negatively impact domain reputation.
12 Nov 2024 - Email Geeks
4 technical articles
AboutMy.Email reporting RFC 8058 failures for one-click unsubscribe is linked to several factors outlined in technical documentation. RFC 8058 specifies the List-Unsubscribe header format and the need for a POST request endpoint. Failures arise from incorrect header formatting, endpoint issues (lack of support for POST), or server-side problems. HTTP status codes like 403 (Forbidden) signify authentication issues, violating the standard, while 500 or 503 indicate server-side problems. Proper implementation requires correct header syntax, proper POST request handling, and a successful 200 OK response from the server.
Technical article
Documentation from MDN Web Docs explains that HTTP status codes like 403 (Forbidden) can indicate that the server is refusing to fulfill the unsubscribe request due to missing authentication or permissions, violating the one-click unsubscribe standard.
5 Feb 2023 - MDN Web Docs
Technical article
Documentation from SparkPost details the correct syntax and implementation of the List-Unsubscribe header. It highlights ensuring that the server handling the unsubscribe POST request correctly processes the request and returns a success response (200 OK).
19 Dec 2022 - SparkPost
Are mailto links compliant with Google and Yahoo's one-click unsubscribe requirements?
Does Microsoft support RFC 8058 list-unsubscribe-post?
How are Gmail and Yahoo enforcing unsubscribe requests, and what factors do they consider for compliance?
How do Gmail and Yahoo's new one-click unsubscribe requirements work?
How do I add an unsubscribe button to the email header and what is RFC 8058?
How to check if Sendlane complies with RFC 8058 for one-click unsubscribe?