Feature request: ignore trailing whitespace in spf record

[John Smith]

I find that some companies make copy-pasta mistakes and include whitespace garbage or new lines in their SPF record.

spf-engine-2.9.2 fails these with "SPF Permanent Error: Unknown mechanism found: -all;"

Most recent example:

# drill -t txt travel.fewo-direkt.de
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 16590
;; flags: qr rd ra ; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; travel.fewo-direkt.de. IN TXT

;; ANSWER SECTION:
travel.fewo-direkt.de. 300 IN TXT "v=spf1 include:_spf.messagegears.net -all\010"
travel.fewo-direkt.de. 300 IN TXT "spf2.0/pra include:_auth.messagegears.net -all\010"
travel.fewo-direkt.de. 300 IN TXT "google-site-verification=RqbYRWlrm4pSAOLa_1N89KTt-jOIDwzG8LekKsvLZP8"

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 26 msec
;; SERVER: 172.17.18.3
;; WHEN: Sat Aug 29 14:10:35 2020
;; MSG SIZE rcvd: 235

[Scott Kitterman (kitterman)]

That error comes from pyspf, so I would recommend filing an issue there:

https://github.com/sdgathman/pyspf/issues

Also, that's a line feed, not a space. I think the case for ignoring non-spaces is weaker, but particularly for the case of garbage text after the 'all' term it'd be pretty low risk to support.