This reply mechanism is driving me a little weird--the reply function sends the messages to their individual authors, not the list. I hope I'm not breeching etiquette by redirecting my reply to the list.
Thanks, Mark, for your cogent and complete reply. The short answer and good thing about all of this is, the new system is supposed to be an as-near-100% replica as is possible of the old system, just everything re-installed and new, just keeping the old data. The new system already has the same identity and nameserver info as the old, the idea being to move data and other applications (which is already underway) and then switch the DNS records after the new environment has been thoroughly tested. I'll check the wiki's you mentioned and report on progress when done. On Thu, 05 Jun 2014 08:09:52 -0700, you wrote: >On 06/05/2014 04:27 AM, Steve Matzura wrote: >> I'm ready for the next step, which is to >> move an entire configuration and mail spool from an old Debian >> 5+Mailman 2.1.11 server. >> >> I imagine the spool (/var) files can just be tar'd and moved en masse. > > >Yes and no. You do not want to move the locks/, logs/ or qfiles/ >directories and spam/ is probably non-existent or empty. It's probably >not necessary to move anything from data/ but that reqwuires some thought. > > >> But what about mailman configuration files--mailing list info, that >> sort of thing? What should be moved, what should be re-created, etc.? > > > See the FAQ at <http://wiki.list.org/x/2oA9> > >You do want to move the lists/ directory in its entirety except maybe >the lists/mailman/ site list if you have already set that up on the new >server. That moves list configs, membership, etc. > >If host/domain names are changing, you will need to run fix_url; see the >FAQ at <http://wiki.list.org/x/mIA9>. > >You also maybe need to run bin/genaliases if your MTA uses mailman >generated aliases and you didn't move them from data/ > >Archives can be an issue. You can move the entire archives/private/ >directory and that should be OK, but people sometimes run into >permissions issues following that. It is best not to move >archives/public/, but if you do, make sure that you end up moving the >symlinks and not their targets. archives/public/ contains only symlinks >into archives/private and these will be created as appropriate by >Mailman as lists are accessed. > >If host/domain names are changing, The cleanest process is to move only >the archives/private/LISTNAME.mbox/LISTNAME.mbox files and rebuild the >HTML archive with bin/arch for each list, but there are downsides to >this. If some lists have scrub_nondigest = Yes, the scrubbed attachments >will be lost in this process, and if there are unescaped "From " lines >in messages that will cause problems too (see bin/cleanarch). ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
