Summary
Resolving SNDS issues with IPs already added to another account involves a multi-faceted approach. First, ensure all IPs are authorized in SNDS and no longer sending mail. If the IPs were inherited, provide proof of ownership to Microsoft SNDS support. Correct rDNS records, WHOIS information, and verify FBL and email authentication settings (SPF, DKIM, DMARC). Adhere to Microsoft’s policies and contact SNDS support directly if problems persist or for IP reassignment assistance. Discrepancies often stem from outdated records or shared IP history.
Key findings
- IP Authorization is Key: Ensuring all IPs are authorized within the SNDS Access Control panel is a primary step for managing your feed.
- Ownership Verification: Providing documented proof of IP ownership is critical for inherited IPs to facilitate reassignment by Microsoft.
- rDNS and WHOIS Accuracy: Maintaining accurate rDNS and WHOIS records is essential to avoid misattribution of IPs in SNDS.
- FBL Configuration: Properly configured feedback loops and email authentication mechanisms (SPF, DKIM, DMARC) prevent misattribution of feedback data.
- Microsoft Policies: Adhering to Microsoft's privacy policies and usage guidelines is crucial to prevent access restrictions and complications.
Key considerations
- Sending Practices: Ensure your sending practices comply with Microsoft’s policies to facilitate the reassignment process.
- Documentation is Vital: Gather and provide detailed information about your IP block’s history and ownership to Microsoft’s SNDS support.
- Contact Support Directly: For persistent issues, contact Microsoft SNDS support with detailed information about your IP block's history and ownership.
- Address Historical Data: Recognize that an IP showing as used by another account may reflect historical data; request a reputation reset if needed.
- Check Non-Usage: Ensure the IP address is no longer sending mail before attempting to remove or reassign it.
What email marketers say
10 marketer opinions
To resolve SNDS issues with IPs already added to another account, several key steps are recommended. First, ensure all IPs in your SNDS feed are authorized in the Access Control panel; unauthorized IPs can restrict feed management. If you've inherited the IP, provide proof of ownership to Microsoft SNDS support. Verify and correct rDNS records to match your domain, and update WHOIS database information to accurately reflect your organization. Ensure your feedback loop (FBL) is properly configured and email authentication (SPF, DKIM, DMARC) is correctly implemented. Contact SNDS support for persistent issues, providing detailed history and documentation of IP ownership.
Key opinions
- IP Authorization: Unauthorized IPs in SNDS feeds limit management capabilities; ensure all IPs are authorized via the Access Control panel.
- Proof of Ownership: If inheriting IPs, provide documented proof of ownership to Microsoft SNDS support for reassignment.
- rDNS Records: Incorrect or outdated rDNS records can cause misattribution of IPs; verify and correct these records to match your domain.
- WHOIS Database: Outdated or incorrect information in the WHOIS database can cause issues; ensure your organization's details are accurately updated.
- Feedback Loop (FBL): Improperly configured FBLs can lead to misattribution of feedback; verify proper setup and authentication.
Key considerations
- Compliance: Ensure your sending practices are compliant with Microsoft's policies before requesting IP reassignment.
- Documentation: Gather all relevant documentation regarding IP ownership and history before contacting SNDS support.
- Propagation Time: Allow sufficient time for DNS record changes (rDNS) to propagate across the internet.
- SNDS Support: For persistent issues, direct communication with Microsoft SNDS support is crucial for resolution.
- Email Authentication: Properly configured SPF, DKIM, and DMARC records are essential for correct FBL operation and IP reputation.
Marketer view
Email marketer from Email Marketing Forum suggests that if you're encountering issues after acquiring IPs, verify that your organization's details are correctly updated in the Whois database. This helps Microsoft accurately associate the IP with your account. Outdated information may lead to conflicts.
3 Aug 2021 - Email Marketing Forum
Marketer view
Marketer from Email Geeks explains that you cannot delete IPs in the feed until all of them are authorized again. Identify all unauthorized IPs (absent in the Access Control panel) and authorize them via the Request Access panel.
3 Apr 2023 - Email Geeks
What the experts say
2 expert opinions
Resolving SNDS issues involving IPs associated with a previous owner requires clear documentation of ownership transfer and updated IP registration information. Contact Microsoft SNDS support with proof of ownership to initiate reassignment. Ensure your sending practices comply with Microsoft's policies. Verify and update WHOIS records to accurately reflect your organization's ownership of the IP range, as discrepancies can cause misattribution and reporting issues.
Key opinions
- Documentation of Ownership: Clear documentation proving the transfer of IP ownership is crucial for initiating the reassignment process with Microsoft SNDS support.
- Accurate WHOIS Records: Discrepancies in SNDS data often arise from inaccurate or outdated WHOIS records, which must be verified and updated to reflect current ownership.
Key considerations
- Compliance with Policies: Demonstrate that your sending practices comply with Microsoft's policies to facilitate the IP reassignment process.
- Contacting SNDS Support: Contacting Microsoft SNDS support is essential for resolving IP ownership issues, especially after verifying and updating WHOIS records.
Expert view
Expert from Word to the Wise explains that discrepancies in SNDS data often arise from inaccurate or outdated IP registration information. Verify that your WHOIS records are up-to-date and correctly reflect your organization's ownership of the IP range. Discrepancies can cause Microsoft to misattribute the IP, leading to SNDS reporting issues. Correcting these records and contacting SNDS support are crucial steps.
8 Oct 2022 - Word to the Wise
Expert view
Expert from Spam Resource explains that if you have inherited an IP range that is still associated with a previous owner in SNDS, the first step is to ensure you have clear documentation proving the transfer of ownership. Contact Microsoft SNDS support and provide this documentation to initiate the reassignment process. Be prepared to demonstrate that your sending practices align with Microsoft's policies.
23 Feb 2024 - Spam Resource
What the documentation says
4 technical articles
Resolving SNDS issues with IPs already added to another account, according to Microsoft SNDS documentation, involves several steps. First, ensure the IP is no longer sending mail before attempting removal via the SNDS interface. If the IP remains associated with another account or the data reflects historical usage, contact Microsoft support for assistance. Proper authorization of IP ranges is crucial for monitoring in SNDS. Adhering to Microsoft's privacy policies and usage guidelines is mandatory to avoid access restrictions and complications in IP ownership disputes.
Key findings
- IP Removal Process: Ensure the IP is no longer sending mail before attempting removal through the SNDS interface.
- Historical Data: IP association with another account may reflect historical data, requiring a reputation reset or direct Microsoft intervention.
- IP Authorization: Proper authorization of IP ranges is necessary to monitor them in SNDS.
- Policy Adherence: Adherence to Microsoft's privacy policies and usage guidelines is mandatory for SNDS usage.
Key considerations
- Contacting Support: Contact Microsoft support directly if IP removal fails or issues persist.
- Verifying Non-Usage: Confirm the IP is not actively sending mail before initiating the removal process.
- Proof of Ownership: Be prepared to provide proof of ownership when contacting Microsoft support for IP-related issues.
- Avoiding Violations: Avoid improper usage and attempts to bypass security measures to prevent access restrictions.
Technical article
Documentation from Microsoft SNDS Documentation clarifies that you must authorize the IP ranges you intend to monitor in SNDS. If the IPs are already authorized under another account, follow the IP removal process after verifying non-usage. Contact support with proof of ownership if issues persist.
10 Aug 2024 - Microsoft SNDS Documentation
Technical article
Documentation from Microsoft SNDS Documentation notes that you must adhere to Microsoft's privacy policies and usage guidelines when using SNDS. Improper usage or attempts to bypass security measures can lead to access restrictions and may complicate IP ownership disputes.
23 Nov 2022 - Microsoft SNDS Documentation
Can ESP clients sign up for Validity FBL and how do they validate their IPs/domains?
How accurate is Microsoft SNDS data for deliverability monitoring?
How accurate is SNDS and Google Postmaster Tools reputation data?
How can I monitor Microsoft reputation on a shared IP and what are third-party DKIM signatures?
How do I grant someone access to my SNDS account?
What are the limitations of Amazon SES regarding Microsoft SNDS access and is there a workaround?
