From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) by dpdk.org (Postfix) with ESMTP id 8E23E376E for ; Thu, 4 Jun 2015 10:06:28 +0200 (CEST) Received: by wifw1 with SMTP id w1so49053070wif.0 for ; Thu, 04 Jun 2015 01:06:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=wQNOUHxmI8pAOc0nOpc4mtr2ITzXMSeyvHhHrsnaoX8=; b=DYo2GtWDRiOi9LiFBLS/IDquibzuy77H7w+ptZ8vGI1leyYnRWukFrMyX8rna+/5WW W+eX7RhCAYaQZt74EIsL0XoCu2pdEk12B6Yk+rpZy5W/OouzPnOe30Hz8gx8nO9LYoKr vzr0WENlAaj1VJ+ChiileDlYrQJSFymdHtgED5iCey8NwfLcur1FCeF3ulnEqSiOAj/A Gc/IhvJmYliOytHwUtT4wOsceeJtx6aWVoDp5EiBARKsfhDrgLKj+kIMKhvbGH00TKTO 13IGriPudJU3b8Qn+hjsnT/5LWEpFzNthbDoUtyP8C2psZ7w9xy+ZDQPfxQyJZiOFcAf YzVQ== X-Gm-Message-State: ALoCoQkhdHSdAmizZnOhbfI7iuUeBx0BQFydOLJVw6xJ1f5r5hTG3Bwl72Ytzz0n4/EI2WhefbUl X-Received: by 10.180.206.229 with SMTP id lr5mr50015820wic.86.1433405188384; Thu, 04 Jun 2015 01:06:28 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id di9sm30024036wib.16.2015.06.04.01.06.26 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Jun 2015 01:06:27 -0700 (PDT) From: Thomas Monjalon To: Matthew Hall , Alexander Duyck Date: Thu, 04 Jun 2015 10:05:36 +0200 Message-ID: <33335550.m3QIexZNHU@xps13> Organization: 6WIND User-Agent: KMail/4.14.8 (Linux/4.0.4-2-ARCH; KDE/4.14.8; x86_64; ; ) In-Reply-To: <20150604030945.GA16836@mhcomputing.net> References: <556FBDD3.2090604@gmail.com> <20150604030757.GA16737@mhcomputing.net> <20150604030945.GA16836@mhcomputing.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Any chance someone could fix the SPF records for this mailing list? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2015 08:06:28 -0000 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).