Sending Email on your behalf.
ETZ sends a large volume of email on behalf of our agencies. In some instances we send that email using the agencies' domain. This can cause problems for ourselves and our agencies in email delivery. Recently email providers have tightened the rules for companies like ETZ sending email on their clients behalf.
Due to these tightening rules and the recent changes we made to our systems it has become necessary for all agencies who use Timesheetz with their own email domain, to add an SPF record to their DNS. An SPF record tells servers across the internet to trust that we are allowed to send email for you. Without that trust, email providers may not deliver messages vital to your business.
What needs to change?
If we send emails using your domain, then you will need to add an SFP record to your DNS records. If you already have an SPF record, then you will need to modify it to reference our new _spf.timesheetz.net sub-domain. Using this sub-domain should insulate your organisation from having to make these kinds of changes in the future.
Who makes the change?
Typically an agency will either have an in-house IT team, or outsource that function to another company. In either case you will need to contact them and ask them to add or adjust your SPF record. We recommend you also send them this article for clarity.
Technical information on our SPF record.
In line with industry best practice ETZ maintains an _spf sub domain to allow us to send email on our customers behalf.
As an agency or their IT provider you need to add the following section to an existing DNS SPF record:
If the agency does not currently have an SPF record then the entire record should look like:
"v=spf1 include:_spf.timesheetz.net ~all"
In the past we have advised users to add ip4 and a record sections to their SPF records. These are now redundant, and our recommendation would be to remove them.
The following are redundant SPF entries and can be removed:
You can check the validity of your SPF record at https://mxtoolbox.com/spf.aspx
For more information on SPF records please see http://www.openspf.org