James B. Byrne wrote:

On 28 Mar 2005 at 11:38, Mark Sapiro wrote:

...

Are the domains different. Were the list visible when you first created them? See http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029. htp . You probably need to run fix_url.py. You may also need to rebuild the archives with bin/arch if the "more info" links need to be fixed.

Here is the scenario. These lists are presently hosted on a server that is to be decommissioned. At that time the host name of that server will be transferred to the target machine as a CNAME. I wish to confirm that the lists are reachable from the network on the new host before cutting over. I infer from the instructions given above that in order to test this I will have to run:

bin/withlist -l -r fix_url <listname> -u

for each list, test, and when the host name change occurs then redo it on the same host with the old name again:

bin/withlist -l -r fix_url <listname> -u

In a similar fashion the archives need to be reconstructed using bin/arch.

Does this describe the situation?

Depending on just how much testing you want to do, you could skip all of the above. You won't see any lists on the http://newhostname.domain.tld/mailman/listinfo/ or the http://newhostname.domain.tld/mailman/admin pages, but you should still see and be able to administer the lists by going to http://newhostname.domain.tld/mailman/listinfo/<listname> and http://newhostname.domain.tld/mailman/admin/<listname> pages and visiting their archives.

Also, if you set VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py, you should also see all the public lists on the first two pages. This should be enough to let you know things are working without actually going through all the fix_url and bin/arch stuff.

-- Mark Sapiro msapiro@value.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

In the continuing saga of transferring mailman hosts (and moving from mailman mailman-2.1.5-8 to mailman-2.1.5-33) I performed the cut-over this morning using the following steps:

1. Shutdown SMTP service on the old mailman host (service sendmail stop)

2. Clear mqueue of all outstanding mailman deliveries (sendmail - qRmailman)

3. Clear data of all outstanding mailman administrative requests (as a practical matter there were none).

4. Shutdown Mailman service on the old mailman host (service mailman stop)

5. # cd /var/lib/mailman

6. # tar -xvf mailmanArchives.tar /var/lib/mailman/archives

7. # tar -xvf mailmanLists.tar /var/lib/mailman/lists

8. # gzip -S .gz mailman*tar

9. Down and remove mailman IP alias address on old host. (webmin Networking module - use ifconfig and edit etc/sysconfig entries if done manually)

10. Log on to new mailman host.

11. Stop mailman service (service mailman stop).

12. # cd /var/lib/mailman

13. # sftp <oldhost>; sftp> get /var/lib/mailman/mailman*.tar.gz; sftp> quit

14. tar -xvzf mailman*.tar.gz

15. /usr/lib/mailman/bin/check_perms -f -v

16. Add mailman IP alias address to new host NIC (webmin as above)

17. Start mailman service on new host (service mailman start)

18. Make sure that /etc/httpd/conf/httpd.conf is configured to listen on the new IP address.

19. Restart httpd service on new host (service httpd restart)

20. Browse to mailman.domain.tld/mailman - mailman Greeting page displays! All the public lists are listed! All the list subscriber pages are reachable by hyperlink! Subscriber requests work! All list administrative pages are reachable by hyperlink!
    Administrative requests work!

!!!Archives unreachable??????

The Link to a transferred list's archives gives the following error:

Forbidden

You don't have permission to access /pipermail/transferlist/ on this server.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. Apache/2.0.52 (CentOS) Server at mailman.domain.tld Port 80

/var/log/httpd/error_log:

[Tue Mar 29 11:37:55 2005] [error] [client 216.185.xxx.xxx] Symbolic link not allowed: /var/lib/mailman/archives/public/transferlist

However, a list that was created on the new machine links to its own archives without problems.

This is the mailman.conf file contents:

/etc/httpd/conf.d/mailman.conf

# # httpd configuration settings for use with mailman. #

ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ AllowOverride None Options ExecCGI Order allow,deny Allow from all </Directory>

Alias /pipermail/ /var/lib/mailman/archives/public/ Options Indexes MultiViews FollowSymLinks AllowOverride None Order allow,deny Allow from all </Directory>

# Uncomment the following line, replacing www.example.com with your server's # name, to redirect queries to /mailman to the listinfo page (recommended).

RedirectMatch ^/mailman[/]*$ http://mailman.domain.tld/mailman/listinfo

Now, the interesting thing is that the locally created lists have archive hyperlinks of the form mailman.domain.tld while the transferred lists have archive hyperlinks of the form <realhostname>.domain.tld. I am not sure how this can be but it is the case none the less. So, do I run bin/fix_url.py or add an additional redirect directive to conf.d/mailman.conf or do something else?

Any and all assistance greatly appreciated.

Regards, Jim

--
*** e-mail is not a secure channel *** mailto:byrnejb.<token>@harte-lyne.ca James B. Byrne Harte & Lyne Limited vox: +1 905 561 1241 9 Brockley Drive fax: +1 905 561 0757 Hamilton, Ontario <token> = hal Canada L8E 3C3

On 29 Mar 2005 at 9:49, Mark Sapiro wrote:

What happens if you go to http://mailman.domain.tld/pipermail/transferlist/

Forbidden

You don't have permission to access /pipermail/transferlist/ on this server.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

Do the directives in mailman.conf only apply to the mailman.domain.tld host?

To my knowledge, no. As far as I can tell the mailman.conf directives are applied across every IP address on the server.
There are no other redirects specified elsewhere that deal with \mailman or \pipermail and I lack sufficient experience with http directives to know whether or not this situation can be resolved by adding a second Redirectmatch for the fqdn host or if that would just override the one for the mailman aliased hostname.

Where are these hyperlinks of the form http://<realhostname>.domain.tld/pipermail/... Are they everywhere in the archive or just on the listinfo page?

All the archives, both the testlist and the others, have embedded http links of the form:

testlist/2004-July/index.html: <li><b><a href="http://mailman.domain.tld/mailman/listinfo/testlist">More info on this list...

and

/thread.html: <li><b><a href="http://mailman.domain.tld/mailman/listinfo/reallist">

Have you changed PUBLIC_ARCHIVE_URL in mm_cfg.py?

No.

Thanks, Jim

--
*** e-mail is not a secure channel *** mailto:byrnejb.<token>@harte-lyne.ca James B. Byrne Harte & Lyne Limited vox: +1 905 561 1241 9 Brockley Drive fax: +1 905 561 0757 Hamilton, Ontario <token> = hal Canada L8E 3C3