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: AS16276 188.165.0.0/16 X-Spam-Status: No, score=-3.4 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out2.migadu.com (out2.migadu.com [188.165.223.204]) (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 D4C301F4D7 for ; Tue, 24 May 2022 23:39:40 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=kyleam.com header.i=@kyleam.com header.b="SCEjdi/W"; 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=1653435575; 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=9EGfTe2ZM8vBnEMj2RADlLmnM3VYrzUjahnKNqrZNjc=; b=SCEjdi/WbHMUjdS7S5KFii1Tjq0Mvpst3LbxHKXzDDW+EqZHy2RFU3pm1hF/ZYFC9LcJHS lDHAiiwWwZC+ye1Fv8oKx42qtbdgCE9y4Z8Z0KsBCBUFY/OFJXi3AEzS/VfJRDQRmmWuSh 7WoQjALffxfEs9cInXIxqtfpyfYju+enYiVP2EcODldc/oDXrzit4xDUQroJH6iH5HxQ0T K7nHImH4BdvgeoBRkQZ0h/zwM/eos54B+AJTWcItphrkuD4jkwi20ot1U5WSTk4Fx5wd2U 36pS64o2FtmS1xeQyOlncLsGViZhAhPwEK9Fg1LNM+R/kIczKqAQWKVpOub46Q== From: Kyle Meyer To: Mukund Sivaraman Cc: meta@public-inbox.org Subject: Re: Message-ID not found In-Reply-To: References: Date: Tue, 24 May 2022 19:39:32 -0400 Message-ID: <871qwiqz4b.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: > 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? The slash looks percent-encoded one too many times: message ID: Yo1VM9+M/sYJIZkN@d1 | / -> %2F V percent-encoded once: Yo1VM9+M%2FsYJIZkN@d1 | % -> %25 V percent-encoded twice: Yo1VM9+M%252FsYJIZkN@d1 > "Message-ID not found" Hmm, I'm surprised by the trailing "/T". When I visit the above URL, I see Message-ID not found which is what I would expect. > 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/ Yes, the looks to match the URL you'd get by percent-encoding the "/" once (see above). > Could someone please check what the bug could be? > > Does public-inbox-httpd have a problem with the '/' character in > Message-IDs? Here's what https://inbox.banu.com/test-list/_/text/help/ says about slashes: Forward slash ('/') characters in the Message-IDs need to be escaped as "%2F" (without quotes). And here's the escaping that public-inbox does on the message ID (): # RFC3986, section 3.3: sub MID_ESC () { '^A-Za-z0-9\-\._~!\$\&\'\(\)\*\+,;=:@' } sub mid_escape ($) { uri_escape_utf8($_[0], MID_ESC) }