| Note |
|---|
Add Full example with M365 for reference:
|
The exists mechanism is used to construct an arbitrary host name that is used for a DNS ‘A' record query. These 'A’ records are all of the current INKY IP addresses and will include any future address.
If you already have spf-2.inkyphishfence.com as a record in your customers SPF record from the previous instructions, there is no change necessary at this time. The new exists mechanism will provide INKY greater flexibility in the future, but there is currently no plan, timeline, or goal to change the IP addresses listed within the original SPF record.
Once it becomes clear that INKY must expand the IP ranges used then we’ll provide direct communication to customers on the timeline of the change.
https://inkyops.atlassian.net/wiki/x/AgArlQ Details on updating your SPF record to work with INKY |
Why do I see SPF, DKIM, and DMARC failures in my message headers after enabling INKY?
...
Should I add INKY’s IP addresses to my SPF Record?
No. You should not have to, since INKY should never be the last message hop before being sent to the recipient mail server. Because of this, the The recipient mail server should always see the IP address Address connecting from Office 365, Google Workspace, or your upstream provider.
Unfortunately, sometimes recipient servers mistakenly misinterpret the headers of an email and see INKY’s IP before the mail was sent out to the recipient server and call that an SPF Failure. To account for some of these other tools and ensure clean deliverability - it is recommended to add INKY to your SPF Record.