0365 mail users are encouraged to use include:spf.protection.outlook.com -all in their SPF record.
I have followed this guidance. My company's spf record says:
v=spf1 include:spf.protection.outlook.com -all
the spf.protection.outlook.com record ends with include:spfa.protection.outlook.com -all which ends with include:spfb.protection.outlook.com
Each of those includes has a set of CIDRs for IPs used by outlook.com when sending email.
However, I am getting DMARC reports from google.com indicating an SPF FAIL for an IP that is actually covered by one of the includes in the SPF record. I think this is incorrect, yet is happening frequently.
Here is an example:
source_ip>126.96.36.199</source_ip> <count>1</count> -<policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>fail</spf>
the rejected ip is part of ip4:188.8.131.52/17 which is part of the spfb.protection.outlook record:
spfb.protection.outlook.com. 394 IN TXT "v=spf1 ip6:2a01:111:f400::/48 ip4:184.108.40.206/19 ip4:220.127.116.11/23 ip4:18.104.22.168/24 ip4:22.214.171.124/17 ip4:126.96.36.199/21 ip4:188.8.131.52/21 ip4:184.108.40.206/24 ip4:220.127.116.11/23 ip4:18.104.22.168/26 -all"
So, why is Google's email server treating this as an SPF fail?
This is not an isolated example - I receive frequent SPF fail notifications with respect to IPs included in the SPF record.