Sender Policy Framework (SPF) is an open standard for email authentication. It validates the connecting IP address, by looking up the SPF / TXT record in DNS for the domain in the envelope MAIL FROM or HELO/EHLO. By adding our _netblocks.mimecast.com entry to your SPF / TXT record, you ensure we are allowed to send mail for your domain name. Mail Transfer Agents (MTAs) can verify SPF for inbound emails if the sender publishes DNS entries for them in their domain records.
Implementing SPF for Outbound Email Delivery
To ensure a successful implementation of SPF with Mimecast, include a comprehensive list of our outbound IP addresses in your DNS SPF record. This is a long list (24 distinct IP4 ranges at the time of writing) and new ranges may be added in the future without notice. However, you can ensure your record is always up to date by including the "xx._netblocks.mimecast.com" statement.
To determine what "xx" is for your region, refer to the table below:
|Europe (UK and Jersey)||v=spf1 include:eu._netblocks.mimecast.com ~all|
|North America||v=spf1 include:us._netblocks.mimecast.com ~all|
|South Africa||v=spf1 include:za._netblocks.mimecast.com ~all|
|Australia||v=spf1 include:au._netblocks.mimecast.com ~all|
|Global (includes all the above)||v=spf1 include:_netblocks.mimecast.com ~all|
Some typical examples are suggested below as a starting point for constructing an appropriate record:
|Simple Case||Relaxed configuration for customers which only send external mail for a given domain via Mimecast.|
|Strict Case||For customers wishing to implement a strict SPF reject for unmatched requests, we strongly recommend testing with the relaxed syntax first.|
|Customers with an Existing SPF Record for a Given Domain||If you have an existing SPF record representing a range of possible senders, these examples show how you can include Mimecast as a legitimate sender.|
|Customers with an Existing SPF Include Record for a Given Domain||In all cases, customers with existing SPF records should review their entries to ensure Mimecast servers are referenced exactly once. Any previous Mimecast references should be removed in favor of _netblocks.mimecast.com. Customers using a domain include a mechanism to refer to a DNS entry which already references _netblocks.mimecast.com, need take no further action.|
Creating the DNS Entry
If you wish to implement SPF for your domain, you'll need to create a corresponding TXT DNS record. By adding our IP Ranges to your TXT / SPF record, you ensure Mimecast is allowed to send mail carrying your domain name.
To create a DNS record:
- Update the SPF records for your domains with the information displayed in the application under SPF Record, as shown below:Only use the SPF record displayed in the application, as there are regional differences (i.e. "eu" for Europe in the above image). The regional records are also listed in the "Implementing SPF for Outbound Email Delivery" section above. If you're not the person responsible for this task, click the link to send an email containing the required detail to someone who is
- Log on to your .
- Update / replace each domain’s SPF record to specify us as the authorized outbound service.
- If all email for your domains will be routed via us, remove all previous SPF records.
- Other outbound sources for your domain may require a combined SPF record. In this instance, ensure you include the Mimecast "xx_netblocks.mimecast.com" entry before creating a mail flow connector. To determine what "xx" is, refer to step 1 above.See the "Implementing SPF for Outbound Email Delivery" section in the Configuring DNS Authentication Definitions and Policies page, and the Implementing SPF for Outbound Email Delivery page for additional information.
- Navigate to
- Click on the or links to view further information about the SPF record and toggle the display.This step performs a TXT record lookup and validates the SPF record entry. You can have more than one mechanism (IP/Host), but Mimecast must be the first one listed.