[Mailman-Users] Problem With Mailman Migration

2008-04-02 Thread Michael J Wise
I've recently moved our mailman service to a different server. It 
appears to be working well in all regards but one. When I attempt to 
manage a list from the webpage interface on the correct server it sends 
me to the admin password authorization page on the old server. All lists 
constantly refer back to the old server for admin tasks.

I have set the mm_cfg.py file properly with our new servers address 
(x.domain.tld), and have run withlist -l -r fix_url both in -a 
mode and individually on the various lists with no results. I also would 
like to know how to shutdown the old mailman admin web page. I have 
edited out the reference to mailman in httpd.conf and restarted the 
daemon with no success; there are no aliases to mailman in the 
httpd.conf file aside from what I edited.

The server platform is Mac Server 10.4.11. Thank you for your help.

-- 
Michael J Wise
Technology Coordinator
Thomas Jefferson School
4100 S. Lindbergh Blvd.
St. Louis, MO 63127
(314)843-4152 x171

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp


Re: [Mailman-Users] Problem With Mailman Migration

2008-04-02 Thread Mark Sapiro
Michael J Wise wrote:

I've recently moved our mailman service to a different server. It 
appears to be working well in all regards but one. When I attempt to 
manage a list from the webpage interface on the correct server it sends 
me to the admin password authorization page on the old server. All lists 
constantly refer back to the old server for admin tasks.

I have set the mm_cfg.py file properly with our new servers address 
(x.domain.tld), and have run withlist -l -r fix_url both in -a 
mode and individually on the various lists with no results.


This is exactly the kind of thing that fix_url is supposed to fix. The
fact that it doesn't indicates problems with your host settings in
Defaults.py/mm_cfg.py

What you want to start with in mm_cfg.py is (with your own host names
of course)

DEFAULT_URL_HOST = 'www.example.com'
DEFAULT_EMAIL_HOST = 'example.com'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

If you don't have that, do that, restart Mailman and run fix_url again


I also would 
like to know how to shutdown the old mailman admin web page. I have 
edited out the reference to mailman in httpd.conf and restarted the 
daemon with no success; there are no aliases to mailman in the 
httpd.conf file aside from what I edited.


Then there is some non-obvious magic at work. If you don't have the
ScriptAlias for Mailman in httpd.conf, how is httpd getting to those
CGI scripts?  You might get a clue from your httpd access_log.


The server platform is Mac Server 10.4.11. Thank you for your help.


Which I assume is still the Apple modified Mailman 2.1.5. Maybe these
are Apple questions.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp