
Email Best Practices 101
This email boot camp will help you to increase the ROI of your email operations with 15 proven tactics for boosting email deliverability.
The Sender Policy Framework (SPF), is a technical standard and email authentication technique that helps protect email senders and recipients from spam, spoofing, and phishing.
Specifically, it defines a way to validate an email message was sent from an authorized mail server in order to detect forgery and to prevent spam. It was designed to supplement SMTP, the basic protocol used to send email, because SMTP does not itself include any authentication mechanisms.
SPF establishes a method for receiving mail servers to verify that incoming email from a domain was sent from a host authorized by that domain’s administrators. It piggybacks on the well-established Domain Name System (DNS). In general terms, the process works like this:
An SPF record is included in an organization’s DNS database. An SPF record is a specially-formatted version of a standard DNS TXT record. An SPF record looks something like this:
mydomain.com TXT "v=spf1 include:myauthorizeddomain.com include:sparkpostmail.com ~all”
Reading left-to-right in plain English, this record is saying that any email that claims to be from “mydomain.com” should be validated with SPF (that’s the “v=spf1” prefix to the record). It then specifies that the SPF records for “myauthorizeddomain.com” and “sparkpostmail.com” also should be included when validating email from mydomain.com (those are the parts labeled “include:”). In practical terms, that usually is done to indicate that the other domains authorized to send email on its behalf. Finally, the record concludes by stating that any other servers claiming to send mail should be flagged as questionable, and possibly failing, the SPF test (“~all”).
SPF records can be more complicated than this example, but the basic mechanism remains the same.
SPF, DKIM, and DMARC are all standards that enable different aspects of email authentication. They address complementary issues.
If you are a business sending commercial or transactional email, you definitely need to implement one or more forms of email authentication to verify that an email is actually from you or your business. Properly configuring email authentication standards like SPF is one of the most important steps you can take to improve your deliverability. However, SPF by itself only goes so far; SparkPost and other email experts recommend also implementing DKIM and DMARC to define a more complete email authentication policy.
Yes. SparkPost implements and adheres to email authentication standards including SPF. In fact, SparkPost handles the SPF part of that automatically, so all email from your account is already SPF-compliant.
SparkPost’s free email tools for developers make working with email authentication standards like SPF easy. Our SPF Inspector lets you quickly check who’s authorized to send email for your domain. And our SPF Builder is an easy way to create a working SPF record for your domain.
Learn more about SPF with these resources from SparkPost’s email experts and elsewhere on the web.
Learn more about how to configure and use SPF with the SparkPost service in the SparkPost Support Center.
Develop your email industry expertise and master best practices with SparkPost’s email resources.
This email boot camp will help you to increase the ROI of your email operations with 15 proven tactics for boosting email deliverability.
Learn how third-party data shows the deliverability difference between SparkPost and also-ran cloud service providers yields hard, bottom-line benefits.
This practical course is a great way to get started understanding email deliverability and how to measure email performance.
Try SparkPost and see how we deliver far more value than the competition.