Sender Policy Framework and Sender ID: Second in 3-Part Series on E-Mail Authentication
E-mail authentication and its importance has been widely discussed in the media, in blogs and at industry trade shows. But before you embark on an e-mail authentication program, you will need to separate fact from fiction. In this three-part series, Knowledge Center contributor Ellen Siegel explains what e-mail authentication is, why e-mail authentication is important, how e-mail authentication works and what exactly you need to do to authenticate your e-mail.
Editor's Note: In Part 1 of her three-part series on e-mail authentication, Knowledge Center contributor Ellen Siegel shared a comprehensive, high-level overview of e-mail authentication. Here, in Part 2, Ellen delves into the functionality and implementation details of Sender Policy Framework (SPF) and Sender ID authentication. In Part 3, Ellen delves into the functionality and technical details of Domain Keys Identified Mail (DKIM).As discussed in Part 1 of this three-part e-mail authentication series, e-mail authentication is a way of associating a verifiable identity with an e-mail. The industry has settled on two basic approaches to identity verification. The first approach is path-based, based on the identity of the mail server that delivers the message. The second approach is cryptographic, relying on the fact that the private encryption key used to create a message's digital signature would exist only on authorized mail servers. In the interest of clarity, this article will ignore some of the less common options and focus on the most common configurations.