From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <muks@mukund.org>
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=-3.2 required=3.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS,
	T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no
	version=3.4.2
Received: from mx.mukund.org (mx.mukund.org [IPv6:2a01:4f8:252:2ade:1::78])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id 0C4AA1F4D7
	for <meta@public-inbox.org>; Tue, 24 May 2022 23:59:32 +0000 (UTC)
Authentication-Results: dcvr.yhbt.net;
	dkim=pass (2048-bit key; unprotected) header.d=mukund.org header.i=@mukund.org header.b="WJ4VTDlH";
	dkim-atps=neutral
Date: Wed, 25 May 2022 05:29:27 +0530
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mukund.org; s=mail;
	t=1653436770; bh=nYpVxliJDjXqMog8BT4edGrgrXuqUD0HjzEnBezm474=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
	b=WJ4VTDlHYiU+ybnju2f2MqJFX1+sNYYAdHAeE7aCvoahOLO9OEBarKtXTL3LU7C7I
	 2phx2HoQqO13A3gs/hxsHI+7oH39Uzy8gU9AOzj5IwnSI6UkTdJODUczpAcelRqODf
	 nE1BeGhSmbOuAqtwXUH1mrLjTUSQ5SpljmuIpy9SKfbk2fmbQnm/h0vQCSG7DBX8av
	 vBBXg86BACfYGEqyWXHGIgFBCVkSFK3DvImerxCDHKG4RoC3lm2V4I9ADPyCIG3dL8
	 4nC8DlQUJ6loE7CstLKiw239kEG/1qmNE9m6M5XbG47UKapUiScaeuchTjDCYzoZm5
	 tXkOR6QaHz3ZA==
From: Mukund Sivaraman <muks@mukund.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: Message-ID not found
Message-ID: <Yo1xX+MNTMBmPITl@d1>
References: <Yo1c3oSzBKsRgQ4z@d1>
 <871qwiqz4b.fsf@kyleam.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <871qwiqz4b.fsf@kyleam.com>
List-Id: <meta.public-inbox.org>

Hi Kyle

On Tue, May 24, 2022 at 07:39:32PM -0400, Kyle Meyer wrote:
> Mukund Sivaraman writes:
> 
> > I'm testing public-inbox with a "test-list" to try to provide a HTTP
> > interface to mailing list archives. I'm using stock
> > public-inbox-1.7.0-2.fc35.noarch on Fedora 35.
> >
> > List emails are injected by public-inbox-mda. public-inbox-httpd
> > displays an error at this URL:
> >
> > https://inbox.banu.com/test-list/Yo1VM9+M%252FsYJIZkN@d1/T/
> 
> What's the source of this URL?

In the thread index at: https://inbox.banu.com/test-list/

The 2nd thread with subject "About Pluto" links to:

https://inbox.banu.com/test-list/Yo1VM9+M%2FsYJIZkN@d1/T/#t

The webpage at that URL displays the
"Message-ID <Yo1VM9+M/sYJIZkN@d1/T> not found" error.

In this case, there is just one escape "%2F" in the URL for '/', and
from the error message it has correctly unescaped the Message-ID except
for the trailing "/T".

Could there be a bug in how the '/' is treated as a separator in
public-inbox-httpd?

		Mukund