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 A61211F4D7
	for <meta@public-inbox.org>; Tue, 24 May 2022 22:32:04 +0000 (UTC)
Authentication-Results: dcvr.yhbt.net;
	dkim=pass (2048-bit key; unprotected) header.d=mukund.org header.i=@mukund.org header.b="mms+EFlS";
	dkim-atps=neutral
Date: Wed, 25 May 2022 04:01:58 +0530
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mukund.org; s=mail;
	t=1653431520; bh=C/wss7YKVA3ZuEnqVvNnEHUXuAq/Cyyt3IOrAmblsls=;
	h=Date:From:To:Subject:From;
	b=mms+EFlSmNfv1JzizEiFG5rI/KXutO5i6idfAbNW+UaqFqAKrmk5oqwouEfzWZkqe
	 Y+AUNw/JN7Kd2C06iiRNJVVSRDznGb+b5yoqnTGp4LjKggnNk5RXxsCufuZKExvLVi
	 Vvjo3YbzYGzOnWoRj7Xn7Oi+BBUctf+l1e0VOBGbx7Xl6bg+TYe8i9IzhNLscDRMZA
	 rgg0THVoZthNgL617f8tP7zef+dd6SAf+LplO+KfqDLK6bnMDT0Xg+gJeE3EaN2lRj
	 qksM9Lq7xHrXvadChY9rRAysLmCcePGZkfcVd6x0fWqXMTVjvho7/IokjW8bH+iMME
	 rDcgEw67y2m0w==
From: Mukund Sivaraman <muks@mukund.org>
To: meta@public-inbox.org
Subject: Message-ID not found
Message-ID: <Yo1c3oSzBKsRgQ4z@d1>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
List-Id: <meta.public-inbox.org>

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/

"Message-ID <Yo1VM9+M/sYJIZkN@d1/T> not found"

The ASCII encoded Message-ID is "Yo1VM9+M/sYJIZkN@d1" generated by the
Mutt client.

The corresponding message exists:
https://inbox.banu.com/test-list/Yo1VM9+M%2FsYJIZkN@d1/

Its parent (In-Reply-To) exists:
https://inbox.banu.com/test-list/Yo1UiImlt7Sh+I68@d1/

and the parent's thread can be browsed:
https://inbox.banu.com/test-list/Yo1UiImlt7Sh+I68@d1/T/

Could someone please check what the bug could be?

Does public-inbox-httpd have a problem with the '/' character in
Message-IDs?

The inbox was init'ed using -V 2. I have tried running:

  public-inbox-index --reindex --all --rethread

but it hasn't fixed it.

		Mukund