Summary
In September 2020, multiple email service providers (ESPs) reported issues with receiving Feedback Loop (FBL) reports from Microsoft. The disruption began around mid-September. Potential causes include Microsoft infrastructure changes impacting SPF/DKIM validation and delivery speeds, occasional Microsoft FBL outages, glitches in Microsoft's internal systems, and changes in how Microsoft processes FBL data. Some suggest checking Microsoft's status page, contacting support, and waiting a few days for resolution. Authentication issues, particularly with SPF, DKIM, and DMARC implementation, along with temporary DNS issues affecting authentication may have caused FBL problems. Others suggested double-checking FBL setup, monitoring IP reputation via Microsoft's SNDS program, and closely monitoring delivery metrics to identify potential issues. Data privacy considerations impacting how Microsoft processed and shared data, or reputation-based suppression of FBL reports due to increased complaints or decreased engagement were also possible causes.
Key findings
- Widespread FBL Disruption: Multiple ESPs experienced a cessation of Microsoft FBL reports around mid-September 2020.
- Infrastructure and System Issues: Microsoft infrastructure changes, system glitches, outages, or changes in FBL data processing may have contributed to the problem.
- Authentication Problems: Issues with SPF, DKIM, or DMARC implementation, and temporary DNS problems could impact FBL reporting.
- Reputation Impacts: Sudden changes in sender reputation may cause Microsoft to suppress FBL reports.
- Data Privacy Changes: Changes in data privacy standards, causing changes in the way FBL data is sent.
Key considerations
- Check Status and Contact Support: Verify Microsoft's status page for known issues and contact support if necessary.
- Review FBL Setup: Double-check FBL setup to ensure proper configuration.
- Monitor Reputation and Metrics: Monitor IP reputation using Microsoft's SNDS and track delivery metrics for abnormalities.
- Authentication Implementation: Ensure SPF, DKIM, and DMARC are properly implemented.
- Adapt to Privacy Standards: Stay informed about and adapt to evolving data privacy standards.
- Watch DNS Propagation: Ensure SPF and DKIM record changes propagate correctly.
What email marketers say
16 marketer opinions
In September 2020, several email service providers (ESPs) experienced issues with receiving Feedback Loop (FBL) reports from Microsoft. The disruptions generally started around mid-September. Possible causes include Microsoft infrastructure changes impacting SPF/DKIM validation and delivery delays, occasional outages on Microsoft's end, and potential glitches in Microsoft's internal systems. Some suggest checking Microsoft's status page for known outages or contacting Microsoft support. Other suggestions included temporary glitches, or Microsoft changing the way they process FBL data. It was recommended to double-check FBL setup, monitor IP reputation using Microsoft's SNDS program to identify filtering issues, and to monitor delivery metrics.
Key opinions
- Widespread Issue: Multiple ESPs reported a cessation of Microsoft FBL reports around the same time in September 2020.
- Infrastructure Changes: Microsoft infrastructure changes may have impacted SPF/DKIM validation and delivery speeds.
- Potential Glitches: Temporary glitches or internal system issues on Microsoft's end could be responsible.
- Possible Changes to FBL processing: It's possible that Microsoft changed the way FBL data is processed.
Key considerations
- Check Microsoft Status: Consult Microsoft's status page or contact support to identify known outages.
- Verify FBL Setup: Double-check FBL setup and ensure it's correctly configured.
- Monitor IP Reputation: Use Microsoft's SNDS program to monitor IP reputation and complaint rates.
- Monitor Delivery Metrics: Proactively monitor deliverability metrics to identify and resolve potential issues.
- Check DNS Settings: Ensure SPF and DKIM records are correctly configured and propagating properly to avoid authentication failures that affect FBL reporting.
Marketer view
Marketer from Email Geeks shares their FBL reports seemed to stop on the 17th but then came back and were backdated.
29 Oct 2022 - Email Geeks
Marketer view
Marketer from Email Geeks shares that several ESPs are facing the issue of not receiving FBL complaints from Microsoft since Thursday evening (UTC time). They have started a thread on Mailop and suggest verifying if others are also impacted.
7 Oct 2023 - Email Geeks
What the experts say
3 expert opinions
Experts suggest that the disruption in Microsoft FBL reports in September 2020 could stem from several factors. Data privacy considerations might have led to changes in Microsoft's data processing and sharing practices, causing temporary disruptions. Common issues such as misconfiguration, blocklisting, and network glitches could also impact FBL report reception. Additionally, a sudden change in sender reputation, such as a spike in complaints, might trigger Microsoft to suppress FBL reports as a spam mitigation measure.
Key opinions
- Data Privacy Impact: Data privacy considerations could cause changes in how Microsoft processes and shares FBL data.
- Common FBL Issues: Misconfiguration, blocklisting, and network glitches are potential causes of FBL report disruption.
- Reputation-Based Suppression: Sudden changes in sender reputation can trigger Microsoft to suppress FBL reports.
Key considerations
- Adapt to Privacy Standards: Stay informed and adapt to evolving data privacy standards to minimize disruptions.
- Proactive Monitoring: Proactively monitor deliverability metrics to identify and resolve potential issues with FBL reception.
- Maintain Sender Reputation: Ensure a consistent sender reputation to avoid being flagged for spam mitigation measures.
Expert view
Expert from Word to the Wise explains that data privacy considerations can lead to changes in how Microsoft processes and shares FBL data, potentially causing temporary disruptions or delays in receiving reports. She highlights the importance of adapting to evolving privacy standards.
30 Dec 2021 - Word to the Wise
Expert view
Expert from Spam Resource emphasizes that sudden changes in sender reputation can trigger Microsoft to temporarily suppress FBL reports as part of their spam mitigation efforts. A sudden spike in complaints or a sudden drop in engagement can trigger this.
6 Sep 2021 - Spam Resource
What the documentation says
4 technical articles
Microsoft's documentation highlights several factors impacting FBL reception. Participating in Outlook.com's FBL requires implementing SPF, DKIM, and DMARC authentication. Monitoring the SNDS portal provides insights into mail traffic and complaint rates, indicating potential FBL issues. Ensuring proper configuration of systems to receive and process feedback data is crucial, alongside reviewing FBL documentation for troubleshooting. The RFC documentation explains the ARF format, emphasizing clear identification and processing of feedback loops, suggesting any changes by Microsoft to its FBL processing might affect ARF parsing.
Key findings
- Authentication Required: Participation in Outlook.com FBL necessitates the implementation of SPF, DKIM, and DMARC.
- SNDS Monitoring: Microsoft SNDS provides data on mail traffic and complaint rates to diagnose FBL problems.
- System Configuration: Properly configured systems are essential for receiving and processing FBL data.
- ARF Format: Changes to Microsoft's FBL processing might affect the parsing of ARF reports.
Key considerations
- Implement Authentication: Ensure proper implementation of SPF, DKIM, and DMARC for FBL participation.
- Utilize SNDS: Regularly monitor the SNDS portal for insights into mail traffic and potential issues.
- Review Configuration: Verify that systems are correctly configured to receive and process FBL data.
- Troubleshooting: Consult FBL documentation for troubleshooting tips and best practices.
Technical article
Documentation from Microsoft SNDS recommends monitoring the SNDS portal to get the most up-to-date information about your mail traffic including complaint rates, which may indicate FBL issues.
14 Aug 2022 - Microsoft SNDS
Technical article
Documentation from RFC Editor (RFC 5965) explains the ARF format for FBL reports, emphasizing the need for clear identification and processing of feedback loops. If Microsoft made changes to its FBL processing, it might have temporarily affected the ARF parsing.
15 Apr 2025 - RFC Editor
Are abuse reports and feedback loops (FBLs) still useful in email marketing, and how do they work with different email clients?
Are there any current issues with Yahoo FBL emails?
How can I accurately monitor complaint rates for email marketing using Google Postmaster Tools, Yahoo FBL, and my ESP?
How can I contact Yahoo's postmaster team for FBL access and troubleshoot setup issues?
How did Yahoo update their FBL ARF format and how did it impact ESPs?
