nospamproxy.de [1,2] has some good articles on anti-spam technologies and points out, that CallerID works in a very similar way to SPF, RMX and other protocols to verify the sending host. Microsoft introduced its CallerID at hotmail.com as you can test yourself:
# host -t txt _ep.hotmail.com
So from the technical side it seems that the CallerID(ea) is probably even behind what SPF is capabale of [3,4,5]. On the other hand, some argue, that Microsoft might to \”acknowledge Open Source without accepting some of the risks of being truly Open Source might bring\”:
This product may incorporate intellectual property owned by Microsoft Corporation. If you would like a license from Microsoft, you need to contact Microsoft directly [3].
From that perspective, the patent claims by Microsoft might be only defensive [4]. Some searching for latest patents by Microsoft (Title or Abstract: spam, Applicant: Microsoft) only reveals four related patents, one of them published in January 2004 [6].
If – on a legislatory level – Microsoft intends to push its technology, one should point out to the governmental experts and commissions that there are already technical alternatives that should be taken in account as well.
[1] http://www.nospamproxy.de/EN/rulez-ms.htm
[2] http://www.nospamproxy.de/EN/rulez-spf.htm
[3] http://lists.essential.org/pipermail/ecommerce/2004q1/001206.html
[4] http://www.newsforge.com/software/04/02/26/1448253.shtml
[5] http://www.mail-archive.com/cobalt-users@list.cobalt.com/msg61809.html
[6] http://l2.espacenet.com/espacenet/viewer?PN=EP1376427&CY=ch&LG=en&DB=EPD
