Sender Policy Framework (SPF)
The SPF record contains a list of servers and services that are authorized to send email via your domain.
Emails sent from Envoke pass SPF check by default so in many cases adding Envoke to your SPF record is optional, however, it's recommended that you add it anyway since your internal policies or IT team may require it.
The following entry adds Envoke email sender IPs in your SPF record in the DNS of your domain.
This needs to be added by the IT person or team who has access to manage your domain. You can send a link to this page to them. https://support.envoke.com/en/articles/3773461-spf-records
Check your current SPF record
You can check your current SPF record here using your sender domain.
For example if you send emails from firstname.lastname@example.org then your sender domain is comms.acme.com
Additional technical details
Emails in general have two sending addresses associated with them:
the "envelope sender", and the "from address".
The envelope sender works in the background; it is where computers respond (in the case of bounce messages or errors)
The from address is visible to contacts; this is where people respond.
SPF is used to validate the envelope sender. Envoke's envelope sender (Return-Path header) is always lists.bettermail.ca which is the address that is being verified by SPF records and we manage the SPF record for its domain.
The from address can be customized to use any email you like. The sending domain for this email address should be authenticated using Domain Keys.
This means you can send messages through Envoke, using your own from address without updating your SPF record.
SPF records and forwarded messages
smtpX.mailsender04.com is the name for some of our SMTP servers, this however is not being verified by SPF records.
Our SPF records for bettermail.ca allow sending from all of our IP ranges.
See the following sample SPF pass header from Gmail for example.
spf=pass (google.com: domain of email@example.com designates 220.127.116.11 as permitted sender) firstname.lastname@example.org
The problem with some forwarded emails is that the destination still checks the SPF records of the original sender (our Return-Path header).
Since the IPs of the forwarding server are not in our SPF records it will be rejected by the destination server due to our SPF policy which was previously set to a hard fail "-all".
This really is not a problem with the SPF records but how the forwarding is done.
Please see http://www.openspf.org/SRS or http://en.wikipedia.org/wiki/Sender_Rewriting_Scheme for help in implementing the Sender Rewriting Scheme.
Our SPF records will allow forwarded messages to be classified as a soft SPF fail instead of the original hard SPF fail.