From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.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=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id ABC1520248;
	Thu, 21 Mar 2019 16:13:57 +0000 (UTC)
Date: Thu, 21 Mar 2019 16:13:57 +0000
From: Eric Wong <e@80x24.org>
To: Ali Alnubani <alialnu@mellanox.com>
Cc: meta@public-inbox.org
Subject: Re: issue with emails sent by bugzilla
Message-ID: <20190321161357.hlkwygbabgup6tuk@dcvr>
References: <VI1PR05MB426985E6CC6D1D6EAC6BBD05D7420@VI1PR05MB4269.eurprd05.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <VI1PR05MB426985E6CC6D1D6EAC6BBD05D7420@VI1PR05MB4269.eurprd05.prod.outlook.com>
List-Id: <meta.public-inbox.org>

Ali Alnubani <alialnu@mellanox.com> wrote:
> Hi,
> 
> I'm having an issue where all emails that are sent by Bugzilla aren't found by the http daemon, and
> instead, I will get:
> "
> Message-ID <for@bar>
> not found
> 
> 1 partial match found:
> http://domain/list/foo@bar// (Which also redirects to the same page).
> ...
> ...
> "
> 
> I'm guessing that this happens because Bugzilla uses the Message-Id format "<foo@bar/>" (notice the '/').
> 
> Does anyone have an insight on this issue?

Might be a bug...(see below) I can check in a bit.

Does: http://domain/list/foo@bar%2F/ work?

Does NNTP work?  (e.g. lynx nntp://<HOST>/<MESSAGE_ID> ,
or nntp://<HOST>/<NEWSGROUP> )

You'll need a "newsgroup" entry in the ~/.public-inbox/config
file:

	[publicinbox "foo"]
		address = foo@example.com
		mainrepo = /path/to/foo
		newsgroup = inbox.comp.foo

> The emails are being imported successfully to the repository,
> but maybe they aren't indexed correctly?
>
> I would appreciate if someone could give me a starting point
> to where I should begin debugging this.

Likely a bug in the PublicInbox/WWW.pm code which does routing.
(sub call).  And maybe URL generation if the %2F example above
works.