Hmmmm, had a bit of bovver with my SPF records allegedly not being right. In a discussion with the hosting provider over this and wanted to check my facts.....
[root@test ~]# dig -t txt impamark.co.uk
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.68.rc1.el6 <<>> -t txt impamark.co.uk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39272
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;impamark.co.uk. IN TXT
;; ANSWER SECTION:
impamark.co.uk. 2709 IN TXT "v=spf1 mx a -all"
;; Query time: 0 msec
;; SERVER: 192.168.97.1#53(192.168.97.1)
;; WHEN: Fri Oct 5 15:03:12 2018
;; MSG SIZE rcvd: 61
As far as I am aware that is correct?
When I test with mxtoolbox.com It all seems OK apart from one bit
Prefix Type Value PrefixDesc Description
v version spf1 The SPF record version
+ mx Pass Match if IP is one of the MX hosts for given domain name
+ a Pass Match if IP has a DNS 'A' record in given domain
- all Fail Always matches. It goes at the end of your record.
Any ideas why it shows Fail on -all ? Is that just due tio the way it 'processes' the rules, so anything after -all that hasn't matched is classed as a Fail?
All the tests below it show green ticks.
SPF Contains characters after ALL No items after 'ALL'.
SPF Syntax Check The record is valid
Any thoughts appreciated. I'm pretty sure my hosting provider has suffered a network block due to some spammer on my IP range but just wanted to be sure of my facts first.