SPF has mechanisms after "all"
URGENTWhat it means
Everything after all is never evaluated, including the offending value. Senders you believe are authorised are silently not.
How to fix it
Move all to the very end of the record, after every ip4:, ip6: and include: mechanism.
Check your own domain
This page describes the condition. To find out whether your domain has it, run the SPF test or the full checkup, which examines every record at once.
Understand it properly
This page covers one condition. For the whole picture, What is SPF, and the ten-lookup limit, or start at the Health Library.
Where this comes from
We judge this against RFC 7208 section 5.1. Every finding on this site cites the specification behind it so you can check the work rather than take our word for it.
Other SPF conditions
SPF_ALL_NOT_LAST
Every fix on this site is yours to implement. If you would rather someone did it, I take this work directly.