From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 1D4FF3B2AE for ; Fri, 30 Sep 2016 09:08:42 -0400 (EDT) Received: by mail-it0-x231.google.com with SMTP id o19so20844936ito.1 for ; Fri, 30 Sep 2016 06:08:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=r3MeNEIDCNWR4wWVuaNn0RxBnu1caxqSuPhnkMvkkCk=; b=LQUDIljtU1IdjCUNCbltu9E8IIJQ+3s3Ib46GGQfV5JYhZDWJ6g74bBKcvx6fIDWnw ZzSoEJgOI2j+1igVC4ZWHaKnWS4NzoeVlxs2vrR2csl1Hf6Td6//oAL3Xsr6mmtMJm3t rK3JIJlePV/9V7Ui5mYOqueucJSgQ58T4pHwdmPgmivvfc9m/aAkO9Bnm2cFM8r5Apy3 PyUW53Z8pyiraK/seJ2jh65cT9fUlbghk02yWpyamkwJi2SwVmcTwYra7FwSXgE7oGMH NhnnvrxUwcR4db0Fuka2S6TrDS4PdHfXtHYht2BYgZeTsy74JekA86tyKGKqSTV3NMa7 yluQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=r3MeNEIDCNWR4wWVuaNn0RxBnu1caxqSuPhnkMvkkCk=; b=DwbbmvTDcFlW/lUNVDSLgQxFBLd2BOAfXCcodFkL/uaBLW4H9RRFw8syquEwtBxjAf QioX4z6eCc3c/Lzek9bA4HpHXcDY+kEFe3hBzyNAmAJ9/7dS2Jj6BKK5HhT8mcPkuuDd j3ngKD+de4eRajXjGR0/6PffQOMfUvtX1of4Fz4YxqrtnKA2sn38BBojA6VzUjdJLdS+ ms7uTmbKJBi228iNiAuaUKnJ8zv5sp4c1DOW8TvimwAhCtiWoN/Ynes/a0APEyyB6PSS Qtogf+5ulhAjmzJ0y6nGjzQg7xoq3gArbp9yOHDVFoxaak8y64vmTns36FPFYjwumE0h EMaQ== X-Gm-Message-State: AA6/9Rk+OeXoaGlVq7E2ZVxKDTKRPAXC5Inq6b5CEzAReJ2caT+PS8uTsaYBfAoVQoUhU06bgR3+R/4dRft4HQ== X-Received: by 10.36.210.70 with SMTP id z67mr4272894itf.67.1475240921544; Fri, 30 Sep 2016 06:08:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.158.212 with HTTP; Fri, 30 Sep 2016 06:08:21 -0700 (PDT) In-Reply-To: <874m4xbyt4.fsf@toke.dk> References: <06273A79-CAEB-4981-9BEE-22939D333D66@gmail.com> <30DC0151-C918-4664-A1FE-9179E08DE833@gmail.com> <874m4xbyt4.fsf@toke.dk> From: Neil Shepperd Date: Fri, 30 Sep 2016 09:08:21 -0400 Message-ID: To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Cc: Jonathan Morton , Dave Taht , cake@lists.bufferbloat.net Content-Type: multipart/alternative; boundary=94eb2c05d07e163daa053db94bb9 Subject: Re: [Cake] cake for net-next 4.8 X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Sep 2016 13:08:42 -0000 --94eb2c05d07e163daa053db94bb9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hmm, PTR record is there, so I guess setting up DKIM is indeed the most likely culprit. On 30 September 2016 at 04:02, Toke H=C3=B8iland-J=C3=B8rgensen wrote: > Neil Shepperd writes: > > > I think I have now accumulated enough spam/nonspam classified emails > > to make a statistically signification observation: it seems like all > > emails classified as spam from these lists were send from ipv6: > > > > SPF: PASS with IP 2600:3c03:0:0:f03c:91ff:fe61:86ce > > > > All emails from bufferbloat.net lists are failing DKIM (because of the > > mailing list footer breaking the DKIM signature) which might be worth > > fixing, and failing DMARC because all mailing lists fails DMARC > > (however google does not have a strict DMARC policy so that shouldn't > > matter, I hope). > > > > By the way, it's not just you, either. I have emails from others on > > these lists in my spam folder. > > > > The distinguishing factor seems to be whether the email was sent from > > the lists.bufferbloat.net ipv6 address. Unless this address > > corresponds to some kind of tunnel broker possibly also used by > > spammers, I can only assume this is some kind of bug (after all, it > > was spf validated so the address shouldn't matter at that point?). > > Indeed, gmail requires extra measures for IPv6: > https://support.google.com/mail/answer/81126 (scroll down to "Additional > guidelines for IPv6"). > > Fixing DKIM might be worthwhile :) > > -Toke > --94eb2c05d07e163daa053db94bb9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hmm, PTR record is there, so I guess setting up DKIM is in= deed the most likely culprit.

On 30 September 2016 at 04:02, Toke H=C3=B8iland-J=C3=B8r= gensen <toke@toke.dk> wrote:
Ne= il Shepperd <nshepperd@gmail.com<= /a>> writes:

> I think I have now accumulated enough spam/nonspam classified emails > to make a statistically signification observation: it seems like all > emails classified as spam from these lists were send from ipv6:
>
> SPF: PASS with IP 2600:3c03:0:0:f03c:91ff:fe61:86ce
>
> All emails from bufferbloat.net lists are failing DKIM (because of th= e
> mailing list footer breaking the DKIM signature) which might be worth<= br> > fixing, and failing DMARC because all mailing lists fails DMARC
> (however google does not have a strict DMARC policy so that shouldn= 9;t
> matter, I hope).
>
> By the way, it's not just you, either. I have emails from others o= n
> these lists in my spam folder.
>
> The distinguishing factor seems to be whether the email was sent from<= br> > the lists.bufferbloat.net ipv6 address. Unless this address
> corresponds to some kind of tunnel broker possibly also used by
> spammers, I can only assume this is some kind of bug (after all, it > was spf validated so the address shouldn't matter at that point?).=

Indeed, gmail requires extra measures for IPv6:
https://support.google.com/mail/answer/81126 (s= croll down to "Additional
guidelines for IPv6").

Fixing DKIM might be worthwhile :)

-Toke

--94eb2c05d07e163daa053db94bb9--