Microsoft's sender reputation data portal (Smart Network Data Services, or SNDS) and their ISP feedback loop mechanism (Junk Mail Reporting Program, or JMRP), are undergoing a transition. The SNDS website relaunched in June, 2026, with updated access controls and some changes to what data is shared and how it is shared.
I'll likely cover that in more detail at some point in the future. For now, I'm going to hang back a bit, and wait for the shakedown cruise to complete. They're clearly still working the bugs out, and I'll wait for things to get a bit more stable and revised before diving in, myself. So far, multiple folks are telling me stories of having trouble getting access to IP ranges because of confirmation emails not being received. Registration dates and feedback loop feeds seem to be buggy for some folks, as well.
So, if you're having trouble....know that you're not alone. And know that Microsoft is undoubtably working their way through any issues. If you can, wait, and try again, in a few days, to see if your particular issue has been addressed.
One thing I will highlight is that if you were relying on the return-path address in a spam complaint feedback loop report (JMRP), you'll need to find another way to identify campaign and recipient info. Other folks have suggested that the message-ID header might be a safe place to encode this information. (And as always, you don't want to make it obviously human decipherable, or somewhere, someday, some bad guy will try to do something silly with it.)
Stay tuned…as I learn more, I'll do my best to share it. And thank you, Microsoft friends, for your hard work to improve SNDS. I'm very much looking forward to seeing what comes.
Microsoft's sender reputation data portal (Smart Network Data Services, or SNDS) and their ISP feedback loop mechanism (Junk Mail Reporting Program, or JMRP), are undergoing a transition. The SNDS website relaunched in June, 2026, with updated access controls and some changes to what data is shared and how it is shared.
I'll likely cover that in more detail at some point in the future. For now, I'm going to hang back a bit, and wait for the shakedown cruise to complete. They're clearly still working the bugs out, and I'll wait for things to get a bit more stable and revised before diving in, myself. So far, multiple folks are telling me stories of having trouble getting access to IP ranges because of confirmation emails not being received. Registration dates and feedback loop feeds seem to be buggy for some folks, as well.
So, if you're having trouble....know that you're not alone. And know that Microsoft is undoubtably working their way through any issues. If you can, wait, and try again, in a few days, to see if your particular issue has been addressed.
One thing I will highlight is that if you were relying on the return-path address in a spam complaint feedback loop report (JMRP), you'll need to find another way to identify campaign and recipient info. Other folks have suggested that the message-ID header might be a safe place to encode this information. (And as always, you don't want to make it obviously human decipherable, or somewhere, someday, some bad guy will try to do something silly with it.)
Stay tuned…as I learn more, I'll do my best to share it. And thank you, Microsoft friends, for your hard work to improve SNDS. I'm very much looking forward to seeing what comes.
Comments
Post a Comment
Comments policy: Al is always right. Kidding, mostly. Be polite, please and thank you.