From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: [kernel.org users] b4: DKIM verification available
Date: Mon, 23 Nov 2020 13:17:46 -0500 [thread overview]
Message-ID: <20201123181746.fu32rqyw3bpohciz@chatter.i7.local> (raw)
In-Reply-To: <20201123164220.GW244516@ziepe.ca>
On Mon, Nov 23, 2020 at 12:42:20PM -0400, Jason Gunthorpe wrote:
> Konstantin: This seems like a few bad behaviors here.. Shouldn't the
> first one report the DKIM failure??
Yeah, but I try not to put in features that everyone would immediately
turn off due to high false-positive rates. :) We treat a successful DKIM
verification as a nice surprise and quietly move on otherwise.
> It also feels like b4 should try other list archives if the DKIM is
> bad. eg inspect the to/cc headers and pick a vger list if available.
There is a better solution that should become available in the future
releases of public-inbox:
- it'll allow us to combine threads from multiple lists
- when multiple sources match, we'll be able to assign a "weighting"
metric that should let us pick vger lists over mailman lists when the
same message exists on both
-K
next prev parent reply other threads:[~2020-11-23 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201120221530.mfwn72nr6lqr2qqs@chatter.i7.local>
[not found] ` <20201122002808.GA20499@outflux.net>
2020-11-22 17:38 ` [kernel.org users] b4: DKIM verification available Konstantin Ryabitsev
2020-11-22 17:51 ` Kees Cook
[not found] ` <20201123154841.GU244516@ziepe.ca>
[not found] ` <1dccb9ac431b854ba4f7a72f6e7b90baecdacbe1.camel@HansenPartnership.com>
[not found] ` <20201123164220.GW244516@ziepe.ca>
2020-11-23 18:17 ` Konstantin Ryabitsev [this message]
2020-11-23 18:28 ` Jason Gunthorpe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201123181746.fu32rqyw3bpohciz@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jgg@ziepe.ca \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).