reverse DNS is problematic for exactly the reason you allude to, namely that ISPs rather than domain owners are in technical control, which puts small users (I is one!) at a big disadvantage. For these reasons rather than rDNS Caller ID instead uses a new forward query to the domain purportedly responsible for a message. If you can admin your incoming MX records, then you can admin your Caller ID outgoing info: the control is in the same place. You can find gruesome details from http://www.microsoft.com/spam.
My personal opinion is that you are not reading this correctly, and are indeed reading too much into this. I cannot and so will not attempt to reinterpret the actual contents of the license, but I suggest you give it another careful reading.
The technical specifications for Caller ID for E-mail and the larger Coordinated Spam Reduction Inititative can be found through links on the page http://www.microsoft.com/spam.
Slashdot Mirror
reverse DNS is problematic for exactly the reason you allude to, namely that ISPs rather than domain owners are in technical control, which puts small users (I is one!) at a big disadvantage. For these reasons rather than rDNS Caller ID instead uses a new forward query to the domain purportedly responsible for a message. If you can admin your incoming MX records, then you can admin your Caller ID outgoing info: the control is in the same place. You can find gruesome details from http://www.microsoft.com/spam.
My personal opinion is that you are not reading this correctly, and are indeed reading too much into this. I cannot and so will not attempt to reinterpret the actual contents of the license, but I suggest you give it another careful reading.
The technical specifications for Caller ID for E-mail and the larger Coordinated Spam Reduction Inititative can be found through links on the page http://www.microsoft.com/spam.