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 fu
At 04:06 11/02/2003, Matthew Davis wrote:
* Paul Kleeberg ([EMAIL PROTECTED]) 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
* Paul Kleeberg ([EMAIL PROTECTED]) 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
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 s
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.
But read on in that file and see if there are anymore op
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. but I want the Mailman pages to be known as (and
return the name) lists. which currently e
