[vcf-midatlantic] MIME format

Cory Smelosky b4 at gewt.net
Wed Nov 4 23:57:38 EST 2015


On Wed, 4 Nov 2015, Jason Howe via vcf-midatlantic wrote:

> Yes and Google just recently changed something with regards to mail and ipv6. 
> I had to add an ipv6 entry to my SPF record last week on my domain because 
> google started bouncing stuff, where my ipv4 only SPF had been allowing me to 
> send stuff to people on gmail flawlessly for years.
>
> In the last year or so, when setting up new servers, I've been setting up 
> AAAA records and making sure services bind to both 4 and 6 addresses -- it's 
> actually quite interesting to see how much traffic actually flows over ipv6.
>

Like the majority of this email!

> --Jason
>
> On 11/04/2015 05:49 PM, Systems Glitch via vcf-midatlantic wrote:
>>> Received: from www.mailmanlists.us ([2604:3400:dc1:43:216:3eff:fe36:d305])
>>>          by mx.google.com with ESMTP id 
>>> v129si2644061qka.16.2015.11.04.16.17.36;
>>>          Wed, 04 Nov 2015 16:17:37 -0800 (PST)
>>> Received-SPF: softfail (google.com: domain of transitioning
>>> vcf-midatlantic-bounces at lists.vintagecomputerfederation.org does not
>>> designate 2604:3400:dc1:43:216:3eff:fe36:d305 as permitted sender)
>> Looks like you need an `ip6:` IPv6 record for SPF. I'm guessing you should 
>> put a v6 network/prefix in there, since www.mailmanlists.us seems to be in 
>> the middle of an existing range.
>> 
>> IPv6...it's out there...and people are using it!
>> 
>> Thanks,
>> Jonathan
>
>

-- 
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects



More information about the vcf-midatlantic mailing list