Summary
Updating the complaint address for JMRP FBLs in SNDS is complex and often requires more than just a simple edit. A common workaround is to delete the existing feed and recreate a new one, which makes it crucial to document current settings beforehand. Access issues can arise if there's a mismatch between the user account and the registered owner of the IP ranges. Microsoft support is often needed to verify ownership and grant necessary permissions, but response times can be slow, so persistence is key. Ensuring that Abuse Reporting Format (ARF) reports are correctly formatted is also critical. Additionally, general email infrastructure health, proper complaint feedback loop management, SNDS data monitoring, full email authentication (DKIM, SPF, DMARC), and avoiding blacklists are essential for maintaining a good sender reputation and preventing deliverability problems. While programmatic updates via APIs could be an option, their availability and documentation are uncertain.
Key findings
- Feed Recreation: Directly updating feeds is usually not possible; recreating the feed is a common workaround.
- Ownership Issues: Access problems might stem from mismatches between the user account and registered IP owner; verify ownership with Microsoft.
- Support Reliance: Microsoft support is often required, but be prepared for potential delays.
- ARF Importance: Correctly formatted ARF reports are critical for proper FBL functioning.
- Email Health: Overall email infrastructure health is vital for deliverability.
- Authentication Matters: Complete authentication (DKIM, SPF, DMARC) is crucial.
Key considerations
- Document Beforehand: Document all settings before deleting and recreating feeds.
- Be Persistent: Be prepared to follow up with Microsoft support due to potential delays.
- Verify Account: Verify the user account has the required administrative privileges and IP ownership.
- Check ARF: Review and validate your ARF implementation to ensure correct formatting.
- Monitor SNDS: Regularly monitor SNDS data for issues and ensure you are adhering to Microsoft's sending policies.
- Avoid Blacklists: Ensure that your IPs and domains are not blacklisted.
What email marketers say
7 marketer opinions
Updating the complaint address for JMRP FBLs in SNDS can be challenging. Directly updating feeds might not be supported, often requiring deletion and recreation. Contacting Microsoft support is advised, but persistence may be necessary due to potential delays. While APIs for programmatic updates are a possibility, they may be undocumented or unavailable. Monitoring SNDS data, properly managing complaint feedback loops, maintaining a healthy email infrastructure, and ensuring full email authentication (DKIM, SPF, DMARC) are crucial for maintaining sender reputation and effective communication with Microsoft's services.
Key opinions
- Feed Updates: Direct updates to SNDS feeds may not be possible; recreation might be necessary.
- Support Delays: Microsoft support response times can be slow, requiring persistence.
- API Option: Programmatic updates via API are a possibility, but availability is uncertain.
- Monitoring Importance: Regularly monitor SNDS data to identify and address deliverability issues.
- FBL Management: Properly managing complaint feedback loops is critical for sender reputation.
- Infrastructure Health: Maintaining a healthy email infrastructure impacts effective communication with Microsoft.
- Authentication: Ensure full email authentication (DKIM, SPF, DMARC) to avoid deliverability problems.
Key considerations
- Document Settings: Before deleting and recreating feeds, document current settings.
- Detailed Requests: Provide detailed information when contacting Microsoft support.
- ARF Formatting: Ensure Abuse Reporting Format (ARF) reports are correctly formatted.
- Review Guidelines: Ensure sending practices are aligned with Microsoft’s guidelines.
- Blacklist Checks: Regularly check IPs against blacklists.
Marketer view
Email marketer from EmailGeek Forum shares that based on past experiences, the SNDS system may not support direct updates to existing feeds. The recommended workaround is often to delete the existing feed and recreate a new one with the updated complaint address. Before doing so, it's crucial to document your current settings to ensure a smooth transition.
10 Feb 2023 - EmailGeek Forum
Marketer view
Email marketer from Reddit shares that contacting Microsoft support for SNDS issues can sometimes be slow. They recommend being persistent and providing as much detail as possible in your initial support request. Also, check the SNDS forums for known issues or workarounds.
26 Jan 2022 - Reddit
What the experts say
3 expert opinions
Updating the complaint address for JMRP FBLs in SNDS is often problematic due to limitations in the system. Direct updates to the feed are typically not possible, requiring you to recreate the feed. Access issues may stem from a mismatch between the user account and the registered owner of the IP ranges. Ensuring correctly formatted ARF reports is also crucial for the process.
Key opinions
- No Direct Updates: Directly updating JMRP SNDS feeds is generally not possible; recreation is required.
- Account Mismatch: Access issues may arise from a mismatch between the user account and the registered IP owner.
- ARF Formatting: Correctly formatted ARF reports are crucial for updating complaint addresses.
Key considerations
- Verify Ownership: Confirm the user account has administrative privileges and is the original registrant of the IPs.
- Contact Support: Contact Microsoft support to confirm ownership if necessary.
- Review ARF Specs: Review ARF specifications and validate your implementation to ensure correct formatting.
Expert view
Expert from Email Geeks explains there's no way to update a JMRP SNDS feed and that you have to break it and recreate it because that functionality simply doesn’t exist.
24 May 2022 - Email Geeks
Expert view
Expert from Word to the Wise Forums suggests that issues accessing or updating SNDS settings might stem from a mismatch between the user account and the registered owner of the IP ranges. Verify that the account used has administrative privileges and is the original registrant of the IPs. They advise contacting Microsoft support to confirm ownership.
16 May 2022 - Word to the Wise
What the documentation says
3 technical articles
According to Microsoft's documentation, updating the complaint address for JMRP FBLs in SNDS involves ensuring the user account has appropriate permissions, potentially requiring contact with Microsoft support to verify ownership. It's also vital to review JMRP program requirements, properly configure the FBL, and ensure correctly formatted ARF reports are being sent to Microsoft. Providing detailed information to support can expedite the process.
Key findings
- Permissions: User account permissions must be adequate to manage the SNDS feed.
- Support Contact: Contacting Microsoft support is often necessary, especially for ownership verification.
- FBL Configuration: Proper FBL configuration and compliance with JMRP requirements are essential.
- ARF Reports: Correctly formatted Abuse Reporting Format (ARF) reports must be sent to Microsoft.
Key considerations
- Verify Ownership: Ensure the logged-in user is the original owner or has the necessary permissions.
- Provide Details: Provide detailed information (IP ranges, error messages) when contacting support.
- Review JMRP: Review and adhere to all JMRP program requirements.
- Validate ARF: Validate ARF report formatting to ensure compliance.
Technical article
Documentation from Microsoft Documentation suggests reviewing the requirements for the JMRP program and ensuring that the FBL is properly configured. The complaint feedback loop (FBL) setup is crucial, and you should verify that you're sending the correct Abuse Reporting Format (ARF) reports to Microsoft.
23 Nov 2022 - Microsoft Documentation
Technical article
Documentation from Microsoft Support states users facing issues with JMRP and SNDS should contact Microsoft support via their online portal. Response times may vary, but provide detailed information about the problem, including IP ranges and error messages, to expedite the process.
23 Feb 2023 - Microsoft Support
How accurate is Microsoft SNDS data for deliverability monitoring?
How accurate is SNDS and Google Postmaster Tools reputation data?
How can I gain access to Yahoo's Campaign and Performance Feeds as an ESP?
How critical are Feedback Loops (FBLs) for sender reputation, and how often do they require re-enrollment?
How do ESPs collect Yahoo FBL data using double DKIM signing?
How do I get my emails out of spam for Hotmail and Outlook?
