SPF results now match the RFCs, and what's next for DKIM and DMARC

DKIM and DMARC verification have been available as a feature you can request for a while now. As part of some work on them we noticed that our documentation for SPF has always been different from what the server actually sends.

The SPF result values are specified in the RFCs, so the documentation has always been correct. The server's output used a format closer to the rest of the hash: soft_fail, temp_error and perm_error instead of softfail, temperror and permerror. Today we released an update so the server output matches the RFCs, and what the documentation has always said. pass, fail, neutral and none are unchanged.

In the next couple of weeks we'll probably be moving DMARC and DKIM over to a self-serve option too. We just need to consider the cost. It isn't a massively expensive check, but it does occupy time in the server, and it's only really needed for production workloads. We're considering making it available from the Starter plan and above.