From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Matthew Hall <mhall@mhcomputing.net>,
Alexander Duyck <alexander.duyck@gmail.com>
Cc: dev@dpdk.org
Subject: Re: Any chance someone could fix the SPF records for this mailing list?
Date: Thu, 04 Jun 2015 10:05:36 +0200 [thread overview]
Message-ID: <33335550.m3QIexZNHU@xps13> (raw)
In-Reply-To: <20150604030945.GA16836@mhcomputing.net>
2015-06-03 20:09, Matthew Hall:
> 2015-06-03 19:54, Alexander Duyck:
> > I have noticed a number of emails from this list are going to spam. It
> > looks like it might be gmail filtering based on the fact that most of
> > the list has a valid SPF based on an IPv4 address that reports out like
> > below:
[...]
> > Received-SPF: pass (google.com: best guess record for domain of
> > dev-bounces@dpdk.org designates 92.243.14.124 as permitted sender)
[...]
> > However the ones that are going straight into my spam folder list an
> > IPv6 address that is rated neutral by the SPF:
[...]
> > Received-SPF: neutral (google.com: 2001:4b98:dc0:41:216:3eff:fe72:dd13
> > is neither permitted nor denied by best guess record for domain of
> > dev-bounces@dpdk.org) client-ip=2001:4b98:dc0:41:216:3eff:fe72:dd13;
[...]
> > I was just wondering if it would be possible to get the IPv6 address
> > added as a permitted sender for the domain to help reduce the amount of
> > messages that are likely being flagged as spam for myself and likely
> > others.
>
> https://support.google.com/mail/answer/81126?p=ipv6_authentication_error&rd=1#authentication
Thanks for the information.
Indeed the ip6: field of the SPF was not filled. It should be fixed now.
By the way, it is possible to avoid spam classification in gmail with a
filter to:(dev@dpdk.org).
prev parent reply other threads:[~2015-06-04 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 2:54 Any chance someone could fix the SPF records for this mailing list? Alexander Duyck
2015-06-04 3:07 ` Matthew Hall
2015-06-04 3:09 ` Matthew Hall
2015-06-04 8:05 ` Thomas Monjalon [this message]
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=33335550.m3QIexZNHU@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=alexander.duyck@gmail.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.