Mailing List Archive

Looks like Microsoft[1] has implemented or is testing its implementation
of its SPF-like Caller-ID[2] on its domains. If this is a permanent
thing, there should probably be some rules developed to support it, and
that'll spell the end of those fake MS "security update" trojans/spams.
Any plans for supporting this within the product?

# nslookup -q=txt _ep.microsoft.com
Server: dns1.courts.state.tx.us
Address: 10.200.10.8

Non-authoritative answer:
_ep.microsoft.com text = "<ep xmlns='http://ms.net/1'
testing='true'><out><m>"
"<mx/><a>213.199.128.160</a><a>213.199.128.145</a><a>207.46.71.29</a><a>
194.121.59.20</a><a>157.60.216.10</a><a>131.107.3.116</a><a>131.107.3.11
7</a><a>131.107.3.100</a>" "</m></out></ep>"

# nslookup -q=txt _ep.hotmail.com
Non-authoritative answer:
_ep.hotmail.com text = "<ep xmlns='http://ms.net/1'
testing='true'><out><m><indirect>list1._ep.hotmail.com</indirect><indire
ct>list2._ep.hotmail.com</indirect><indirect>list3._ep.hotmail.com</indi
rect></m></out></ep>"

-tom

[1] insert rant about nonstandard proprietary almost-SPF Microsoft ate
my baby and causes the seven deadly sins
[2] http://www.microsoft.com/mscorp/twc/privacy/spam_callerid.mspx