Sender ID Framework SPF Record Wizard

News has it that Microsoft in September will make it mandatory for mail
servers sending mail to MSN.com and Hotmail.com to comply with their Secure
ID framework. Currently, Microsoft's technical support for this soon to be
requirement is non-existent. You can find RFCs and technical documents at
http://www.microsoft.com/mscorp/safety/technologies/senderid/default.mspx

But as far as support...it doesn't exist.

The above URL does provide a link to a Sender ID Framework SPF Record
Wizard (
http://www.anti-spamtools.org/SenderIDEmailPolicyTool/Default.aspx ), but
the wizard itself is flawed. For starters, it doesn't work with Internet
Explorer 5! Every page of the wizard generates run-time errors.

For instance on steps 2 and 3, the following code line is faulty:

var oPopup = window.createPopup();

Then when one moves from step 3 to step 4, the following code (marked belwo
with -> ) is faulty, and prevents the user from proceding to step 4:

function RegularExpressionValidatorEvaluateIsValid(val) {
var value = ValidatorGetValue(val.controltovalidate);
if (ValidatorTrim(value).length == 0)
return true;
-> var rx = new RegExp(val.validationexpression);
var matches = rx.exec(value);
return (matches != null && value == matches[0]);

And on Step 3, you receive a red warning message about "One or more domain
names have invalid syntax" whenever you enter a domain that begins with a
number, such as "911.com" This is for the field marked, "Enter any
additional domain names whose MX records refer to valid outbound e-mail
servers for pc-shareware.com (one domain name per line)."

Then on step 4, the instructions state, "Your SPF record must be published
in DNS records of type TXT" but the instructions fail to indicate what
RECORD NAME the administrator should use when creating the new record!

Microsoft should stop arrogantly demanding compliance from email providers
around the world while they at the same time providing near zero support and
few instructions on how to become compliant. Their buggy web site, and lack
of simple instructions written in plain English points to this Sender ID
effort becoming a massive failure.


.

Relevant Pages

  • Re: Newsgroups: MS should WARN us FIRST not to use real email addresses here!!
    ... I purchase and use a product from Microsoft, ... NOT their responsibility to provide me with proper instructions on how to ... up for newsgroups because it isn't necessary anyway??? ... and therefore the necessity of having to enter an email ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Newsgroups: MS should WARN us FIRST not to use real email addresses here!!
    ... NOT their responsibility to provide me with proper instructions on how to ... "it is your opinion that Microsoft ... From the research I have done since, it seems that these newsgroups are ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Newsgroups: MS should WARN us FIRST not to use real email addresses here!!
    ... NOT their responsibility to provide me with proper instructions on how to ... "it is your opinion that Microsoft ... From the research I have done since, it seems that these newsgroups are ... and therefore the necessity of having to enter an email ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Newsgroups: MS should WARN us FIRST not to use real email addresses here!!
    ... NOT their responsibility to provide me with proper instructions on how to ... "it is your opinion that Microsoft ... From the research I have done since, it seems that these newsgroups are ... and therefore the necessity of having to enter an email ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • MS "Help" messages print far too small.
    ... We have to print out the instructions so that we can ... Here's some of the double talk we have uncovered in Microsoft Windows ... To Set Printer Properties - this option is available only if folders are set ... To Set Printer Defaults - only if you have the Manage Printers permission. ...
    (microsoft.public.windowsxp.general)
Loading