The Sender ID Framework is a protocol created by Microsoft to counter email domain spoofing and to provide greater protection against phishing schemes by verifying an email message's sender.
Today, a huge majority of unwanted e-mail contains headers that lie about the origin of the mail. This is true of most spam and substantially all of the virus e-mail that is sent.
Diagram of How Sender ID Works
How Do I Set Up My Sender ID Record?
Sender ID uses the SPF Record
or a SPF2.0 Record. If you have an SPF Record and your email software Purported Responsible Address (PRA) is derives from RFC 5322
and the MAIL FROM (Reverse-Path) derives from RFC 5321
, then you don't need an SPF2.0 record.
If your email software only implements one of the RFCs then you'll need to specify which one by adding a TXT record to you DNS.
If your mail server implements:
|RFC 5322 ONLY:|| TXT/SPF = spf2.0/pra a mx a:mail.unlocktheinbox.com ip4:22.214.171.124 ?all|
|RFC 5321 ONLY:|| TXT/SPF = spf2.0/pra ?all|
|BOTH:|| Your normal SPF Record which you can generate here: Unlock the Inbox SPF Wizard|
The word "BOTH"
above means, that the Sender ID will use the "v=spf1" as defined in SPF
to perform the check and you don't need specific "spf2.0" (PRA) tags. However, if you wanted to add the (PRA) Sender ID records, you can, but it's unnecassary.
You can use Microsoft's Sender ID Wizard to generate your SPF2.0 Records here: Microsoft's Sender ID Wizard
Add those records to both the TXT (TYPE 16) and the SPF (TYPE 99) in DNS (if your able), to learn more about SPF (TYPE 99) - Click Here
Once those records are added to your DNS you can send an email to "firstname.lastname@example.org"
and it will return the results letting you know the status of SPF, DKIM, Sender ID, and Spam Assassin checks.
Source: Unlock The Inbox