Re: [Mailman-Users] Problem Migrating Mailman to New Server
Dennis Putnam wrote: OK, now I understand what you are asking. I restarted mailman and let it run for several minutes with no error in /var/log/mailman/error. Then I submitted a help to -request. That is when the error occurred. I suppose it might mot be the help request per se but rather anything that causes mailman to do something. I tried to run a couple of other commands and they all do the same thing. I am reluctant to actually send a test to the list out of fear it might destroy something and make matters worse. Here is the traceback. Oct 24 17:30:09 2008 (5961) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1' Oct 24 17:30:09 2008 (5961) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/ArchRunner.py, line 73, in _dispose mlist.ArchiveMail(msg) File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 216, in ArchiveMail h.processUnixMailbox(f) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 580, in processUnixMailbox self.add_article(a) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 632, in add_article article.parentID = parentID = self.get_parent_info(arch, article) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 664, in get_parent_info article.subject) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 311, in getOldestArticle self.__openIndices(archive) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 251, in __openIndices t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 61, in __init__ self.lock() File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 77, in lock self.lockfile.lock() File /usr/lib/mailman/Mailman/LockFile.py, line 243, in lock self.__write() File /usr/lib/mailman/Mailman/LockFile.py, line 422, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1' Oct 24 17:30:09 2008 (5961) SHUNTING: 1224883807.7050669+416c5717ff6f07bcc5748843bf07afb92dc4b212 ArchRunner is trying to archive a message it found in qfiles/archive/. It has encountered the lock permission denied and moved the message to qfiles/shunt/1224883807.7050669+416c5717ff6f07bcc5748843bf07afb92dc4b212.pck What is the message (use bin/dumpdb or bin/show_qfiles to see it). Here is the process (shouldn't this be running as 'mailman'?): mail 5961 0.1 0.7 11100 7356 ?R17:28 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s How are you starting Mailman. Are you running bin/mailmanctl as root or starting it as a 'service' as root? If so, it should be setting the uid and gid of itself and the runners as those of MAILMAN_USER and MAILMAN_GROUP from Defaults.py/mm_cfg.py and supplemental groups as those associated with MAILMAN_USER. So, if I understand your configuration, MAILMAN_USER:MAILMAN_GROUP are mailman:mail. If that's correct, I would expect the runners to be running as user 'mailman'. That may be the cause of the permissions error. -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Mark Sapiro wrote: OK, this is confusing. The public archive directories are links (lrwxrwxrwx) to the private archive directories which contain the actual archives. Those directories are drwxrwsr-x. The files are 755. If the files are 755, that's OK, but they aren't executable so they really should be 644. Sorry. They are indeed 644. Brain was out to lunch. Yes, that's why I said (was). However, if CommandRunner is now 2773, it is likely that 2771 is another runner and was at the time. In any case, 2771 was the pid of the process that tried to create the lock. I asked, because I don't believe that the IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.2271.2' error came from your 'help' command mailed to -request. In any case, where did this error come from?. If it is in Mailman's error log, there should also be a traceback. What is that? OK, now I understand what you are asking. I restarted mailman and let it run for several minutes with no error in /var/log/mailman/error. Then I submitted a help to -request. That is when the error occurred. I suppose it might mot be the help request per se but rather anything that causes mailman to do something. I tried to run a couple of other commands and they all do the same thing. I am reluctant to actually send a test to the list out of fear it might destroy something and make matters worse. Here is the traceback. Oct 24 17:30:09 2008 (5961) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1' Oct 24 17:30:09 2008 (5961) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/ArchRunner.py, line 73, in _dispose mlist.ArchiveMail(msg) File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 216, in ArchiveMail h.processUnixMailbox(f) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 580, in processUnixMailbox self.add_article(a) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 632, in add_article article.parentID = parentID = self.get_parent_info(arch, article) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 664, in get_parent_info article.subject) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 311, in getOldestArticle self.__openIndices(archive) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 251, in __openIndices t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 61, in __init__ self.lock() File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 77, in lock self.lockfile.lock() File /usr/lib/mailman/Mailman/LockFile.py, line 243, in lock self.__write() File /usr/lib/mailman/Mailman/LockFile.py, line 422, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1' Oct 24 17:30:09 2008 (5961) SHUNTING: 1224883807.7050669+416c5717ff6f07bcc5748843bf07afb92dc4b212 Here is the process (shouldn't this be running as 'mailman'?): mail 5961 0.1 0.7 11100 7356 ?R17:28 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s Thanks for your patience and continued help. signature.asc Description: PGP signature signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Mark Sapiro wrote: Prior to 2.1.10, check_perms had a bug and didn't check the owner and group permissions on the archives/private directory itself. Permissions should be 2771 or maybe 2770 (drwxrws--x or drwxrws---). If archives/private is not o+x, it needs to be owned by the web server for public archive URLs to work. I changed it to 2771 (I just needed too do a chmod o-r). Subordinate directories should be 2775 (drwxrwsr-x) and subordinate files 0664 (-rw-rw-r--) except for the archives/private/*/database/ directory and subordinate files which should not have 'other' permissions. OK, this is confusing. The public archive directories are links (lrwxrwxrwx) to the private archive directories which contain the actual archives. Those directories are drwxrwsr-x. The files are 755. It is not clear to my why a help command to the -request address would try to lock the archive. Is (was) 2271 the pid of CommandRunner? No, it is 2273. I'm not sure I understand this question. The pid would depend on when qrunner was launched. I have stopped and started mailman several times so the pid could be anything, couldn't it? signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Dennis Putnam wrote: Mark Sapiro wrote: Prior to 2.1.10, check_perms had a bug and didn't check the owner and group permissions on the archives/private directory itself. Permissions should be 2771 or maybe 2770 (drwxrws--x or drwxrws---). If= archives/private is not o+x, it needs to be owned by the web server for public archive URLs to work. I changed it to 2771 (I just needed too do a chmod o-r). Then that wasn't the problem. Subordinate directories should be 2775 (drwxrwsr-x) and subordinate files 0664 (-rw-rw-r--) except for the archives/private/*/database/ directory and subordinate files which should not have 'other' permissions. OK, this is confusing. The public archive directories are links (lrwxrwxrwx) to the private archive directories which contain the actual archives. Those directories are drwxrwsr-x. The files are 755. If the files are 755, that's OK, but they aren't executable so they really should be 644. And yes, the contents of archives/public are symlinks (the permissions of which are irrelevant). That's so archives can be changed from public to private and vice versa by just removing/creating symlinks. It is not clear to my why a help command to the -request address would try to lock the archive. Is (was) 2271 the pid of CommandRunner? No, it is 2273. I'm not sure I understand this question. The pid would depend on when qrunner was launched. I have stopped and started mailman several times so the pid could be anything, couldn't it? Yes, that's why I said (was). However, if CommandRunner is now 2773, it is likely that 2771 is another runner and was at the time. In any case, 2771 was the pid of the process that tried to create the lock. I asked, because I don't believe that the IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.2271.2' error came from your 'help' command mailed to -request. In any case, where did this error come from?. If it is in Mailman's error log, there should also be a traceback. What is that? -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
That advanced the ball. The problem was that the mailman's primay group was mailman (Mandriva automagically creates a primary group for each user with the same name as the user name, that has been a problem more than once). I changed the primary group to mail. Thanks. However, I am now getting permission denied errors on the database folders. IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.2271.2' I ran check_perms and all is OK. This has always been about ownership/permissions but I question why check_perms doesn't/won't fix it. What is it supposed to be? FWIW, the owner:group for /usr/lib/mailman and /var/lib/mailman trees is mailman:mail. I should also note that the command (it was just a help command to req) did work but I did not want to try actually mailing something to a list until this is all fixed. Thanks again for your help and my ISP seems to be accepting email from the python.org domain again. Mark Sapiro wrote: Where are your aliases? The mail wrapper is compiled to to expect to be invoked by the 'mail' group. Postfix will invoke the wrapper as the user and that user's primary group corresponding to the owner of the aliases.db file in which the pipe command was found. I.e., if the aliases.db file is userx:groupy, postfix will invoke the wrapper as userx:groupx where groupx is userx's primary group. -- Mark Sapiro mark at msapiro.net http://mail.python.org/mailman/listinfo/mailman-usersThe 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Dennis Putnam wrote: However, I am now getting permission denied errors on the database folders. IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.2271.2' I ran check_perms and all is OK. This has always been about ownership/permissions but I question why check_perms doesn't/won't fix it. What is it supposed to be? Prior to 2.1.10, check_perms had a bug and didn't check the owner and group permissions on the archives/private directory itself. Permissions should be 2771 or maybe 2770 (drwxrws--x or drwxrws---). If archives/private is not o+x, it needs to be owned by the web server for public archive URLs to work. Subordinate directories should be 2775 (drwxrwsr-x) and subordinate files 0664 (-rw-rw-r--) except for the archives/private/*/database/ directory and subordinate files which should not have 'other' permissions. FWIW, the owner:group for /usr/lib/mailman and /var/lib/mailman trees is mailman:mail. I should also note that the command (it was just a help command to req) did work but I did not want to try actually mailing something to a list until this is all fixed. It is not clear to my why a help command to the -request address would try to lock the archive. Is (was) 2271 the pid of CommandRunner? -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Mark Sapiro wrote: Dennis Putnam wrote: Mark Sapiro wrote: Can you go successfully go to a http://www.example.com/mailman/listinfo/listname page for a known listname even though it doesn't appear on the overview. If not, I think your web server is pointing at the wrong place. OK, now we are making progress. Thanks. I can indeed see the list if I supply the list name in the link like you suggested. I guess that means the scriptalias is correct so the question now becomes, why do they not show up on the admin or listinfo links? Does this also mean if I start mailman it will work in spite of the incorrect web interface? Yes, Mailman will probably work if you start it as long as aliases or whatever is required for mail delivery to the list are in place. As far as lists missing from the listinfo overview, we are back to the FAQ at http://wiki.list.org/x/lYA9. Assuming the lists are public (Privacy options... - advertised = Yes), the list doesn't appear on the overview because VIRTUAL_HOST_OVERVIEW = On (the default), and the host portion of the list's web_page_url attribute does not exactly match the host portion of the URL used to access the page. Perhaps you had VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py on the old server and didn't carry it over. Or, perhaps you changed it in Defaults.py on the old server; if so, this is why you shouldn't do that. I'm making some progress as the problems so far seem to be ownerhip and permissions since the copy had to be done as root. I could not find anything that tells me what the group and owner should be for each associated directory but I think I have them all set to mailman:mail. Now I am getting this error from postfix: status=bounced (Command died with status 2: /usr/lib/mailman/mail/mailman post mailman. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group mail, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group mail, or re-run configure, providing the command line option `--with-mail-gid=mailman'. ) Oct 20 19:25:15 dap002 postfix/qmgr[27883]: 9D0D819835: removed Oct 20 19:25:20 dap002 postfix/smtp[28602]: 202FF19836: to=[EMAIL PROTECTED], relay=mail.bellsouth.net[207.115.11.17]:25, delay=6.8, delays=0.01/0.01/3.2/3.6, dsn=2.0.0, status=sent (250 ok ; id=20081020232532H05001u3qhe) Oct 20 19:25:20 dap002 postfix/qmgr[27883]: 202FF19836: removed I don't think I understand what to do at this point. Everything other then what I copied was set per the Mandriva installer. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Dennis Putnam wrote: I'm making some progress as the problems so far seem to be ownerhip and permissions since the copy had to be done as root. I could not find anything that tells me what the group and owner should be for each associated directory but I think I have them all set to mailman:mail. bin/check_perms will help. I don't think mailman:mail is correct. The user is not important, but the group should be Mailman's group (the setting for MAILMAN_GROUP in Defaults.py. Run bin/check_perms -f as root. That should make group and mode correct. Now I am getting this error from postfix: status=bounced (Command died with status 2: /usr/lib/mailman/mail/mailman post mailman. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group mail, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group mail, or re-run configure, providing the command line option `--with-mail-gid=mailman'. ) See the FAQ at http://wiki.list.org/x/tYA9. I don't think I understand what to do at this point. Everything other then what I copied was set per the Mandriva installer. Where are your aliases? The mail wrapper is compiled to to expect to be invoked by the 'mail' group. Postfix will invoke the wrapper as the user and that user's primary group corresponding to the owner of the aliases.db file in which the pipe command was found. I.e., if the aliases.db file is userx:groupy, postfix will invoke the wrapper as userx:groupx where groupx is userx's primary group. -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Mark Sapiro wrote: Dennis Putnam wrote: I am installing a replacement server and am having trouble migrating Mailman. The installation works but none of my lists show up when I use the browser interface. However, when I run 'list_lists' from the command line they are there. Is this a config issue with just the HTML interface or is there something else fundamentally wrong? See the FAQ at http://wiki.list.org/x/lYA9. Thanks for the reply but I've already been there. That does not seem to be my problem. All the config files were copied from the working server as is (the mm_cfg.py file is correct). The new server has exactly the same hostname and IP address. The only (intentional) difference, other then the hardware, is the underlying OS (Mandriva Free 2007 Spring replacing Mandriva 2007). I suppose it is possible that this version of Mandriva put the Mailman files someplace different then the previous version (why it doesn't follow the standard is beyond me) but so far I have not found any other location with config files. I think Mailman needs a command that lists all the file paths it is using. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Dennis Putnam wrote: Mark Sapiro wrote: Dennis Putnam wrote: I am installing a replacement server and am having trouble migrating Mailman. The installation works but none of my lists show up when I use the browser interface. However, when I run 'list_lists' from the command line they are there. Is this a config issue with just the HTML interface or is there something else fundamentally wrong? See the FAQ at http://wiki.list.org/x/lYA9. Thanks for the reply but I've already been there. That does not seem to be my problem. All the config files were copied from the working server as is (the mm_cfg.py file is correct). The new server has exactly the same hostname and IP address. The only (intentional) difference, other then the hardware, is the underlying OS (Mandriva Free 2007 Spring replacing Mandriva 2007). I suppose it is possible that this version of Mandriva put the Mailman files someplace different then the previous version (why it doesn't follow the standard is beyond me) but so far I have not found any other location with config files. I think Mailman needs a command that lists all the file paths it is using. grep PREFIX Mailman/Defaults.py You said bin/list_lists shows the lists, so presumably they are where they should be unless the web server is pointing at CGI wrappers from a different installation. Have you checked where the scriptalias in the web server points? Can you go successfully go to a http://www.example.com/mailman/listinfo/listname page for a known listname even though it doesn't appear on the overview. If not, I think your web server is pointing at the wrong place. -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Dennis Putnam wrote: Mark Sapiro wrote: Can you go successfully go to a http://www.example.com/mailman/listinfo/listname page for a known listname even though it doesn't appear on the overview. If not, I think your web server is pointing at the wrong place. OK, now we are making progress. Thanks. I can indeed see the list if I supply the list name in the link like you suggested. I guess that means the scriptalias is correct so the question now becomes, why do they not show up on the admin or listinfo links? Does this also mean if I start mailman it will work in spite of the incorrect web interface? Yes, Mailman will probably work if you start it as long as aliases or whatever is required for mail delivery to the list are in place. As far as lists missing from the listinfo overview, we are back to the FAQ at http://wiki.list.org/x/lYA9. Assuming the lists are public (Privacy options... - advertised = Yes), the list doesn't appear on the overview because VIRTUAL_HOST_OVERVIEW = On (the default), and the host portion of the list's web_page_url attribute does not exactly match the host portion of the URL used to access the page. Perhaps you had VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py on the old server and didn't carry it over. Or, perhaps you changed it in Defaults.py on the old server; if so, this is why you shouldn't do that. -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Problem Migrating Mailman to New Server
I am installing a replacement server and am having trouble migrating Mailman. The installation works but none of my lists show up when I use the browser interface. However, when I run 'list_lists' from the command line they are there. Is this a config issue with just the HTML interface or is there something else fundamentally wrong? I thought I just needed to do a simple copy of the /var/lib/mailman directory to the new server but perhaps there is more to it then that. TIA. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Dennis Putnam wrote: I am installing a replacement server and am having trouble migrating Mailman. The installation works but none of my lists show up when I use the browser interface. However, when I run 'list_lists' from the command line they are there. Is this a config issue with just the HTML interface or is there something else fundamentally wrong? See the FAQ at http://wiki.list.org/x/lYA9. -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
