From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.0.0.0/16 X-Spam-Status: No, score=-3.6 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out0.migadu.com (out0.migadu.com [IPv6:2001:41d0:2:267::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 0BCFA1F4D7 for ; Wed, 25 May 2022 01:44:40 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=kyleam.com header.i=@kyleam.com header.b="q9lUxzfC"; dkim-atps=neutral X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1653443076; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Wfbx57ucJZf7WAFEukppiXggE3w3MMUbHD8lw6QsC/w=; b=q9lUxzfCGuR4/Yh9IE4M9Dqpo4CfxsbzzLN1xbJC0M+I55A8VLW5cChw6j2iw83UXoHVFH 6OaEz+cak3f/e+Dehz52txVpmWFoSEkiuyv2yESBrKTgoa987zvH4n1WI7eDzcQvjpbHhU lwqzT94DbTtVlcscpxeEBtTBh9Nb5Agg4r9gUGmbTI6yQWZ+BrrOwnpvHUWNLHl1AuX0Zb ECITFPCHNBsbNqqfYDd2O9rVX8mgH+F5h+F/m6KKbZEiiwLaYc4oHJFH7cI9gUV64GM+WR 589zJxoc/nsmyfetDOFd2y1p95n1h5fD/qx7+9oPMShNo20MThd1fFvY8CyIQg== From: Kyle Meyer To: Mukund Sivaraman Cc: meta@public-inbox.org Subject: Re: Message-ID not found In-Reply-To: References: <871qwiqz4b.fsf@kyleam.com> Date: Tue, 24 May 2022 21:44:33 -0400 Message-ID: <87y1yqperi.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: kyleam.com List-Id: Mukund Sivaraman writes: > On Tue, May 24, 2022 at 07:39:32PM -0400, Kyle Meyer wrote: [...] >> > 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 Okay, so that link looks good. And then when I follow the link... > The webpage at that URL displays the > "Message-ID not found" error. ... I see the "Message-ID not found" error you describe. I pulled in your inbox and ran public-inbox-httpd (v1.7.0 and v1.8.0) locally: /test-list/Yo1VM9+M%2FsYJIZkN@d1/T/#t And then when I follow that link.I see the message for , as expected. Hmm. > [...] > Could there be a bug in how the '/' is treated as a separator in > public-inbox-httpd? Sure, though my guess is that there is something more setup-specific going on because 1) I don't see it when I try the inbox locally and 2) I think slashes are common enough in the wild yet I don't recall seeing similar reports for public-inbox.org inboxes, lore.kernel.org inboxes, or the inboxes that I host. As an example, at https://lore.kernel.org/git/?t=20220525002051 the link for "[PATCH v5 02/17] pack-mtimes: support reading .mtimes files" is to https://lore.kernel.org/git/Yo1aaLDmPKJ5%2Frh5@nand.local/T/#u I was able to successfully follow that to the message. Could there be something in your setup that's doing the second round of percent-encoding?