[Mailman-Users] mailman webfrontend under different url

[Richard Barrett]

Timo

I have set up one of my systems to try and reproduce the problem you have 
been having.

Working through a RewriteRule that proxies the request seems to have problems.

I am looking at the source code of MM 2.1.2 to see how big a job it would 
be to fix the problems.

I will get back to you as soon as I have reached some conclusions on this.

Richard

At 21:30 28/04/2003, proescho at informatik.uni-muenchen.de wrote:
>Am Samstag, 26. April 2003 09:27 schrieb Richard Barrett:
> > You should:
> >
> > 1. leave the definition for DEFAULT_URL as None as per the default in
> > $prefix/Mailman/Defaults.py. It is only there for backwards compatibility
> > and its role has been taken over by DEFAULT_URL_HOST and
> > DEFAULT_URL_PATTERN.
> >
> > 2. use the $prefix/bin/withlist script fix_url.py to set the web_page_url
> > of your existing lists to use the value you have assigned in mm_cfg.py
> >
> > 3. do mailmanctl restart as a precaution
>
>i checked all this.
>
>DEFAULT_URL ist None (as it was before)
>I created my new lists only after i made the changes to mm_cfg.py,
>althoug i tried fix_paths as well.
>
>I still have the problem that the links do not point to the proper location.
>Following one working link to the "Mailman Administrator Authentication"
>of the mailman list, the problem can be seen very clear.
>
>Mailman list run by proescho at informatik.uni-muenchen.de (points to
>maillists.test.my.domain)
>Mailman administrative interface (requires authorization) (points to
>tools.my.domain)
>Overview of all maillists.test.rz.informatik.uni-muenchen.de mailing lists
>(points to maillists.my.domain)
>
>The next thing i noticed is, that the cgi action form points to
>/cgi-bin/mailman, althouth i configured /mailman/ in mm_cfg.py
>
>
>any more ideas?
>
>many thanks
>Timo PRoescholdt
>
> >
> > And all should now be well. Newly created lists will pick up your
> > DEFAULT_URL_HOST value. The problem you have is that existing lists are
> > using the old value and fix_url.py should fix that.
> >
> > Post again if this does not work for you.
> >
> > At 22:53 25/04/2003, proescho at informatik.uni-muenchen.de wrote:
> > >hi,
> > >
> > >im trying to run the webfrontend to mailman on a different server.
> > >For this i set up apache mod_proxy on this server to fetch the
> > >requiered pages from to "real" mailman server.
> > >
> > >The Problem ist that i cannot configure mailman to correctly change
> > >the DEFAULT_URL_HOST.
> > >
> > >i configured
> > >
> > >DEFAULT_URL       = 'http://tools.my.domain/mailman/'
> > >DEFAULT_EMAIL_HOST = 'maillists.test.my.domain'
> > >DEFAULT_URL_HOST = 'tools.my.domain'
> > >VIRTUAL_HOST_OVERVIEW=0
> > >
> > >in mm_cfg.py
> > >
> > >the rewrite module rewrites everything from
> > >http://tools.my.domain/mailman/(.*) to
> > >http://mailserver.my.domain/cgi-bin/mailman/$1
> > >
> > >
> > >the result,  when i display the default mailman/admin page, is
> > >that the "mailing list owerview ", and "create new list"-URLS  point
> > >to maillists.test.my.domain insted of tools.my.domain,
> > >only the administrative link to the Mailman List (which i created)
> > >points correctly to tools.my.domain.
> > >
> > >Also when i connect to the server directly
> > >(http://mailserver.my.domain/cgi-bin/mailman/admin) the links are not set
> > >correct.
> > >
> > >Why does mailman use the value of DEFAULT_EMAIL_HOST for these links?
> > >
> > >Mailman version is 2.1.1 on debian woody.
> > >The maillinglists shall appear unter mlists.test.my.domain
> > >
> > >
> > >thanks
> > >timo