[Cake] cake for net-next 4.8

[Neil Shepperd]

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?).

I'm going to see if I can file some sort of a bug with special googler
powers, but I probably won't be allowed to tell you anything if they reply.

On Tue, 27 Sep 2016 at 12:14 Jonathan Morton <chromatix99 at gmail.com> wrote:

>
> > On 27 Sep, 2016, at 19:04, Dave Taht <dave.taht at gmail.com> wrote:
> >
> > Annoying. Perhaps my link to the blog in my .sig? Perhaps they object
> > to my verbosity?
>
> This seems relevant in the headers:
>
> Authentication-Results: mx.google.com; dkim=neutral (body hash did not
> verify) header.i=@gmail.com; spf=pass (google.com: best guess record for
> domain of cake-bounces at lists.bufferbloat.net designates 45.79.142.77 as
> permitted sender) smtp.mailfrom=cake-bounces at lists.bufferbloat.net;
> dmarc=fail (p=NONE dis=NONE) header.from=gmail.com
>
> I forget exactly how DKIM and DMARC work, but DKIM seems to be stymied by
> the list adding its own message footer (which is nevertheless
> best-practice).  I don’t know how relevant a DMARC fail is to their filter,
> or how relevant it *should* be.
>
> Could the listserver replace an original, verified DKIM certificate with
> its own after adding the footer?
>
> On the upside, I was able to add a filter specifically saying “never send
> to Spam folder”, and it appears to be working so far.  But everyone
> probably needs to do that; it’s not a scalable solution, only a workaround.
>
>  - Jonathan Morton
>
> _______________________________________________
> Cake mailing list
> Cake at lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/cake/attachments/20160929/c62cae1f/attachment.html>