user/dev discussion of public-inbox itself
 help / color / Atom feed
* issue with emails sent by bugzilla
@ 2019-03-21 13:45 Ali Alnubani
  2019-03-21 16:13 ` Eric Wong
  2019-04-23 12:39 ` Ali Alnubani
  0 siblings, 2 replies; 5+ messages in thread
From: Ali Alnubani @ 2019-03-21 13:45 UTC (permalink / raw)
  To: meta

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?
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.

Thanks,
Ali

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: issue with emails sent by bugzilla
  2019-03-21 13:45 issue with emails sent by bugzilla Ali Alnubani
@ 2019-03-21 16:13 ` Eric Wong
  2019-03-21 17:29   ` Eric Wong
  2019-04-23 12:39 ` Ali Alnubani
  1 sibling, 1 reply; 5+ messages in thread
From: Eric Wong @ 2019-03-21 16:13 UTC (permalink / raw)
  To: Ali Alnubani; +Cc: meta

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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: issue with emails sent by bugzilla
  2019-03-21 16:13 ` Eric Wong
@ 2019-03-21 17:29   ` Eric Wong
  0 siblings, 0 replies; 5+ messages in thread
From: Eric Wong @ 2019-03-21 17:29 UTC (permalink / raw)
  To: Ali Alnubani; +Cc: meta

Eric Wong <e@80x24.org> wrote:
> Might be a bug...(see below) I can check in a bit.
> 
> Does: http://domain/list/foo@bar%2F/ work?

Just tested, both of the following work without modifications:

https://public-inbox.org/test/aaffffffadkljfadsfasdfasdfasdfffffffas@oops%2F/
https://public-inbox.org/test/oops@test%2F/

Are you running a recent-ish revision off git?

I fixed some bugs at commit 4cf7804c2b263e4a92447315f534f76416d4ffad
("additional tests for bad Message-IDs in URLs") back last June
thanks to Leah's bug report.


Is your instance publically accessible?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* RE: issue with emails sent by bugzilla
  2019-03-21 13:45 issue with emails sent by bugzilla Ali Alnubani
  2019-03-21 16:13 ` Eric Wong
@ 2019-04-23 12:39 ` Ali Alnubani
  2019-04-24 20:20   ` Eric Wong
  1 sibling, 1 reply; 5+ messages in thread
From: Ali Alnubani @ 2019-04-23 12:39 UTC (permalink / raw)
  To: Eric Wong; +Cc: meta

Hi Eric,

I apologize again for my late response, I never got your replies (my
mail server must have quarantined them for some reason).

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 '/').
>>>

Eric Wong <e@80x24.org> wrote:
>> Might be a bug...(see below) I can check in a bit.
>>
>> Does: http://domain/list/foo@bar%2F/ work?

> Just tested, both of the following work without modifications:
>
> https://public-inbox.org/test/aaffffffadkljfadsfasdfasdfasdfffffffas@oops%2F/
> https://public-inbox.org/test/oops@test%2F/
>
> Are you running a recent-ish revision off git?
>
> I fixed some bugs at commit 4cf7804c2b263e4a92447315f534f76416d4ffad
> ("additional tests for bad Message-IDs in URLs") back last June
> thanks to Leah's bug report.
>
>
> Is your instance publically accessible?

I just checked and turns out this was an issue my nginx configurations.

I use nginx to proxy_pass requests to public-inbox-httpd, and the urls must
have been passed incorrectly.

Sorry about the formatting of the email, and thank you for your help :)

Thanks,
Ali

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: issue with emails sent by bugzilla
  2019-04-23 12:39 ` Ali Alnubani
@ 2019-04-24 20:20   ` Eric Wong
  0 siblings, 0 replies; 5+ messages in thread
From: Eric Wong @ 2019-04-24 20:20 UTC (permalink / raw)
  To: Ali Alnubani; +Cc: meta

Ali Alnubani <alialnu@mellanox.com> wrote:
> Hi Eric,
> 
> I apologize again for my late response, I never got your replies (my
> mail server must have quarantined them for some reason).

No worries, at least we have archives :>

I don't have much experience dealing with outlook.com so I'm not
sure what deliverability things I can do on my end; but yeah,
the big players making life hard for small-time mail admins is
a major reason this project exists.

> I just checked and turns out this was an issue my nginx configurations.
> 
> I use nginx to proxy_pass requests to public-inbox-httpd, and the urls must
> have been passed incorrectly.

Thanks for the followup.  Perhaps we should add a sample nginx
config file to get users setup, more easily.  Care to provide
one?  I haven't kept up with nginx changes in recent years...

But other HTTPS proxies could work just as well for
public-inbox-httpd (and Varnish).

Long-term, I plan to add HTTPS support to public-inbox-httpd
(since -nntpd needs TLS, too).  That could make nginx
unnecessary for HTTPS and make setup easier.

(And Cache::FastMmap may eliminate the need for Varnish for
 hug-of-death situations)

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, back to index

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-03-21 13:45 issue with emails sent by bugzilla Ali Alnubani
2019-03-21 16:13 ` Eric Wong
2019-03-21 17:29   ` Eric Wong
2019-04-23 12:39 ` Ali Alnubani
2019-04-24 20:20   ` Eric Wong

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror http://public-inbox.org/meta
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
	nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
	nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
	nntp://news.gmane.org/gmane.mail.public-inbox.general

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox