From: "Dave Täht" <dave@taht.net>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake for net-next 4.8
Date: Fri, 30 Sep 2016 12:42:52 -0700 [thread overview]
Message-ID: <50625ff6-5baf-6c4b-6e1b-55d55a37c199@taht.net> (raw)
In-Reply-To: <874m4xbyt4.fsf@toke.dk>
On 9/30/16 1:02 AM, Toke Høiland-Jørgensen wrote:
> Neil Shepperd <nshepperd@gmail.com> 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 :)
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
>
next prev parent reply other threads:[~2016-09-30 19:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 18:30 Dave Taht
2016-09-27 14:38 ` Jonathan Morton
2016-09-27 16:04 ` Dave Taht
2016-09-27 16:13 ` Jonathan Morton
2016-09-29 23:22 ` Neil Shepperd
2016-09-30 8:02 ` Toke Høiland-Jørgensen
2016-09-30 13:08 ` Neil Shepperd
2016-09-30 19:42 ` Dave Täht [this message]
2016-09-30 20:37 ` Neil Shepperd
2016-09-30 21:10 ` Dave Täht
2016-10-03 21:17 ` Neil Shepperd
2016-10-04 6:33 ` Henning Rogge
2016-10-04 16:09 ` Dave Täht
2016-10-20 5:56 ` Neil Shepperd
2016-09-27 17:52 ` Jonathan Morton
2016-09-27 18:18 ` Dave Taht
2016-09-27 18:56 ` Jonathan Morton
2016-09-27 19:29 ` Dave Taht
2016-09-27 19:54 ` Jonathan Morton
2016-09-28 23:26 ` Dave Taht
2016-09-28 23:34 ` Jonathan Morton
2016-09-29 20:43 ` Andrew Shewmaker
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50625ff6-5baf-6c4b-6e1b-55d55a37c199@taht.net \
--to=dave@taht.net \
--cc=cake@lists.bufferbloat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox