From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake for net-next 4.8
Date: Tue, 27 Sep 2016 19:13:55 +0300 [thread overview]
Message-ID: <30DC0151-C918-4664-A1FE-9179E08DE833@gmail.com> (raw)
In-Reply-To: <CAA93jw7tyL+SL8GrDy66ggQ3BSDsoTmaeAcKLPex1L9y6FSQCA@mail.gmail.com>
> On 27 Sep, 2016, at 19:04, Dave Taht <dave.taht@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@lists.bufferbloat.net designates 45.79.142.77 as permitted sender) smtp.mailfrom=cake-bounces@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
next prev parent reply other threads:[~2016-09-27 16:13 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 [this message]
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
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=30DC0151-C918-4664-A1FE-9179E08DE833@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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