Is using the same URL for both List-Unsubscribe header and body compliant with RFC 8058 for one-click unsubscribe?

Email marketer from EmailonAcid stated that the List-Unsubscribe header must have a way to unsubscribe a user with a single click. As long as it handles the requests as needed, it can be the same URL as the body link.

Email marketer from Mailjet explains that using the List-Unsubscribe header with a one-click unsubscribe option is crucial for compliance. They highlight the importance of handling POST requests correctly to ensure a seamless unsubscribe experience. They also mention that the URL used in the header can technically be the same as the one in the email body, as long as the server differentiates between GET and POST requests.

Email marketer from StackOverflow writes that he believes it to be okay to use the same URL for both, they reiterate that the different request types from the header versus the body must be respected.

Email marketer from Email Geeks shares that if the engineer receives a HTTPS POST request on the unsubscribe URL, they must silently unsubscribe the user. If they get an HTTPS GET Request, they must return HTML which allows the user to click.

Email marketer from Email Marketing Forum stated that technically yes it is fine to have the same URL as long as they are handled differently. But also notes that different URL's would lead to a better UX.

Email marketer from Reddit shares that it is compliant, as long as you handle the HTTPS POST request for the header link correctly versus the HTTPS GET request from the body link.

Email marketer from Litmus explains that implementing a one-click unsubscribe, using the List-Unsubscribe header correctly, improves deliverability. The article indicates it's acceptable for the header URL to direct to the same unsubscribe page as the body link, provided the server handles POST requests from the header differently from GET requests from the body link.

Email marketer from Sendinblue shares that RFC 8058 compliance requires a one-click unsubscribe mechanism. The List-Unsubscribe header should be implemented correctly, and while the URL can be the same as in the email body, it’s vital to process POST requests silently to unsubscribe the user without requiring additional clicks.

Expert from Email Geeks explains that using the same URL for both List-Unsubscribe header and the body is normal. The header requires a List-Unsubscribe-Post header and a POST request to the URL must perform the unsubscription. When clicked from the body the URL must go to a webpage to unsubscribe.

Expert from Email Geeks advises to personally test the one-click unsubscribe functionality rather than trusting the server-side implementation.

Expert from Word to the Wise explains that a one-click unsubscribe can be tested using a command line to POST to the unsubscribe URL.

Expert from Email Geeks explains that the Gmail unsubscribe option will not open a subscription center, but will silently POST to the server and unsubscribe the user.

Expert from Word to the Wise shares that if aboutmy.email reports the email as compliant, it is likely compliant. He then reiterates that the List-Unsubscribe needs to be an HTTPS one-click unsubscribe.

Documentation from SparkPost explains that the URL in the List-Unsubscribe header can be the same. They do emphasize that if this is the case then the server must differentiate between GET and POST requests.

Documentation from Microsoft details the requirements for bulk email senders, including the need for a one-click unsubscribe option. It mandates the inclusion of the List-Unsubscribe header, and while it doesn't explicitly prohibit the same URL, it expects the POST method to be handled appropriately for immediate unsubscription.

Documentation from Google Workspace Admin Help explains that Gmail requires a one-click unsubscribe feature, implemented via the List-Unsubscribe header. While not directly addressing the same URL, the documentation emphasizes the importance of handling POST requests correctly to facilitate one-click unsubscription, implying that the header URL is treated differently.

Documentation from RFC Editor specifies that the List-Unsubscribe header field can contain either a single URI or a comma-separated list of URIs. These URIs provide a means for users to unsubscribe from the mailing list. The standard doesn't explicitly forbid the same URL being used in both header and body but mandates specific behavior for POST requests to the header URL.