Re: issue with emails sent by bugzilla

[Eric Wong <e@80x24.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.