From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (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 200D13B2AE for ; Fri, 30 Sep 2016 16:37:11 -0400 (EDT) Received: by mail-it0-x22e.google.com with SMTP id o19so44585742ito.1 for ; Fri, 30 Sep 2016 13:37:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=qtk0pPYzYE55Pa4kpoSEP20Vx+BVNjb1q/xG6O4WQNg=; b=tqBKSqRdcW6jKvr+eOVtT8Ya68TS33jRUy/ouWTwkw9/URyOrIsonmDI99c7qWU6Fq ObJnArNhsXMAutBCjP8mx8iw4gre+AiLR3E0g/jpxZXAe3Y3MgrT+mftAan5ELPqsBzc Djm+IzS4/bNLtnElvCfNr710sL6XdIECIi9iihVgmCKhHSmD6d02la+X5v8MwlA6Utdo i71S2O32XTJ5bSZk+hCuc/i8puay4FKoyG6kUidF7rInlKAW4WIKZn+G+dAYvIXQhp80 KdnFRElXhVSaUDp8S0Bt5WZ7VCRasI/rvUKR2VblqYXqB5W3wR6XBAf8Q3bRRVpkEAEb 8Q3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=qtk0pPYzYE55Pa4kpoSEP20Vx+BVNjb1q/xG6O4WQNg=; b=cIpoPa5pC26HgsS0k6ufAKoXcxR0JM0UDZ10Cs+E110iE8Gw9wSffGhirkjCKRGZ4k TB2IXWJj/jbZaTJ3u8IAPJF/rKKRfntZdKA46C97BH3oVN1UpdL2TOZhK7Gm0xHKScQy 7trwEnJp5X/WQ3b7ln4sL0HKFGnnvt1WYoyO9upcymM6WnistwNYuVPbs/hZdeMHmRJT z5jJKjFaVqjYliMj/udqPGjoJRu//POLN+RF5O3uXantiserYpHBbuK1lSGu24Wk02kb x5BPVmHHXJHq2dDO5oxCXZ+JEp9jLw03zK55xn1dqzbuZj6j8iC5WEttVwHEnJaeqMEp dVSw== X-Gm-Message-State: AA6/9RniPnOXicCMOKfAVPK4/tmOfMSJIzz+5vHddjh2wwI8YrOCK1SOAKgV7v4GcATuc24zyMj7LfCieh+eIg== X-Received: by 10.36.25.14 with SMTP id b14mr6322615itb.29.1475267830529; Fri, 30 Sep 2016 13:37:10 -0700 (PDT) MIME-Version: 1.0 References: <06273A79-CAEB-4981-9BEE-22939D333D66@gmail.com> <30DC0151-C918-4664-A1FE-9179E08DE833@gmail.com> <874m4xbyt4.fsf@toke.dk> <50625ff6-5baf-6c4b-6e1b-55d55a37c199@taht.net> In-Reply-To: <50625ff6-5baf-6c4b-6e1b-55d55a37c199@taht.net> From: Neil Shepperd Date: Fri, 30 Sep 2016 20:37:00 +0000 Message-ID: To: =?UTF-8?Q?Dave_T=C3=A4ht?= , cake@lists.bufferbloat.net Content-Type: multipart/alternative; boundary=001a1144b0c4fcc41f053dbf8eb7 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 20:37:11 -0000 --001a1144b0c4fcc41f053dbf8eb7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Disabling ipv6 (at least in the mail server, in outgoing direction) is probably the easiest option... I see on most messages here DKIM-Signature headers apparently from gmail: "v=3D1; a=3Drsa-sha256; c=3Drelaxed/relaxed; d=3Dgmail.com; s=3D20120113;".= These signatures are failing because of the added message footer. No sign of a DKIM-Signature for lists.bufferbloat.net. You'd need to set that up in the list MTA. On Fri, 30 Sep 2016 at 15:42 Dave T=C3=A4ht wrote: > > > On 9/30/16 1:02 AM, 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 "Additiona= l > > guidelines for IPv6"). > > > > Fixing DKIM might be worthwhile :) > > But it passes the spf check?? And the reverse lookup is correct. > > How about I just disable ipv6? > > Have no idea why dkim doesn't work. > > > > > -Toke > > _______________________________________________ > > Cake mailing list > > Cake@lists.bufferbloat.net > > https://lists.bufferbloat.net/listinfo/cake > > > _______________________________________________ > Cake mailing list > Cake@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cake > --001a1144b0c4fcc41f053dbf8eb7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Disabling ipv6 (at least in the mail server, in outgoing d= irection) is probably the easiest option...
I see on most messages here = DKIM-Signature headers apparently from gmail: "v=3D1; a=3Drsa-sha256; = c=3Drelaxed/relaxed; d=3Dgmail.com; s=3D20= 120113;". These signatures are failing because of the added message fo= oter. No sign of a DKIM-Signature for=C2=A0lists.buf= ferbloat.net. You'd need to set that up in the list MTA.
<= br>
On Fri, 30 Sep 2016 at 15:42= Dave T=C3=A4ht <dave@taht.net> = wrote:


On 9/30/16 1:02 AM, Toke H=C3=B8iland-J=C3=B8rgensen wrote:
> Neil Shepperd <nshepperd@gmail.com> writes:
>
>> I think I have now accumulated enough spam/nonspam classified emai= ls
>> to make a statistically signification observation: it seems like a= ll
>> 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 o= f the
>> mailing list footer breaking the DKIM signature) which might be wo= rth
>> fixing, and failing DMARC because all mailing lists fails DMARC >> (however google does not have a strict DMARC policy so that should= n't
>> matter, I hope).
>>
>> By the way, it's not just you, either. I have emails from othe= rs on
>> these lists in my spam folder.
>>
>> The distinguishing factor seems to be whether the email was sent f= rom
>> 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, i= t
>> was spf validated so the address shouldn't matter at that poin= t?).
>
> 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 :)

But it passes the spf check?? And the reverse lookup is correct.

How about I just disable ipv6?

Have no idea why dkim doesn't work.

>
> -Toke
> _______________________________________________
> Cake mailing list
> Cake@l= ists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
_______________________________________________
Cake mailing list
Cake@lists.= bufferbloat.net
https://lists.bufferbloat.net/listinfo/cake
--001a1144b0c4fcc41f053dbf8eb7--