What you say is correct but won't that put a "legacy" URL into Default.py whereas if I used the (undocumented?) parameters below, would it build Default.py with the correct URLs and therefore eliminate the necessity to add the entry to mm_cfg.py?

I suppose I should just shut-up and try it and see what happens...

At 9:23 PM -0500 2/9/03, Matthew Davis wrote:
After installation look at the DEFAULT_EMAIL_HOST section in
Mailman/Defaults.py  But as the top of the file says, don't make changes
there, make them to mm_cfg.py.

So you might want to add this to your mm_cfg.py
DEFAULT_EMAIL_HOST = lists.<domain>

But read on in that file and see if there are anymore option of interest to
you.

* Paul Kleeberg ([EMAIL PROTECTED]) wrote:
 I am installing Mailman on my production machine.  I want it to
 install with the same name as another machine where my lists are
 currently running with listproc.  In other words I am installing it
 on www.<domain> but I want the Mailman pages to be known as (and
 return the name) lists.<domain> which currently exists on a different
 box.  How do I do this?  Do I define it when running configure?  I do
 not see that as an option in the INSTALL file but I see
 > "--with-urlhost" and "--with-mailhost" in the "configure" file.

--
Matthew Davis
http://dogpound.vnet.net/

Truck Pulls: for people who cannot understand the WWF
--
Paul Kleeberg
[EMAIL PROTECTED]

------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [email protected]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to