Re: [Mailman-Users] Problems with relocating a list
You probably followed some of my instructions. I've not had a chance to get back to update them. In the mailman list directories you'll find that there are links to the archives. I had the same issue after I did mine, it took a bit to figure it out but simply deleting the links and making new ones to the correct location on the new machine fixed it for me.
----- Original Message Follows ----- From: Anthony Chavez acc@anthonychavez.org To: mailman-users@python.org Subject: [Mailman-Users] Problems with relocating a list Date: Tue, 21 Sep 2004 12:49:13 -0600
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Moving a Mailman list from one server to a new one has been a *very* smooth process for the most part, but I'm noticing some small quirks in the wake.
Here's an account of how I accomplished this.
Installed Mailman 2.1.5, Postfix 2.1.4, and Apache 2.0.50 on the new server. These versions exactly match the ones on the old server.
Went through the process dictated in FreeBSD-post-install-notes, INSTALL, README, and README.POSTFIX, which essentially involved editing main.cf, httpd.conf, adding MTA = 'Postfix' to mm_cfg.py and creating the "mailman" list.
Under the direction of section 3.4 in the FAQ Wizard, I copied the data, archives and lists directories from the old server to the new one. But rather than clobbering the pre-existing directories, I copied only the *relevant* directories from archives and lists (i.e. archives/private/listname* and lists/listname). Nothing was copied from data and the "mailman" list was not copied.
Ran withlist -l -r fix_url listname && genaliases
Started postfix and qrunner.
Configured Apache on the old site to proxy and Postfix to relay to the new server while DNS changes propagated.
Now, the aforementioned quirks:
The old lists are not advertised on the new Web site.
Apache will not let me access the public archives (that were private before the move) and I get a 403. I'm sure this has to do with Apache 2's default deny policy, but not entirely sure how to deal with it (I'm still somewhat of an Apache 2 newbie, but I've had a few years experience with 1.x).
Any assistance would be greatly appreciated.
Cheers!
Anthony Chavez http://www.anthonychavez.org/ mailto:acc@anthonychavez.org jabber:acc@jabber.anthonychavez.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin)
iD8DBQFBUHesbZTbIaRBRXERAoIGAJ0fYE5OA0qsowSA8C15dZ+J/dlGdQCeNbEQ M0fmXySbfdTfpReNuH3/2hw= =kfs3 -----END PGP SIGNATURE-----
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/
==================== Kevin W. Gagel Network Administrator (250) 561-5848 local 448 (250) 562-2131 local 448
The College of New Caledonia, Visit us at http://www.cnc.bc.ca Virus scanning is done on all incoming and outgoing email.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, 21 Sep 2004 14:37:22 -0700 "Kevin W. Gagel" gagel@cnc.bc.ca wrote:
You probably followed some of my instructions. I've not had a chance to get back to update them. In the mailman list directories you'll find that there are links to the archives. I had the same issue after I did mine, it took a bit to figure it out but simply deleting the links and making new ones to the correct location on the new machine fixed it for me.
Thank you for your response.
I've determined that in this case, it's a simple matter of misconfiguration. Attempts to view list advertisements at http://www.mydomain.com/mailman/listinfo yields no results. However, connecting to http://mydomain.com/mailman/listinfo works fine.
However, Apache 2 still 403s when attempting to access /pipermail/gubug/, using either hostname....
Anthony Chavez http://www.anthonychavez.org/ mailto:acc@anthonychavez.org jabber:acc@jabber.anthonychavez.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, 21 Sep 2004 23:32:25 -0600 Anthony Chavez acc@anthonychavez.org wrote:
However, Apache 2 still 403s when attempting to access /pipermail/listname/, using either hostname....
My question at this point is this: what Mailman directories should Apache allow access to? Section 4 of the INSTALL document says to allow access from all for /usr/local/mailman/cgi-bin, but in order to access my public archives I also must enable it for /usr/local/mailman/archives/public.
Anthony Chavez http://www.anthonychavez.org/ mailto:acc@anthonychavez.org jabber:acc@jabber.anthonychavez.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 22 Sep 2004 11:58:11 -0600 Anthony Chavez acc@anthonychavez.org wrote:
On Tue, 21 Sep 2004 23:32:25 -0600 Anthony Chavez acc@anthonychavez.org wrote:
However, Apache 2 still 403s when attempting to access /pipermail/listname/, using either hostname....
My question at this point is this: what Mailman directories should Apache allow access to? Section 4 of the INSTALL document says to allow access from all for /usr/local/mailman/cgi-bin, but in order to access my public archives I also must enable it for /usr/local/mailman/archives/public.
Never did get a response to this. Can anyone point me in the right direction?
Naturally, I'd like to only allow access to those parts of Mailman that are *absolutely* necessary to be accessed by subscribers. I'm interested to know if anyone has already distilled these paths before I start experimenting.
Thanks!
Anthony Chavez http://anthonychavez.org/ mailto:acc@anthonychavez.org jabber:acc@jabber.anthonychavez.org
On Sat, Nov 20, 2004 at 12:36:53AM -0700, Anthony Chavez wrote:
On Wed, 22 Sep 2004 11:58:11 -0600 Anthony Chavez acc@anthonychavez.org wrote:
My question at this point is this: what Mailman directories should Apache allow access to? Section 4 of the INSTALL document says to allow access from all for /usr/local/mailman/cgi-bin, but in order to access my public archives I also must enable it for /usr/local/mailman/archives/public.
You will need to allow access to the scripts in /usr/local/mailman/cgi-bin, and the files in the /usr/local/mailman/archives directory tree. (You will also want to allow Apache to follow symbolic links from /usr/local/mailman/archives/public into the private directory.)
participants (3)
-
Anthony Chavez -
Jim Tittsler -
Kevin W. Gagel