Does Microsoft support RFC 8058 list-unsubscribe-post?

Email marketer from Sendinblue explains the importance of one-click unsubscribe. The recommendation of using a URL for unsubscribing is a key feature of RFC 8058, without directly mentioning Microsoft's support for the full standard, support for this aspect indicates compatibility.

Email marketer from Zoho lists best practices for how to correctly manage unsubscribes and shows the benefits of keeping a clean email list, but does not list vendor-specific support details.

Email marketer from HubSpot shares tips to stay compliant with the CAN-SPAM act, including how to implement unsubscribe options to improve email deliverability, however, no vendor-specific information is shared.

Email marketer from Mailjet shares benefits of implementing one-click unsubscribe, although without specifically confirming if Microsoft fully supports the RFC 8058 specification, they do promote using unsubscribe by URL, which is a major component of it.

Email marketer from EmailToolTester details options to manage and track unsubscribes for email marketing campaigns, they also mention how to correctly implement the RFC8058 specification to improve deliverability, but does not provide any vendor-specific support details.

Email marketer from Litmus describes List-Unsubscribe headers including HTTP and mailto options but without reference to specific platform support. They recommend having a clear and easy to find unsubscribe link that is highly visible.

Expert from Email Geeks confirms that Microsoft supports list-unsub-post and shares implementation details. Al initially encountered issues due to a misunderstanding of the POST request format, but corrected the implementation. The POST request includes the subID in the URL parameters, not the body. They also observed that if only an HTTP link is provided in list-unsub without a mailto version or list-unsub-post, Microsoft still calls the URL as a GET request, which may not work correctly.

Expert from Word to the Wise highlights the importance of List-Unsubscribe and managing suppression lists, but the information does not specifically address if Microsoft supports RFC 8058. It covers the advantages of having a clear, easy to use unsubscribe mechanism.

Expert from Spam Resource discusses the List-Unsubscribe header in relation to feedback loops, mentioning that incorporating List-Unsubscribe can improve sender reputation, which indirectly supports RFC 8058 by promoting best practices but not directly stating Microsoft support.

Expert from Email Geeks explains that the body of the POST request is the contents of the List-Unsubscribe-Post header, so it never contains anything useful and can be ignored; the URL should be used instead.

Documentation from Oracle defines the importance of implementing the List-Unsubscribe header to manage bounces and sender reputation but does not define vendor-specific information.

Documentation from Microsoft Learn details the List-Unsubscribe header, recommending both mailto: and HTTP/HTTPS unsubscribe mechanisms. It indirectly acknowledges support for RFC 8058 by allowing a URL, but doesn't explicitly state full RFC 8058 compliance.

Documentation from SparkPost promotes best practices for implementing List-Unsubscribe headers, including use of both mailto: and HTTPS options, but does not offer insights into platform-specific compliance.

Documentation from RFC Editor provides the standard definition of RFC 8058, "Reporting Spam Using an HTTP 'POST' Request", offering deep technical details but no information about specific vendor adoption. This document details how unsubscribes can be managed via HTTP post requests, which can be used as part of List-Unsubscribe functionality.