Summary
An expert from Email Geeks confirms Microsoft supports RFC 8058 list-unsubscribe-post, providing implementation details such as the subID being located in the URL parameters. They also noted the potential for Microsoft to use a GET request if only an HTTP link is provided. Microsoft's documentation indirectly acknowledges RFC 8058 by recommending HTTP/HTTPS unsubscribe mechanisms. Various marketing platforms and experts highlight the importance of one-click unsubscribe and managing suppression lists, without explicitly confirming Microsoft's full RFC 8058 compliance. These platforms emphasize best practices for List-Unsubscribe implementation, emphasizing sender reputation and regulatory compliance.
Key findings
- Microsoft Confirmed Support: Microsoft supports RFC 8058 list-unsubscribe-post, according to an Email Geeks expert.
- SubID in URL Parameters: The subID should be included in the URL parameters of the POST request.
- Potential GET Request Fallback: Microsoft might use a GET request if only an HTTP link is provided in the List-Unsubscribe header.
- Indirect Acknowledgement in Docs: Microsoft documentation indirectly acknowledges RFC 8058 by recommending HTTP/HTTPS unsubscribe mechanisms.
- General Unsubscribe Emphasis: Most sources focus on the general importance of List-Unsubscribe implementation for sender reputation, bounce management, and regulatory compliance.
Key considerations
- Correct Implementation: Ensure the correct implementation of the RFC 8058 specification, including the location of the subID in the URL parameters.
- Handle Potential GET Requests: Consider handling potential GET requests if only an HTTP link is provided.
- Comprehensive Strategy: Implement a comprehensive unsubscribe strategy to maintain sender reputation and manage suppression lists effectively.
- Regulatory Compliance: Adhere to regulations like CAN-SPAM when implementing unsubscribe mechanisms.
What email marketers say
6 marketer opinions
Several email marketing platforms highlight the importance of one-click unsubscribe and recommend using a URL for unsubscribing, which aligns with RFC 8058. However, none of the sources explicitly confirm whether Microsoft fully supports the RFC 8058 specification. Instead, they focus on best practices for managing unsubscribes, emphasizing clear and easily accessible unsubscribe links and compliance with regulations like CAN-SPAM.
Key opinions
- One-Click Unsubscribe: Multiple platforms promote one-click unsubscribe as a best practice.
- URL Unsubscribes: The use of URLs for unsubscribing is a common recommendation and a key feature of RFC 8058.
- Lack of Explicit Confirmation: No source explicitly confirms Microsoft's full support for RFC 8058.
- Best Practices Focus: The emphasis is on general unsubscribe best practices and regulatory compliance.
Key considerations
- Microsoft Compliance: Further investigation is needed to confirm Microsoft's explicit compliance with the full RFC 8058 specification.
- Best Practice Implementation: Implementing one-click unsubscribe with a URL, as recommended, improves user experience regardless of full RFC 8058 support.
- Regulatory Compliance: Ensuring unsubscribe processes comply with regulations like CAN-SPAM is crucial.
Marketer view
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.
20 Nov 2021 - Sendinblue
Marketer view
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.
14 Mar 2022 - Zoho
What the experts say
4 expert opinions
Expert from Email Geeks confirms Microsoft supports list-unsub-post (RFC 8058), detailing implementation nuances, including the location of the subID in the URL parameters rather than the POST body. If only an HTTP link is present, Microsoft may use a GET request, which can lead to issues. Other experts highlight the importance of List-Unsubscribe in improving sender reputation and managing suppression lists but do not explicitly confirm Microsoft support.
Key opinions
- Microsoft Support: Confirmed support for list-unsub-post (RFC 8058) by Microsoft.
- Implementation Details: The subID is located in the URL parameters of the POST request.
- GET Request Fallback: Microsoft may use a GET request if only an HTTP link is provided, which may not function correctly.
- General Best Practices: Importance of List-Unsubscribe for sender reputation and suppression list management is highlighted.
Key considerations
- Correct Implementation: Ensuring correct implementation of list-unsub-post, especially regarding the location of the subID.
- HTTP Method Handling: Considering the potential for Microsoft to use a GET request if only an HTTP link is available and implementing accordingly.
- Comprehensive Unsubscribe Strategy: Focusing on a comprehensive unsubscribe strategy for sender reputation.
Expert view
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.
1 Nov 2024 - Email Geeks
Expert view
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.
2 Dec 2021 - Word to the Wise
What the documentation says
4 technical articles
The documentation sources provide information on the List-Unsubscribe header and RFC 8058, but do not offer definitive answers on Microsoft's specific compliance. Microsoft's documentation recommends both mailto: and HTTP/HTTPS unsubscribe mechanisms, indirectly acknowledging support for RFC 8058. The RFC Editor defines the RFC 8058 standard. Other documentation sources promote best practices for implementing List-Unsubscribe headers and highlight its importance for managing bounces and sender reputation, but lack vendor-specific details.
Key findings
- Indirect Acknowledgement: Microsoft documentation indirectly acknowledges RFC 8058 by recommending HTTP/HTTPS unsubscribe mechanisms.
- Standard Definition: RFC Editor provides the standard definition of RFC 8058.
- Best Practices: Sources promote List-Unsubscribe best practices and its impact on sender reputation and bounce management.
- Lack of Specifics: The documentation does not explicitly state Microsoft's compliance with RFC 8058.
Key considerations
- Further Investigation: Further investigation is needed to confirm Microsoft's explicit compliance with RFC 8058.
- Implementation: Focus on implementing List-Unsubscribe headers using both mailto: and HTTP/HTTPS mechanisms.
- Sender Reputation: Consider the impact of List-Unsubscribe implementation on sender reputation and bounce management.
Technical article
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.
18 Mar 2025 - Oracle
Technical article
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.
10 Jun 2023 - Microsoft Learn
How to check if Sendlane complies with RFC 8058 for one-click unsubscribe?
How do I add an unsubscribe header to emails in Intercom?
How can I verify if my company's emails have List-Unsubscribe headers correctly configured?
Are abuse reports and feedback loops (FBLs) still useful in email marketing, and how do they work with different email clients?
What are the challenges and implications of implementing One Click List Unsubscribe Header (RFC 8058) for ESPs?
How do I troubleshoot the List-Unsubscribe header in Responsys?
How do I add an unsubscribe button to the email header and what is RFC 8058?
How are Gmail and Yahoo enforcing unsubscribe requests, and what factors do they consider for compliance?
Is Gmail changing how it tracks email opens and dotted opens?
