An SPF (Sender Policy Framework) record is a type of DNS record, that identifies which mail servers are authorized to send email on behalf of your domain. This prevents "spoofing" and ensures that purchase orders and notifications, sent from Unimarket. Are not flagged as spam by your recipients' mail servers.
Using the SPF "Include" Statement
Unimarket provides a global Include statement. The primary advantage of using this method is that your technical team will not need to manually update your DNS records if Unimarket adds new mail servers or changes its infrastructure in the future.
Important Availability Note: While Unimarket continues to support existing customers using this method, the SPF Include option is no longer available for new customers or for existing customers to switch to if they are not already using it.
Implementation
To authorize Unimarket, add the following to your existing SPF record:
- include:_spf.unimarket.com
Example of a completed SPF record:
- v=spf1 mx include:_spf.unimarket.com ~all
Direct IP Address Authorization
If your organization does not use the "Include" method. You may need to whitelist the specific IP addresses of the Unimarket production email servers, relevant to your region.
| Production Region | IP Address |
|---|---|
| Australia (AU) | 35.201.28.55 |
| New Zealand (NZ) | 35.244.97.153 |
| United States (US) | 34.72.64.51 |
Why SPF Alignment Matters
Deliverability: Without SPF authorization, your suppliers' email servers may reject purchase orders sent from Unimarket, assuming they are fraudulent.
Security: SPF helps protect your brand reputation by making it harder for malicious actors to impersonate your organization's procurement department.
Compliance: Proper SPF records are a prerequisite for advanced security protocols like DMARC.
Troubleshooting
If you have added the record but emails are still being blocked:
SPF Record Limit: Ensure your domain has no more than 10 "DNS lookups" in its SPF record; adding too many includes can cause the check to fail.
Multiple Records: Ensure you only have one SPF record (starting with
v=spf1). Having multiple SPF records on a single domain is invalid.Propagation: DNS changes can take up to 24–48 hours to fully propagate across the internet.