From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@yhbt.net>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00,
	T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no
	version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 9BE0C1F670;
	Mon,  7 Mar 2022 22:14:01 +0000 (UTC)
Date: Mon, 7 Mar 2022 22:14:01 +0000
From: Eric Wong <e@yhbt.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Tom Lendacky <thomas.lendacky@amd.com>, meta@public-inbox.org
Subject: Re: Issue with lore.kernel.org links
Message-ID: <20220307221401.M533070@dcvr>
References: <7ced6131-0c26-319f-58c8-80a1ec5ef336@amd.com>
 <20220307155918.72j2rmnp6qwk3obl@meerkat.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20220307155918.72j2rmnp6qwk3obl@meerkat.local>
List-Id: <meta.public-inbox.org>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Mon, Mar 07, 2022 at 09:44:06AM -0600, Tom Lendacky wrote:
> > Hi Konstantin,
> > 
> > Boris Petkov suggested I email you about an issue I'm having with some of
> > the links on lore.kernel.org.  For example, I performed a search and was
> > presented with a result page:
> > 
> > https://lore.kernel.org/all/Yh3r1PSx/fjqoBB3@nazgul.tnic/?q=Singh
> > 
> > Paging down slightly, you'll see the patch series links. If I click on any
> > of them, for example, the link associated with the line:
> > 
> >   2022-02-24 16:55 ` [PATCH v11 08/45] x86/sev: " Brijesh Singh
> >   https://lore.kernel.org/all/Yh3r1PSx/20220224165625.2175020-9-brijesh.singh@amd.com/
> > 
> >   (Note, that line should really read:
> >    2022-02-24 16:55 ` [PATCH v11 08/45] x86/sev: Detect/setup SEV/SME features earlier in boot Brijesh Singh)
> > 
> > I'm taken to a page that reads:
> > Message-ID <Yh3r1PSx/20220224165625.2175020-9-brijesh.singh@amd.com>
> > not found
> > 
> > Perhaps try an external site:
> > ...
> > 
> > I'm not sure what the issue is, but wanted to let you know.
> 
> The problem is that the message-id has a '/' in it, and it's causing some
> problems. E.g. if you escape the slash, all links work properly:
> https://lore.kernel.org/all/Yh3r1PSx%2FfjqoBB3@nazgul.tnic/?q=Singh
> 
> I'm cc'ing the public-inbox list with the hopes that we can figure out what's
> the best way to handle this situation.

'%2F' is the best we can do for now...

Now, if there's a tool generating URLs where '%2F' isn't used,
then that tool needs fixing.

Newer mutt defaults are painful.  Upstream added $message_id_format
to workaround it (<%Y%02m%02d%02H%02M%02S.G%c%p@%f> for the old default).
Still a totally unnecessary change on mutt's part IMNSHO but I failed
to convince mutt upstream to avoid '/' in Message-IDs by default.