Recursive SPF record for mail.inflatableoffice.com

I suspect that the SPF record for mail.inflatableoffice.com may be causing trouble for some recipients, even for messages that weren't sent from InflatableOffice.

We've observed the following failure in messages that were delivered to Office 365 mail servers:

1. Received-SPF: PermError (protection.outlook.com: domain of nationaleventpros.com used an invalid SPF mechanism)

At the time of delivery, the SPF record of nationaleventpros.com referenced that of mail.inflatableoffice.com:

1. $ dig +short txt nationaleventpros.com
2. "v=spf1 include:spf.protection.outlook.com include:infusionmail.com include:mail.inflatableoffice.com include:secureserver.net -all"

and the SPF record of mail.inflatableoffice.com again referenced itself:

1. $ dig +short txt mail.inflatableoffice.com
2. "v=spf1 ip4:208.64.38.12 ip4:50.56.218.59 ip4:209.250.2.66 include:mail.inflatableoffice.com include:mailSPF.smtp.com ~all"

When I dereferenced the mail.inflatableoffice.com record and removed its recursion—

1. $ dig +short txt nationaleventpros.com
2. "v=spf1 include:spf.protection.outlook.com include:infusionmail.com ip4:208.64.38.12 ip4:50.56.218.59 ip4:209.250.2.66 include:mailSPF.smtp.com include:secureserver.net -all"

—subsequent messages to Office 365 mail servers passed:

1. Received-SPF: Pass (protection.outlook.com: domain of nationaleventpros.com designates 198.71.225.37 as permitted sender) receiver=protection.outlook.com; client-ip=198.71.225.37; helo=a2nlsmtp01-03.prod.iad2.secureserver.net;

I'm not very familiar with mail handling so I may be misinterpreting things, but I think this result suggests that the recursive reference by mail.inflatableoffice.com is incompatible with the way that Office 365 mail servers evaluate SPF records.