unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Boosts still not quite working
Date: Sat, 14 Aug 2021 18:09:53 -0400	[thread overview]
Message-ID: <20210814220953.e2qgzhax2mslmkhv@nitro.local> (raw)
In-Reply-To: <20210814204633.GA1020@dcvr>

On Sat, Aug 14, 2021 at 08:46:33PM +0000, Eric Wong wrote:
> > It was sent to iommu@lists.linux-foundation.org (mailman) and to a bunch of
> > vger lists, all of which have higher boosts in the configuration, e.g. netdev:
> 
> boost doesn't come into effect due to the Mailman footer from
> the iommu list.  extindex and v2 both account for content
> differences despite sharing the same Message-ID
> (deduplicating purely on Message-ID would be open to abuse
>  (and many old MUA-side bugs))

Ah-ha, okay. I clearly misunderstood its purpose. No worries, I see now that
when we retrieve t.mbox.gz, the mailbox contains both the iommu and the vger
sources, which should allow me to pick the preferred version based on the
criteria I need (e.g. DKIM validation).

> I'm planning on having a "diff view" to more easily distinguish
> between different messages having the same Message-ID.  It would
> make it easier to highlight buggy clients, Mailman misconfigurations,
> and malicious attempts to obscure/confuse readers.

Indeed, I agree that it's best to give access to both instead of always
returning the boosted-list version, as this would allow someone for malicious
message-id stuffing.

Now I just need to hack b4 to define a better criteria for when results have
multiple identical message-id's.

Thanks,
-K

      reply	other threads:[~2021-08-14 22:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-14 13:46 Boosts still not quite working Konstantin Ryabitsev
2021-08-14 20:46 ` Eric Wong
2021-08-14 22:09   ` Konstantin Ryabitsev [this message]

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://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210814220953.e2qgzhax2mslmkhv@nitro.local \
    --to=konstantin@linuxfoundation.org \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).