Last Updated: December 13 2023
How to Set Up an SPF Record
Overview
If you have your own email domain (for example, @tradeservice.com.au, @abcelectrical.com), your domain host or IT administrator needs to set up your Sender Policy Framework (SPF) record to list the programs that are authorised to send emails on your behalf.
A SPF record is a powerful anti-abuse tool, that protects you from fraudulent entities disguising their emails as yours. Additionally, an SPF record helps large mail servers such as Google and Microsoft establish the reputation of domains, thereby improving the deliverability of your emails. When an email is sent from Simpro Premium, the recipient’s spam filter checks if Simpro Premium is granted permission to send email from your domain. The server checks the corresponding SPF record to validate this permission. If the SPF record is absent, or set up incorrectly, the recipient’s spam filter may reject the incoming email.
If you host your company email in the cloud, your hosting provider should be able to provide instructions on how to publish your SPF Record.
You should approach your IT administrator or domain host support to set up your SPF record for you.
![Closed](../../Skins/Default/Stylesheets/Images/transparent.gif)
Even if you already have an SPF record, you may need to change / add to it to ensure your emails can be delivered from Simpro Premium.
To check your SPF Record:
- Go to http://kitterman.com/spf/validate.html
- Under Does my domain already have an SPF record? What is it? Is it valid?, enter the domain name for your company. For example, if your email is john@tradeservices.com.au, your domain is tradeservices.com.au.
- Click Get SPF Record (if any).
- If an SPF Record is set up, it is listed under The TXT records found for your domain are:
![Closed](../../Skins/Default/Stylesheets/Images/transparent.gif)
This is recommended for people with advanced knowledge of systems and domain administration.
![Closed](../../Skins/Default/Stylesheets/Images/transparent.gif)
You need to add a:chi-web-01.simprocloud.com to the existing record.
If you use Google for your mail hosting and your domain has an SPF Record, it looks something like this:
v=spf1 include:_spf.google.com ~all
The edited record should be:
v=spf1 a:chi-web-01.simprocloud.com include:_spf.google.com ~all
Microsoft Office 365
If you use Microsoft Office 365 for your mail hosting and your domain has an SPF Record, it looks something like this:
v=spf1 include:spf.protection.outlook.com ~all
The edited record should be:
v=spf1 a:chi-web-01.simprocloud.com include:spf.protection.outlook.com ~all
![Closed](../../Skins/Default/Stylesheets/Images/transparent.gif)
If your domain does not have an SPF entry in its DNS Records, add this record:
v=spf1 a:chi-web-01.simprocloud.com ~all
Your IT Administrator may choose to add more entries to the SPF Record. In this case, ensure that you check the whole SPF against a syntax checker to make sure it doesn’t include errors. Records that do not comply may cause temporary or permanent errors by receiving mail systems.
Once you have created or edited the SPF Record, please test it by sending an email from Simpro Premium, and check to see if it has been delivered to the recipient's inbox. If it is not delivered, contact Simpro Support.
SPF changes may take from 24 to 48 hours to update across the web.
![Closed](../../Skins/Default/Stylesheets/Images/transparent.gif)
Your IT Administrator may also consider using DomainKeys Identified Mail (DKIM) and Domain-based Message Authentication, Reporting and Conformance (DMARC) records to further improve email deliverability.
- DKIM provides an encryption key and digital signature that verifies that an email message was not faked or altered.
- DMARC unifies the SPF and DKIM authentication mechanisms into a common framework and allows domain owners to declare how they would like email from that domain to be handled if it fails an authorisation test.
Contact Simpro Support to get a DKIM key generated for your Simpro Premium build. Follow up with Simpro Support once the key has been added to your DNS so that it can be validated.