I think I see what you're asking, but let me restate your problem, to be clear. You currently have mail working happily from fairwaytoursuae.com
via google, and you want to add a new bulk email system using mailgun. You have been advised to set a new SPF record, and don't quite understand what's going on.
The missing datum is who you are sending mailgun mails from; that is, what fully-qualified domain name (FQDN) appears in the host portion of the envelope-From field. I'm going to assume it's fairwaytoursuae.com
, not mail.fairwaytoursuae.com
.
The issue here is that mailgun has advised you to advertise an SPF record for mail.fairwaytoursuae.com
, but their web system shows an SPF record already existing which is not for that FQDN. Instead, their web system is showing you the current SPF record for the parent domain, fairwaytoursuae.com
, even though the interface suggests this is not so.
I suspect what it actually wants is for you to publish a single, combined record for the parent domain. Something like
fairwaytoursuae.com. IN TXT v=spf1 +a +mx +ip4:198.57.193.33 include:_spf.google.com include:mailgun.org ~all
Even if my guess is right, there are several potential problems with such a record. One is that you are likely to be getting perilously close to the limit of ten DNS lookups which represents the maximum the evaluation of an SPF record may require (another is that it's completely useless, like all SPF records that don't end -all
.) SPF isn't really intended for people who have a highly-distributed email infrastructure, and in starting with gmail you've started with one of the biggest on the planet, and are trying to make it bigger.