Sender Policy Framework (SPF) Records are used to validate the sources of sent email for a domain to ensure they are legitimate messages and not spam. The purpose of an SPF Record is to prevent email forgery. An SPF Record allows you to ensure that emails using your domain are authorized to do so. SPF Records are configured on your authoritative DNS server in the configuration settings and are a necessary requirement to successfully use our Email-to-fax service. Our Email-to-fax service has several steps that must complete for success. The very first step in the process is to check the SPF Record of the sending email address (domain). If the SPF Record check passes, the process moves on to the next steps of converting the file to necessary format and sending the fax. If the SPF Record check fails, the process stops and no further action occurs; hence, the fax you are attempting to send will fail. Therefore, it is imperative that you correctly configure your SPF Record for your domain. Since a domain name owner publishes an SPF record in DNS that declares which server(s) are permitted to send email on behalf of that domain, we use this information to essentially authenticate that the email is authorized to send on the domain's behalf. This article aims to assist you in understanding SPF Records and aid you in configuring and verifying your SPF Record. The information contained in this article may differ slightly for your mail server but the principles will still apply.
The first thing you will need to determine is the number of SMTP servers that will be sending as @yourdomain.com. For example, if firstname.lastname@example.org is sending via Comcast SMTP servers (smtp.comcast.net), your SPF record will need to include IP 22.214.171.124; or to put it in context, ip4:126.96.36.199 (Comcast SMTP Server IP address). Additionally, if there are IP ranges in which mail can pass through, you will need to add those appropriate ranges. This information can typically be obtained through your email provider or system administrator if you do not readily have this information available. An IP range will have a forward slash at the end of the IP address. For example, Google's SPF Record has this range: ip4:188.8.131.52/16.
The most common (easiest) entries you will need for your SPF records will closely mimic the VoIP Innovations eFax record, which contain basic A, MX, and IP listings and will be sufficient in most applications. Think of these as attributes. An SPF Record can contain any combination of these attributes meaning it can have one or several of them. For example, an SPF Record can contain an mx record, a single IP address, a range of IP addresses, a domain name, etc. Note that SPF Records will end with one of several methods, each containing the word 'all'. These methods determine what happens if the email is received from a server not listed in the SPF Record. These methods are '-all', '~all', '?all', and '+all'. The recommended method is '-all' however, you may need to use '~all' for success. Here is a description of each method: -all Fails (email is viewed as a forgery)
~all Soft Fail (the email is possibly a forgery, but the domain may be in transition) ?all Neutral (cannot determine if the email is a forgery or not) +all Pass (this is never a forgery; do not use this method as it is only listed here for completeness) Below are example SPF Records for Gmail and Apple as well as VoIP Innovations eFax Apple v=spf1 ip4:184.108.40.206/8 ~all
VoIP Innovations eFax v=spf1 mx ip4:220.127.116.11 ip4:18.104.22.168 a:titaniumvfax.com ~all
Gmail* v=spf1 redirect=_spf.google.com
*The Gmail SPF is somewhat different from the others as the record redirects multiple times ultimately ending in an IP check as seen viahttp://emailstuff.org/spf/check/gmail.com* The following is an example of how our service checks for an SPF record when an email-to-fax is sent from Gmail, and how it relates to the SPF and MX records. Source number for email@example.com is 4125551212 Sender SPF record: ['v=spf1 redirect=_spf.google.com'] SPF record allows soft-fail, checking all Received headers Checking Header 1 Host: mail-wg0-f41.google.com HELO: mail-wg0-f41.google.com IP: 22.214.171.124 Check Result: pass SPF Check for sender passed As you can see from this, our mail server is verifying the SPF Record for Gmail. This record passes for two reasons. First, the SMTP server belongs to the sending domain. Second, the IP of the SMTP server it is sent from (mail-wg0-f41.google.com) reverses to IP 126.96.36.199 which is within the range 188.8.131.52/16 that is highlighted below. (The IP range 184.108.40.206/16 shown here means the Host minimum is 220.127.116.11 and the Host maximum is 18.104.22.168; thus 22.214.171.124 is within the range.)
Once you have configured your SPF Record, you will need to allow time for it to propagate.
The amount of propagation time is determined by the Time to Live (TTL) parameter you have configured in the server. The TTL is the length of time your record will remain in cache on systems requesting your record. Do not expect a previously failed SPF Record to take immediate effect once you have updated the record. The new record will not update until the current TTL has expired. There are a few tools available to check an SPF record so take advantage of those to assist you. Once such tool is MX Toolbox. When using this site, you will need to enter the domain for which you are checking the SPF Record (for example,
titaniumvfax.com, google.com, etc.) and click the 'MX Lookup' button to get the results.
Once you have the results, click the 'spf' link to get the SPF Record as shown below
From here, using titaniumvfax.com as an example, you will notice the above-mentioned A, MX, and IP records which have now been put into context.
MX: if you are sending from an IP listed as an MX record from your domain, this will pass. IP4: as shown, if the SMTP server you are sending through matches the IP or IP range listed, this will pass. A: If the IP reverses to yourdomain.com, this will pass as well.