On 7/28/20 8:02 AM, Kevin Bowen wrote:
> Thanks. One other question: in my existing mm_cfg.py I have all three of
> the following:
> DEFAULT_HOST_NAME = 'mailman.domain.com'
> DEFAULT_URL_HOST = 'mailman.domain.com'
> DEFAULT_EMAIL_HOST = 'mailman.domain.com'
>
> In Defaults.py, it explains that D
Thanks. One other question: in my existing mm_cfg.py I have all three of
the following:
DEFAULT_HOST_NAME = 'mailman.domain.com'
DEFAULT_URL_HOST = 'mailman.domain.com'
DEFAULT_EMAIL_HOST = 'mailman.domain.com'
In Defaults.py, it explains that DEFAULT_HOST_NAME is deprecated, but the
language is u
On 7/27/20 11:22 AM, Kevin Bowen wrote:
> Am I understanding correctly that DEFAULT_URL_HOST in
> mm_cfg.py would be the way to accomplish that? And would that affect only
> the URLs used in the web UI, it wouldn't change anything about the actual
> mail handling under the hood?
That is correct, b
I'm not sure. I suspect it might be possible, but I'm not sure how, so if I
could just have mailman itself present the alternate URL, that would be
simpler.
Kevin Bowen
kevin.t.bo...@gmail.com
On Mon, Jul 27, 2020 at 1:46 PM Grant Taylor via Mailman-Users <
mailman-users@python.org> wrote:
> O
On 7/27/20 12:22 PM, Kevin Bowen wrote:
Hello,
Hi,
I'm trying to set up the mailman (2.1.9) web UI behind a load balancer
in order to offload the TLS to it (because this is an ancient machine
which doesn't support modern TLS versions, and newer browsers are
complaining about it). I need all
