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: 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 E653E1F453; Wed, 24 Apr 2019 20:20:42 +0000 (UTC) Date: Wed, 24 Apr 2019 20:20:42 +0000 From: Eric Wong To: Ali Alnubani Cc: meta@public-inbox.org Subject: Re: issue with emails sent by bugzilla Message-ID: <20190424202042.xdut3hg3b2lalzaz@dcvr> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: List-Id: Ali Alnubani 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)