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:07:57 -0700 [thread overview]
Message-ID: <20150604030757.GA16737@mhcomputing.net> (raw)
In-Reply-To: <556FBDD3.2090604@gmail.com>
On Wed, Jun 03, 2015 at 07:54:11PM -0700, Alexander Duyck wrote:
> However the ones that are going straight into my spam folder list an IPv6 address that is rated neutral by the SPF:
> Received: from dpdk.org ([2001:4b98:dc0:41:216:3eff:fe72:dd13])
> by mx.google.com with ESMTP id cy1si1185671wib.89.2015.06.03.04.00.32;
> Wed, 03 Jun 2015 04:00:37 -0700 (PDT)
> 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;
> Authentication-Results: mx.google.com;
> 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) smtp.mail=dev-bounces@dpdk.org
>
> 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.
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.
next prev parent reply other threads:[~2015-06-04 3:10 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 [this message]
2015-06-04 3:09 ` Matthew Hall
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=20150604030757.GA16737@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).