I've just spent most of an entire evening trying to understand where Mailman (i.e., the scripts that build Mailman - configure & make - and Mailman itself) gets its identity from. I'm attempting to install Mailman on the host charlie. charlie is the web host for pretorious.net and funkymonkeybutt.com. A reverse-DNS lookup of charlie's IP address will return pretorious.net. Mailman will only be accessible via www.funkymonkey.com (once I get it installed and configured correctly).
I've tried modifying the 'www' and 'url' values of configure and configure.in
I've tried passing --host and --target to ./configure
I've tried modifying Mailman/mm_cfg.py
...and nothing seems to work in a predictable manner. _Sometimes_ the
values that the cgi scripts return (via HTTP) contain the hostname
'charlie' and _sometimes_ they contain one of the values set using the
methods listed above. e.g., If I use hostname www.funkymonkeybutt.com
to
temporarily set the hostname env value, make
begins using pretorious.net
instead of charlie. And Mailman pretty much ignores the Mailman/mm_cfg.py
values.
Everyone seems to talk about Mailman like it practically installs itself and then goes about laying golden eggs. What could possibly be causing me to be the only person on this list with basic installation?
-- Eric P. Los Gatos, CA
On Monday, Sep 24, 2001, Eric Pretorious wrote:
I've just spent most of an entire evening trying to understand where Mailman (i.e., the scripts that build Mailman - configure & make - and Mailman itself) gets its identity from. I'm attempting to install Mailman on the host charlie. charlie is the web host for pretorious.net and funkymonkeybutt.com. A reverse-DNS lookup of charlie's IP address will return pretorious.net. Mailman will only be accessible via www.funkymonkey.com (once I get it installed and configured correctly).
Why don't you just edit mm_cfg.py to contain the hostname that you want? It's easy... here's the relevant part of mine:
=====
############################################### # Here's where we get the distributed defaults.
from Defaults import *
################################################## # Put YOUR site-specific settings below this line.
MAILMAN_URL = 'http://www.list.org/'
# Site-specific settings DEFAULT_HOST_NAME = 'coxcentral.com' # DEFAULT_URL must end in a slash! DEFAULT_URL = 'http://lists.coxcentral.com/mailman/' PUBLIC_ARCHIVE_URL = '/archives'
MAILMAN_OWNER = 'mailman-owner@%s' % DEFAULT_HOST_NAME
=====
Note that you have to have MAILMAN_OWNER in there (even though it looks the same as the default) because you're changing the DEFAULT_HOST_NAME.
-- Paul Cox <paul at coxcentral dot com> Kernel: 2.4.7-12.3mdk - Uptime: 7 days 12 hours 24 minutes.
On Tuesday 25 September 2001 05:24 pm, Paul Cox wrote:
On Monday, Sep 24, 2001, Eric Pretorious wrote:
I've just spent most of an entire evening trying to understand where Mailman (i.e., the scripts that build Mailman - configure & make - and Mailman itself) gets its identity from. I'm attempting to install Mailman on the host charlie. charlie is the web host for pretorious.net and funkymonkeybutt.com. A reverse-DNS lookup of charlie's IP address will return pretorious.net. Mailman will only be accessible via www.funkymonkey.com (once I get it installed and configured correctly).
Why don't you just edit mm_cfg.py to contain the hostname that you want? It's easy... here's the relevant part of mine:
This will only affect new lists as they are created. If you wan't to change lists that already exist you'll need to log into the web interface for your list (if you can!) and change the value for the option:
"Base URL for Mailman web interface. The URL must end in a
single "/". See also the details for an important warning when
changing this value."
(the last option on the General Options page)
if you have issues with the address that the lists are sending out in their emails then you need to change the value for the option" "Host name this list prefers."
(second to last option)
if you don't like these two methods you could always do some bin/withlist black magic.
- Ben
ps. Mailman 2.0.6 is assumed since it wasn't specified.
On Tue, 25 Sep 2001, Paul Cox wrote:
Why don't you just edit mm_cfg.py to contain the hostname that you want? It's easy... here's the relevant part of mine:
############################################### # Here's where we get the distributed defaults.
from Defaults import *
################################################## # Put YOUR site-specific settings below this line.
MAILMAN_URL = 'http://www.list.org/'
# Site-specific settings DEFAULT_HOST_NAME = 'coxcentral.com' # DEFAULT_URL must end in a slash! DEFAULT_URL = 'http://lists.coxcentral.com/mailman/' PUBLIC_ARCHIVE_URL = '/archives'
MAILMAN_OWNER = 'mailman-owner@%s' % DEFAULT_HOST_NAME
Paul:
Sheer brilliance! The MAILMAN_OWNER setting puts me over-the-top. I think I'll just it "good" and move on to customizing the general HTML.
Thanks!
-- Eric P. Los Gatos, CA
participants (4)
-
Ben Burnett
-
Eric Pretorious
-
eric-mailman@pretorious.net
-
Paul Cox