From: Matthew Hall <mhall@mhcomputing.net>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Any chance someone could fix the SPF records for this mailing list?
Date: Wed, 3 Jun 2015 20:09:45 -0700 [thread overview]
Message-ID: <20150604030945.GA16836@mhcomputing.net> (raw)
In-Reply-To: <20150604030757.GA16737@mhcomputing.net>
On Wed, Jun 03, 2015 at 08:07:57PM -0700, Matthew Hall wrote:
> Hello,
>
> I can confirm your claims. When I enabled IPv6 on my mail server Google began
> dropping or severely graylisting 100% of the mail until the IPv6 subnet was
> added to the SPF record. This needs to get fixed or the IPv6 outbound SMTP has
> to be disabled or Google users will lose tons of mails from the list.
>
> Matthew.
See also:
https://support.google.com/mail/answer/81126
https://support.google.com/mail/answer/81126?p=ipv6_authentication_error&rd=1#authentication
There is a specific section regarding IPv6.
Matthew.
next prev parent reply other threads:[~2015-06-04 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 2:54 Alexander Duyck
2015-06-04 3:07 ` Matthew Hall
2015-06-04 3:09 ` Matthew Hall [this message]
2015-06-04 8:05 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150604030945.GA16836@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=alexander.duyck@gmail.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).