Craig Whitmore wrote:
Be carefull. Sender-ID is not SPF.. Microsoft took SPF and added some changes to it (which alot of people in the SPF "community" think make it worse than simple SPF by itself.). Sender-ID has their own records (see nslookup -type=txt spam.co.nz). but will use the SPF records if there is no SenderID record (spf2.0) and this may make Sender-ID give false possitives at rare times. (the reusage of Microsoft of the SPF tag is what SPF people don't like), but when everyone starts using the new RR of "SPF" instead of TXT for SPF., microsoft can do what they want, as it was given for SPF not Sender-ID).
$ host -t txt spam.co.nz spam.co.nz descriptive text "v=spf1 ip4:219.88.242.0/27 -all" spam.co.nz descriptive text "spf2.0/pra ip4:219.88.242.0/27 -all" spam.co.nz descriptive text "Professional DNS Management by Orcon Internet" $ host -t txt microsoft.co.nz {nothing} $ host -t txt microsoft.com microsoft.com descriptive text "v=spf1 mx redirect=_spf.microsoft.com" $ host -t txt _spf.microsoft.com _spf.microsoft.com descriptive text "v=spf1 ip4:213.199.128.139 ip4:213.199.128.145 ip4:207.46.50.72 ip4:207.46.50.82 ip4:131.107.3.116 ip4:131.107.3.117 ip4:131.107.3.100 ip4:131.107.3.108 a:delivery.pens.microsoft.com a:mh.microsoft.m0.net mx:microsoft.com ?all" Humm... -- Juha