[Mailman-Users] Thank you -- Help with migration
TIA, Please help me resolve what I hope is fairly simple permissions error. If need be, I can restore the VM to a state prior to the noted file transfers. Goal: Migrate from Mac OSX.4.11 to Ubuntu 9.04 (on VMware). Steps: Build Ubuntu server with Postfix, Amavisd, Spammassasin, Mailman. Rsync files over with the following commands. Did not use option a because mailman/list owner had different names numerical IDs. sudo rsync -rlptDvz /var/mailman/lists r...@209.xxx.xxx.xx:/var/lib/mailman/ data archive Results: Bug in Mailman version 2.1.12 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. Logs (also attached): sudo more /var/log/mailman/error Apr 26 13:36:10 2010 admin(1508): admin(1508): [- Mailman Version: 2.1.12 -] admin(1508): [- Traceback --] admin(1508): Traceback (most recent call last): admin(1508): File /var/lib/mailman/scripts/driver, line 112, in run_main admin(1508): main() admin(1508): File /var/lib/mailman/Mailman/Cgi/admin.py, line 65, in main admin(1508): admin_overview() admin(1508): File /var/lib/mailman/Mailman/Cgi/admin.py, line 232, in admin_overview admin(1508): mlist = MailList.MailList(name, lock=0) admin(1508): File /var/lib/mailman/Mailman/MailList.py, line 130, in __init__ admin(1508): self.Load() admin(1508): File /var/lib/mailman/Mailman/MailList.py, line 638, in Load admin(1508): dict, e = self.__load(file) admin(1508): File /var/lib/mailman/Mailman/MailList.py, line 604, in __load admin(1508): fp = open(dbfile) admin(1508): IOError: [Errno 13] Permission denied: '/var/lib/mailman/lists/21ctp/config.pck' admin(1508): [- Python Information -] admin(1508): sys.version = 2.6.4 (r264:75706, Dec 7 2009, 18:43:55) [GCC 4.4.1] admin(1508): sys.executable = /usr/bin/python admin(1508): sys.prefix = /usr admin(1508): sys.exec_prefix = /usr admin(1508): sys.path= /usr admin(1508): sys.platform= linux2 admin(1508): [- Environment Variables -] admin(1508):SERVER_SOFTWARE: Apache/2.2.12 (Ubuntu) admin(1508):SCRIPT_NAME: /cgi-bin/mailman/admin admin(1508):SERVER_SIGNATURE: addressApache/2.2.12 (Ubuntu) Server at 209.XXX.XXX.XXX Port 80/address admin(1508): admin(1508):REQUEST_METHOD: GET admin(1508):SERVER_PROTOCOL: HTTP/1.1 admin(1508):QUERY_STRING: admin(1508):HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SV1; SLCC1; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.5.30729; In foPath.2; OfficeLiveConnector.1.3; OfficeLivePatch.0.0; .NET CLR 3.0.30729) admin(1508):HTTP_CONNECTION: Keep-Alive admin(1508):SERVER_NAME: 209.XXX.XXX.XXX admin(1508):REMOTE_ADDR: 192.168.151.102 admin(1508):SERVER_PORT: 80 admin(1508):SERVER_ADDR: 209.XXX.XXX.XXX admin(1508):DOCUMENT_ROOT: /var/www admin(1508):PYTHONPATH: /var/lib/mailman admin(1508):SCRIPT_FILENAME: /usr/lib/cgi-bin/mailman/admin admin(1508):SERVER_ADMIN: webmas...@localhost admin(1508):HTTP_HOST: 209.XXX.XXX.XXX admin(1508):HTTP_UA_CPU: x86 admin(1508):REQUEST_URI: /cgi-bin/mailman/admin admin(1508):HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-ms-application, application/vnd.ms-xpsdocument, application/x aml+xml, application/x-ms-xbap, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* admin(1508):GATEWAY_INTERFACE: CGI/1.1 admin(1508):REMOTE_PORT: 49276 admin(1508):HTTP_ACCEPT_LANGUAGE: en-us admin(1508):HTTP_ACCEPT_ENCODING: gzip, deflate Apr 26 13:36:40 2010 admin(1509): admin(1509): [- Mailman Version: 2.1.12 -] | | | | c...@lists:~$ c...@lists:~$ c...@lists:~$ c...@lists:~$ ls -al /var/lib/mailman/lists/21ctp/ total 28 drwxrwxr-x 2 root list 4096 2010-04-26 13:31 . drwxrwsr-x 40 root list 4096 2010-04-13 11:02 .. -rw-rw 1 root root 5400 2010-04-26 13:31 config.pck -rw-rw 1 root root 4917 2010-04-26 12:00 config.pck.last -rw-rw-r-- 1 root root 24 2009-12-09 08:07 request.pck Thank you, Davis Lee WAN Administrator Albuquerque Public Schools 505 830 6870 -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Simple, yet over my head multiple domain problem
Greetings Geniuses... I have mailman 2.1.11 running with postfix, and it's absolutely great. I love it. The problem is...I'm going to be honest when I say I'm definitely below average intelligence with this sort of thing. I don't know how to make it so I can have more than one domain on my mailman install. I have all the domains pointing to the correct IP address, so the interface works on each domain. I can change the hostname in my main.cffile to whatever domain I want to work at that instant, and it works-but I don't know how I can have 5 domains that work at the same time. I can only get them to work one at a time. I understand that these files must be changed: main.cf mm_cfg.py (something involving virtual hosts) But I've looked everywhere on the internet and I can't find a step by step guide for (idiots) if you will on what I need to do to what file word for word. Basically, how can I make: domain1.info domain2.info domain3.info domain4.info domain5.info all work at the same time. I know this forum is for advanced issues in general, been on it for quite sometime. So I apologize for filling your inbox with such a silly question. I am so grateful for your assistance. Thank you, Tyler -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman vs OSX vs launchd
I know, I'm reopening a ten month old thread. But I think I have a good workaround. On Fri, 26 Jun 2009, Sebastian Hagedorn wrote: --On 26. Juni 2009 20:22:13 +0900 Matthias Schmidt b...@admilon.net wrote: Am/On Thu, 18 Jun 2009 19:22:02 -0500 schrieb/wrote Larry Stone: On 6/18/09 7:11 PM, Bryan Harrison at br...@bryanharrison.com wrote: I've built and installed Mailman 2.12 from current source code and have it running just fine under OS X Server 10.5.7, with on exception, which is not properly speaking a Mailman problem at all. If I start Mailman from the CLI, using /usr/share/mailman/bin/ mailmanctl -s start, all is well. If I allow launchd to start it ScaronI get an endless succession ofScaron Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master qrunner. Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]): Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 9 seconds The reason this happens is that launchd expects the processes it launches to stick around. They must not daemonize. But mailmanctl terminates after it has started the runners. I assume that Apple modified their own distribution of Mailman so that mailmanctl behaves differently. I'd suggest comparing the two. I've been playing around with Mailman on a 10.6 (Snow Leopard) machine. It's for testing right now (at the next refresh of Mac Minis or iMacs, I plan to buy one to replace my PPC iMac that is currently my everything server - for now I'm testing on my laptop, the only Intel Mac I currently have). So I found that unlike on the PPC iMac, where Mailman starts OK after about 75% of the boots, on the laptop, it consistently died. No stray process system.log message but perhaps that's a 10.5/10.6 difference. But I did see that the lock files were being created in $mailman_prefix/locks. So what's different? Well, the laptop is a lot faster. Factor? I think so. I know almost nothing about the internals of forking processes and daemonizing but if I have it right, when 'mailmanctl start' is run, it forks a second copy which daemonizes. Meanwhile, the first copy of mailmanctl exits. My guess is that the first copy was exiting and the process terminating before the second copy had performed whatever magic it does to deamonize and run on its own. My workaround, which appears to work so far, is to have launchd, rather than run mailmanctl directly (via a .plist in /Library/LaunchDaemons), instead run a script in root's home directory that runs mailmanctl, then sleeps for one second before exiting: #!/bin/sh /usr/local/mailman/bin/mailmanctl -s start sleep 1 -- Larry Stone lston...@stonejongleux.com -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Thank you -- Help with migration
Lee, Davis H wrote: admin(1508): IOError: [Errno 13] Permission denied: '/var/lib/mailman/lists/21ctp/config.pck' [...] c...@lists:~$ ls -al /var/lib/mailman/lists/21ctp/ total 28 drwxrwxr-x 2 root list 4096 2010-04-26 13:31 . drwxrwsr-x 40 root list 4096 2010-04-13 11:02 .. -rw-rw 1 root root 5400 2010-04-26 13:31 config.pck -rw-rw 1 root root 4917 2010-04-26 12:00 config.pck.last -rw-rw-r-- 1 root root 24 2009-12-09 08:07 request.pck The files in the lists/listname/ directory need to be Mailman's group - 'list' in your case. The lists/listname directories need to be SETGID - i.e. mode 2775, not 0775. sudo /usr/lib/mailman/bin/check_perms -f (if I have the path right) should fix all of this. -- Mark Sapiro m...@msapiro.netThe 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 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman vs OSX vs launchd
Larry Stone wrote: I know almost nothing about the internals of forking processes and daemonizing but if I have it right, when 'mailmanctl start' is run, it forks a second copy which daemonizes. Meanwhile, the first copy of mailmanctl exits. My guess is that the first copy was exiting and the process terminating before the second copy had performed whatever magic it does to deamonize and run on its own. It probably has nothing to do with this, but through Mailman 2.1.13, mailmanctl forks the eventual daemon with file descriptors for stdin, stdout and stderr, possibly attached to the terminal. Normally, the only symptom is if you start Mailman in a terminal session and then log out, the session doesn't completely close until you physically disconnect, but this may have an effect on your situation. I do have an Intel iMac amongst several other machines, but I know essentially nothing about launchd. Anyway, there is a patch to mailmanctl at http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1221 which probably won't make a difference to your case, but might. -- Mark Sapiro m...@msapiro.netThe 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 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Simple, yet over my head multiple domain problem
Ty Nelson wrote: I don't know how to make it so I can have more than one domain on my mailman install. I have all the domains pointing to the correct IP address, so the interface works on each domain. I can change the hostname in my main.cffile to whatever domain I want to work at that instant, and it works-but I don't know how I can have 5 domains that work at the same time. I can only get them to work one at a time. I understand that these files must be changed: main.cf mm_cfg.py (something involving virtual hosts) But I've looked everywhere on the internet and I can't find a step by step guide for (idiots) if you will on what I need to do to what file word for word. Basically, how can I make: domain1.info domain2.info domain3.info domain4.info domain5.info all work at the same time. I know this forum is for advanced issues in general, been on it for quite sometime. So I apologize for filling your inbox with such a silly question. This list is for any and all Mailman users. No apologies required. If I understand correctly, the easiest solution is to make all the domains local in Postfix. I.e. in main.cf, if for example you have myhostname = domain1.info you could put mydestination = $myhostname, localhost.$mydomain, localhost, domain2.info, domain3.info, domain4.info, domain5.info Then, assuming you have aliases for all the lists, this should work. In any case, you should also have in mm_cfg.py (assuming the web domain corresponding to the email domain domain1.info is www.domain.info) add_virtualhost(www.domain1.info, domain1.info) add_virtualhost(www.domain2.info, domain2.info) add_virtualhost(www.domain3.info, domain3.info) add_virtualhost(www.domain4.info, domain4.info) add_virtualhost(www.domain5.info, domain5.info) This is to facilitate creating lists in the proper domain from the web. If you want some of these domains to be virtual in Postfix, it's a bit more involved. If you let us know exactly what the requirement is, we can help with that too. -- Mark Sapiro m...@msapiro.netThe 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 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Simple, yet over my head multiple domain problem
Mark, That solved it! Not only are you really smart, you're nice too. That always makes my day better. Thanks for taking the time to answer the question. That was so easy and simple to do-but somehow when I get inside mailman I have this horrible fear of breaking it. (I've done that a few times). Thanks again! -Ty On Wed, Apr 28, 2010 at 8:39 AM, Mark Sapiro m...@msapiro.net wrote: Ty Nelson wrote: I don't know how to make it so I can have more than one domain on my mailman install. I have all the domains pointing to the correct IP address, so the interface works on each domain. I can change the hostname in my main.cffile to whatever domain I want to work at that instant, and it works-but I don't know how I can have 5 domains that work at the same time. I can only get them to work one at a time. I understand that these files must be changed: main.cf mm_cfg.py (something involving virtual hosts) But I've looked everywhere on the internet and I can't find a step by step guide for (idiots) if you will on what I need to do to what file word for word. Basically, how can I make: domain1.info domain2.info domain3.info domain4.info domain5.info all work at the same time. I know this forum is for advanced issues in general, been on it for quite sometime. So I apologize for filling your inbox with such a silly question. This list is for any and all Mailman users. No apologies required. If I understand correctly, the easiest solution is to make all the domains local in Postfix. I.e. in main.cf, if for example you have myhostname = domain1.info you could put mydestination = $myhostname, localhost.$mydomain, localhost, domain2.info, domain3.info, domain4.info, domain5.info Then, assuming you have aliases for all the lists, this should work. In any case, you should also have in mm_cfg.py (assuming the web domain corresponding to the email domain domain1.info is www.domain.info) add_virtualhost(www.domain1.info, domain1.info) add_virtualhost(www.domain2.info, domain2.info) add_virtualhost(www.domain3.info, domain3.info) add_virtualhost(www.domain4.info, domain4.info) add_virtualhost(www.domain5.info, domain5.info) This is to facilitate creating lists in the proper domain from the web. If you want some of these domains to be virtual in Postfix, it's a bit more involved. If you let us know exactly what the requirement is, we can help with that too. -- Mark Sapiro m...@msapiro.netThe 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 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Snow Leoparrd (MacOS X 10.6) CLIENT installation steps for Mailman
In September 2004, I posted on this topic with instructions for installing mailman on the client version of MacOS X 10.3 (Panther). Later, I updated it for OS X 10.4 (Tiger) as well as notes (but not full instructions) for OS X 10.5 (Leopard). Just recently, I did a test installation on my 10.6 (Snow Leopard) laptop in anticipation of a new desktop to become my new server later this year. In all cases, these were the CLIENT version of Mac OS X (Mac OS X Server comes with a bastardized version of Mailman). So here, once again for purposes of getting it in the archives, are my instructions for installing mailman on MacOS X 10.6.x. With this version, I've made some changes to bring the mailman home directory in line with Mailman standards (i.e. using /usr/local/mailman instead of /Applications/mailman), improved the system startup procedure, and some other miscellaneous cleanup. = Snow Leopard (MacOS X 10.6) installation steps for Mailman This document is based on my experience installing Mailman 2.1.4 on MacOS X 10.3 (Panther) and subsequently upgrading to Tiger (Mac OS X 10.4) and to mailman 2.1.6 and now to Snow Leopard (Mac OS X 10.6) with mailman 2.1.13. It is largely based on Kathleen Webb's document on installing Mailman and Sendmail on MacOS X 10.2 (Jaguar) (http://mail.python.org/pipermail/mailman-users/2002-October/022944.html) which contains some information on tools that can be useful that will not be repeated here. This guide assumes that you have Postfix (which comes with Snow Leopard) already configured and operating, that you have the built-in web server running (if not, enable it by going to the Sharing pane of System Preferences and turning on Web Sharing), and that you are familiar with the Unix shell and basic text editing from the shell (vi or emacs). It is intended to help you get Mailman installed. It does not deal with actually using Mailman as there are plenty of other sources of help for that. This is based on a new install on a Snow Leopard system that has never had Mailman on it before. Questions are best asked through the mailman-users mailing list. Step 1) Collect all the things you need. a) You need to download and decompress the Mailman software. (The installation instructions are in step 3.) Download the software from: http://www.list.org/ Download the latest 2.1.x.tgz which is a gzip compressed tar file (.tgz). Just leave it for now and we'll expand it later. b) You need to be an administrator of your computer. If you do not have administrator privileges, you will not be able to do this. c) Python comes pre-installed on your computer. It is already functioning and ready for use by Mailman. (To verify you have Python, open the Terminal application. at the % prompt, type: sudo Python -V and then hit the enter/return key. You'll be prompted for your password. When you enter it, the terminal will respond with the Python version. d) Apache web server software comes pre-installed on your computer and has already been configured and is running. e) Postfix is already installed on your computer but is not running by default. You will need to get Postfix configured and started but how to do that is beyond the scope of this document. An excellent way of getting Postfix up and running, along with a POP and IMAP server, is with MailServe Snow http://www.cutedgesystems.com/software/MailServeSnow/. Note that MailServe Snow is not free - as all the underlying software is freely available, you're paying for the configuration and installation tool, not the underlying software. f) You may need to know how to get into hidden subdirectories. In the Finder, use the Go menu and choose Go to Folder. Type in the path to the hidden folder you need to open. g) You may need to know how to make a new user. You use the System Preferences application [from the Apple menu]. Use the Accounts panel in the System section. h) You need to install the Developer Tools that came with your Snow Leopard disks or several of the steps won't work. From this point on, we will do everything in Terminal and as root. So open Terminal and then become root by typing 'sudo su'. You will be prompted for your password and then get a # as a prompt. Step 2) Verify the user and group needed to run Mailman. All versions of OS X since at least Panther have come with the needed users and groups already created. We will be using _mailman for mailman and _www for the webserver. To verify they're there, type 'grep _mailman /etc/group' and 'grep _mailman /etc/passwd. Both should return one line starting with _mailman:*:78:. If they do, they exist. You can repeat that with _www and the number you see should be 70. Assuming all of the above is there, we're good to go. Step 3) Create a folder for mailman in the finder. a) You can choose where to create the folder. I chose to
