Konstantin Ryabitsev <[email protected]> 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/[email protected]/?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/[email protected]/ > > > > (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/[email protected]> > > 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%[email protected]/?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. -- unsubscribe: one-click, see List-Unsubscribe header archive: https://public-inbox.org/meta/
