[vcf-midatlantic] Possible spam fix: DNS change
Jason Howe
jason at smbfc.net
Thu Nov 5 15:08:25 EST 2015
The change has finally propagated around and it seem to have have done
the trick.
On messages coming into my junk gmail account from the list, I'm seeing
the following now:
Received-SPF: pass (google.com: domain of vcf-midatlantic-bounces at lists.vintagecomputerfederation.org designates 2604:3400:dc1:43:216:3eff:fe36:d305 as permitted sender) client-ip=2604:3400:dc1:43:216:3eff:fe36:d305;
The basic issue is that www.mailmanlists.us can't decide if it want's to
talk to google over ipv4 or ipv6. Of the message I checked, most came
in over ipv6, but some still over ipv4.
The SPF record that the mailmanlists.us had Evan define only contained
the ipv4 address as an allowed sender. Adding the ipv6 address into
that should now help across the board, not only gmail users.
There is still the small issue of the fact that www.mailmanlists.us
doesn't have a AAAA record or a ipv6 ptr record defined. This also has
the potential to help get stuff caught up in spam filters, but that is
something they need to fix on their end.
--Jason
There is still the issue of the fact that the hosting company can't
decide if it's wants to talk to google over ipv4 or ipv6 in a consistent
way, especially since they don't have an AAAA record published -- but
that's a support ticket for Evan to open. I'm actually pleasantly
surprised that we're not getting hammered for not having an AAAA ptr record
:)
On 11/05/2015 07:06 AM, Evan Koblentz via vcf-midatlantic wrote:
> Yesterday's messages about our headers + spam made me realize we were on to something. I called Jason H. and he determined that the txt record in our DNS settings -- the GoDaddy registrar side, not the mailing list side -- needed to have an IPv6 entry (vs only an IPv4) to properly synchronize. We made that change.
>
> Jason will explain it better than I could.
>
> If it seems to be fixed then we'll inform the list company.
More information about the vcf-midatlantic
mailing list