[Mailman-Users] Configuring mailman for a future domain name

[Paul Kleeberg]

Well I just decided to try it:

 From within the directory where I unpacked the tarball:
   ./configure --prefix=/var/mailman --with-cgi-gid=apache 
--with-mail-gid=mail --with-mailhost=fpen.org 
--with-urlhost=lists.fpen.org

then "make install" and it appears to have worked.  Default.py has 
the future URLs in it.  I could not find documentation for 
--with-mailhost or --with-urlhost in section 2 of the INSTALL file or 
anywhere else.

I agree with you.  I do not think it wise to edit the Defaults.py 
file but the above process looked like it might be more orthodox. 
I'll let you know if I encounter problems.

Paul

At 11:06 PM -0500 2/10/03, Matthew Davis wrote:
>* Paul Kleeberg (paul at fpen.org) wrote:
>>  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...
>
>That's correct.  By not modifing Defaults.py you put a 'legacy' url in there
>so its posed to confuse the next admin that takes your place (heaven
>forbid...).  But I believe thoes are there for example purporses, and your
>not lucky enough to have the 'defaults' work.
>
>You can edit Defaults.py, I personally see no harm in it other than it'll
>break future source patches and maybe you'll forget working syntex's if you
>mess something up.  But that's nothing that can't be solved by refering back
>to the Defaults.py in the tarball.

-- 
Paul Kleeberg
paul at fpen.org