unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
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
Date: Wed, 24 Apr 2019 20:20:42 +0000	[thread overview]
Message-ID: <20190424202042.xdut3hg3b2lalzaz@dcvr> (raw)
In-Reply-To: <DB6PR0501MB2167DA552D7AA44AF8BB9F7BD7230@DB6PR0501MB2167.eurprd05.prod.outlook.com>

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)

      reply	other threads:[~2019-04-24 20:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190424202042.xdut3hg3b2lalzaz@dcvr \
    --to=e@80x24.org \
    --cc=alialnu@mellanox.com \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).