<\/span>SNDS and JMRP: the tools Microsoft gives you<\/span><\/h2>\n\n\n\nMicrosoft is one of very few mailbox providers operating a genuine feedback loop. Both tools moved hosts in 2026 \u2014 any guide citing the old addresses is stale.<\/p>\n\n\n\n
\n- SNDS portal:<\/strong>
https:\/\/substrate.office.com\/ip-domain-management-snds\/snds<\/code><\/li>\n\n\n\n- SNDS FAQ:<\/strong>
https:\/\/substrate.office.com\/ip-domain-management-snds\/snds\/faq<\/code><\/li>\n\n\n\n- JMRP enrollment:<\/strong>
https:\/\/substrate.office.com\/ip-domain-management-snds\/snds\/jmrp<\/code><\/li>\n\n\n\n- Outlook.com postmaster:<\/strong>
https:\/\/substrate.office.com\/ip-domain-management-snds\/postmaster<\/code><\/li>\n<\/ul>\n\n\n\nThe legacy sendersupport.olc.protection.outlook.com<\/code> and postmaster.live.com<\/code> paths 308-redirect, but lossily \u2014 old .aspx<\/code> deep links land at a section root. junkmailreporting.microsoft.com<\/code> no longer resolves at all.<\/p>\n\n\n\nSNDS<\/a> is per-IP-range and requires proof of control. Microsoft derives authorization addresses from reverse DNS, WHOIS and the routing table, then mails a request key to postmaster@<\/code> and abuse@<\/code> that domain. Access is not permanent once granted. Microsoft periodically requires the authorizing contact to reauthorize, and the FAQ is explicit about the window: if they do not successfully complete that process within 7 days, they lose access. Access is also removed automatically when the advertised subnets covering your IPs change \u2014 a renumbering or a new upstream announcement can silently drop you out of SNDS.<\/p>\n\n\n\nReading SNDS data<\/h3>\n\n\n\n
The Data page reports per IP, per PST day, with 90-day retention: RCPT and DATA counts, message recipients, sample HELO and MAIL FROM, filter result, complaint rate, sample messages, and flags for virus-infected mail, malware hosting and open-proxy status.<\/p>\n\n\n\n
The color bands apply to the filter result column only<\/strong>, measuring the proportion of that IP’s mail SmartScreen classified as spam: green under 10%, yellow 10% to 90%, red above 90%.<\/p>\n\n\n\nMicrosoft publishes no color-coded complaint rate<\/em> bands \u2014 the most repeated falsehood about SNDS. The FAQ’s only complaint figure is a peer benchmark: more than 30% of IPs sending to Outlook.com keep complaint rates below 0.3%. That is a distribution statistic, not a line Microsoft enforces. Nor does green mean inbox \u2014 IPs routinely show green, low complaints and zero trap hits while landing in Junk.<\/p>\n\n\n\nTrap hit counts are scheduled to be removed from SNDS Data Reports starting 22 July 2026<\/strong>, per the portal’s own announcement \u2014 an upcoming change, not one that has landed yet. Automated Data Access changed too: URLs beginning with the legacy host prefix https:\/\/sendersupport.olc.protection.outlook.com\/snds\/<\/code> were deprecated on 22 June 2026. (Generated links are also reported to expire after 30 days, and several sources describe a replacement REST API with OAuth 2.0; neither is stated in the announcement or the FAQ, so treat both as unconfirmed.)<\/em><\/p>\n\n\n\nJMRP, and what it stopped telling you<\/h3>\n\n\n\n
JMRP forwards a copy of any message a consumer Outlook.com user marks as junk. Enrollment happens inside the SNDS portal and requires the IP verified under your SNDS account \u2014 feeds not linked to one were removed.<\/p>\n\n\n\n
As of mid-2026, JMRP reports are standard ARF and heavily redacted. The complainant’s address is gone, the proprietary X-HmXmrOriginalRecipient<\/code> header is gone, To:<\/code> reads “Undisclosed Recipients,” and the message body is stripped entirely<\/strong>. Downloadable samples were discontinued. Microsoft has published nothing about this; the change was observed in the wild from mid-June 2026 and is corroborated across independent practitioner reports.<\/p>\n\n\n\nIf your suppression automation parsed the recipient address or scraped the body for a customer ID, it is broken. What survives is the Message-ID<\/code>, mapped back to your send log, plus custom X-<\/code> headers you inject at send time \u2014 provided they are not formatted like an email address, or they get redacted too. If you inject nothing today, add an opaque subscriber identifier now.<\/p>\n\n\n\n