Hello,
On Sat, Jul 29, 2023 at 08:24:47PM +0100, Mike Zanker via BitFolk Users wrote:
On 29 Jul 2023, at 20:07, Hugo Mills via BitFolk Users
<users(a)mailman.bitfolk.com> wrote:
@ TXT "v=spf1 mx a
ip4:85.119.84.138/21 ip6:2001:ba8:1f1:f0e6::/64 a:mail.carfax.org.uk
a:savella.carfax.org.uk -all"
and the diagnostic message from gmail isn't all that helpful about why
it's not matching.
Does anyone have any idea what I've missed here?
You also need a TXT record for savella.carfax.org.uk
<http://savella.carfax.org.uk/>, e.g.
Weird that the "ip6:2001:ba8:1f1:f0e6::/64" does not cover this.
According to the RFC:
https://datatracker.ietf.org/doc/html/rfc7208#section-5.3
"a:savella.carfax.org.uk" is going to look up the addresses of
"savella.carfax.org.uk", not do a TXT query for an SPF record at
"savella.carfax.org.uk", so why do you believe this is needed? I
think you are thinking of "include":
https://datatracker.ietf.org/doc/html/rfc7208#section-5.2
This doesn't answer the question as to why gmail doesn't think this
SPF record covers 2001:ba8:1f1:f0e6::2.
I would recommend setting proper reverse DNS, although the default
IPv6 reverse DNS provided by BitFolk should satisfy the basic need
for matching reverse DNS, so it's probably not that.
If we can't get to the bottom of this I would ask on mailop:
https://mailop.org/
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting