Mailman 3 April 2010 - Mailman-Users

Re: [Mailman-Users] Block reply to all
by Schwartz, Robert - IS May 1, 2010

May 1, 2010

Grant suggested: To directly answer your question (and for the benefit of others searching the archives) I think the best that you will be able to do is to filter messages based on the existence of the standard reply headers ("References:" and "In-Reply-To:") and reject the message(s). Does anyone know how to do this: Where would you setup this filter? I can't find it in the General Options or Content Filtering. Robert ________________________________ This e-mail and any files transmitted with it may be proprietary and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of ITT Corporation. The recipient should check this e-mail and any attachments for the presence of viruses. ITT accepts no liability for any damage caused by any virus transmitted by this e-mail.

2 1

Re: [Mailman-Users] List all users on one page
by Schwartz, Robert - IS May 1, 2010

May 1, 2010

This is the same question I have. I don't know how to use to script in Windows XP. I only use to web to get to my mail. Nothing is saved on my system. Re: [Mailman-Users] List all users on one page Mark Sapiro Wed, 21 Apr 2010 20:10:41 -0700 Brian Luria > >Where is the best place for me to start understanding terminal commands like >you list there. I am honestly not even sure where to start. I am only used >to the web based interface. The FAQ at <http://wiki.list.org/x/z4A9> lists the commands and what they do. Each command has a --help option that gives the usage and options for the command. The two most useful commands for manipulating non GUI things or things for all lists at once are bin/withlist and bin/config_list. Withlist can run Python scripts against one or all lists and can invoke an interactive Python interpreter with a list instance that can be examined and changed interactively, but this requires both Python knowledge and some knowledge of Mailman internals. bin/config_list is more "friendly". For example, in this case you would just create a file containing the single line admin_member_chunksize = 100 or whatever number you need, and run bin/config_list --inputfile /path/to/above/file listname ________________________________ This e-mail and any files transmitted with it may be proprietary and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of ITT Corporation. The recipient should check this e-mail and any attachments for the presence of viruses. ITT accepts no liability for any damage caused by any virus transmitted by this e-mail.

3 2

cgi in URLs
by Lee, Davis H April 30, 2010

April 30, 2010

IIUC, In migrating from OS X to Ubuntu, my old URLs, listed on all the links on all the pages brought over, had addresses without /cgi-bin/, like this: http://lists.aps.edu/mailman/admin The new install expects the /cgi-bin/, like this: http://lists.aps.edu/cgi-bin/mailman/admin What's the best way to fix this? Thank you, Davis Lee WAN Administrator Albuquerque Public Schools 505 830 6870

3 3

Re: [Mailman-Users] Block reply to all
by b19141＠anl.gov April 30, 2010

April 30, 2010

>You can do this under Privacy Options -> Recipient Filters >Set "Ceiling on acceptable number of recipients for a posting." to 1 > >Then anyone hitting reply-to-all will get a message saying that their >message is held because there are too many recipients, since any >reply-to-all will include both the sender address and the list address. But if someome sends mail to the list, and has an extra recipient in the "To:" or "Cc:", the mail will also be held. ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 240, Room 5.B.8 Internet: BSFinkel(a)anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994

1 0

Snow Leoparrd (MacOS X 10.6) CLIENT installation steps for Mailman
by Larry Stone April 30, 2010

April 30, 2010

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 follow the Mailman "standard" and put it in /usr/local. These instructions assume that is where you create the new folder. To create the folder, type: mkdir -p /usr/local/mailman Then "change directory" to it: cd /usr/local/mailman b) Copy the downloaded compressed tar file (e.g. mailman-2.1.13.tgz) to the directory we just created and then uncompress and untar it. The command below assumes that compressed tar file was downloaded into your Downloads folder. cp ~/Downloads/mailman-2.1.13.tgz . (yes, that's a space and a dot on the end of the command) tar xvzf mailman-2.1.13.tgz c) Set the proper ownership and permissions on the mailman directory: chown _mailman:_mailman /usr/local/mailman chmod a+rw,g+ws /usr/local/mailman d) Change directory in to the Mailman source directory. Assuming the you are using the mailman-2.1.13 version, type: cd /usr/local/mailman/mailman-2.1.13 e) Build Mailman: ./configure --prefix=/usr/local/mailman --with-cgi-gid=_www --with-mail-gid=_mailman f) A whole bunch of lines of code will scroll through the Terminal window. When it finishes, in the Terminal window, type: make install cd /usr/local/mailman sudo bin/check_perms -f sudo bin/check_perms -f (Repeat the check_perms until no errors are reported. If you end up with problems later, this whole step is probably where the problem will come from. Permissions are important to Mailman.) g) Set the Mailman site password: /usr/local/mailman/bin/mmsitepass xxxx [Replace xxxx with the password you want to use as the master password to the mailman application.] ======================================== Step 4) Set up your web server to serve the Mailman web pages for subscribing and administrating the mailing list. a) Change directory to the apache2 configuration directory (Apache2 is the webserver): cd /etc/apache2/ b) Edit httpd.conf with your favorite Terminal text editor such as vi or emacs). For instance, for vi, type: vi httpd.conf Add these lines to the file: ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/ Alias /pipermail/ /usr/local/mailman/archives/public/ <Directory "/usr/local/mailman/archives/public"> Options FollowSymLinks </Directory> c) Save the file and exit the editor. d) Copy the images used for the mailman web pages to where Apache expects them. In Terminal: cp /usr/local/mailman/icons/* /usr/share/httpd/icons e) Next we need to add the cron jobs that mailman needs to any existing root cron jobs. If there are no existing root cron jobs, you can just do: crontab /usr/local/mailman/cron/crontab.in However, if there are existing root cron jobs, then we need to append to it. One way way to do that is: crontab l | cat - /usr/local/mailman/crontab.in | crontab (note that this outputs the existing cron jobs, concatenated the mailman jobs to it, and the saves it as a new crontab. Make sure you have the command right or you risk losing your old jobs. You might want to backup the old jobs first with 'crontab -l > crontab.backup'). You can then edit the crontab with 'crontab -e'. You may want to comment out the gate news to mail job if you aren't doing that. ======================================== Step 5) Configure Postfix to support a separate Mailman alias file. a) Edit your Postix configuration file (possibly /etc/postfix/main.cf or if you used MailServe Snow as I mentioned above, then it's /usr/local/cutedge/postfix/etc/main.cf - you can also do this through the MailServe Snow application and add this as a custom Postfix setting) and add: alias_maps=hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases b) Reload postfix with: postfix reload ======================================== Step 6) Configure Mailman a) We need to let Mailman know we're using Postfix. Using you favorite means of text editing, open /usr/local/mailman/Mailman/mm_cfg.py and add below the line that says "# Put YOUR site-specific settings below this line.": MTA = "Postfix" ======================================== Step 7) Create your site-wide mailing list (mailman). Read the instructions in INSTALL in your mailman source directory (/Applications/Mailman/Mailman-2.1.13). In short, in the Terminal application, type: cd /usr/local/mailman bin/newlist mailman bin/config_list -i data/sitelist.cfg mailman ======================================== Step 8) Configure your system to start Mailman when it is booted. This has been a little tricky since Leopard came out so rather than have launchd start Mailman directly, we will have it run a script we put in root's home directory that does it a way I've found more reliable (by waiting one second after issuing the command to start mailman before it exits): a) In Terminal, change directory to /var/root/: cd /var/root b) Using your favorite text editor (vi, emacs, or whatever), create the file start_mailman.sh. For instance, with vi, type: vi mailman_start.sh And enter the lines: #!/bin/sh /usr/local/mailman/bin/mailmanctl -s start sleep 1 Save and exit. c) Change permissions to make it executable: chmod 755 start_mailman.sh d) Create the Mailman startup preference file: cd /Library/LaunchDaemons touch mailman.plist c) Using your favorite method of text editing, add the following content to mailman.plist: <?xml version="1.0" encoding="UTF-8"?> <plist version="1.0"> <dict> <key>Disabled</key> <false/> <key>Label</key> <string>mailman</string> <key>OnDemand</key> <true/> <key>ProgramArguments</key> <array> <string>/var/root/start_mailman.sh</string> </array> <key>ServiceIPC</key> <false/> <key>RunAtLoad</key> <true/> </dict> </plist> d) Verify the file ownership and permissions: ls -l You should see one of the lines saying something like: -rw-r--r-- 5 root wheel 170 12 May 11:21 mailman.plist e) If the permissions (rw-r--r--) are not correct, type: chmod 644 mailman.plist f) If the owner (root) or group (wheel) is not correct, type: chown root:wheel mailman.plist g) Go into launchctl and enable Mailman. This should also cause it to start immediately. launchctl load -w mailman.plist (the -w is very important. The Disabled attribute in the .plist is no longer used. Instead, Disabled status for all launchd plists is stored in /var/db/laubchd.db/com.apple.launchd/overrides.plist and is set/unset by the -w on the launchctl load/unload commands. Yes, it does seems needlessly complicated). Mailman should have started. To verify, open Terminal and type: ps -efw | grep python You should see a bunch of lines like this: 78 1099 1 0 0:00.01 ?? 0:00.01 /usr/bin/python /usr/local/mailman/bin/mailmanctl -s start 78 1101 1099 0 0:08.38 ?? 0:18.67 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s 78 1102 1099 0 0:07.29 ?? 0:17.57 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s 78 1103 1099 0 0:08.46 ?? 0:18.83 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s 78 1104 1099 0 0:08.14 ?? 0:18.16 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s 78 1105 1099 0 0:07.92 ?? 0:17.73 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s 78 1107 1099 0 0:07.72 ?? 0:18.54 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s 78 1108 1099 0 0:07.80 ?? 0:17.66 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s 78 1109 1099 0 0:00.07 ?? 0:00.19 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 -s 0 15583 15537 0 0:00.00 ttys000 0:00.00 grep pyth (The numbers will vary. The important thing is that you see the qrunner processes.) ======================================== Step 9) Enjoy! At this point, mailman should be ready to use. Read the documentation in your source directory for instructions on setting up your mailing lists. -- Larry Stone lstone19(a)stonejongleux.com http://www.stonejongleux.com/

3 2

Thank you -- Help with migration
by Lee, Davis H April 30, 2010

April 30, 2010

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 root@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: <address>Apache/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: webmaster@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 -----] | | | | core@lists:~$ core@lists:~$ core@lists:~$ core@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

2 3

Implement umbrella list on Mailman 2.1.9
by Esteban Torres Rodriguez April 30, 2010

April 30, 2010

Is it possible to implement umbrella lists Mailman 2.1.9? Do I need to run some patch? I have postfix-2.3.3, mailman 2.1.9, RHEL 5.3 bye.

2 3

How to view bounce mails
by Andy Smith April 29, 2010

April 29, 2010

Hi, On one of my lists a couple of subscribers have been receiving bounce mails. I can see the bounce mails arriving in the MTA logs, and Mailman does log this fact in the bounce log, but I'm wondering about the best way to debug this. I could of course leave the subscribers to work out why they're bouncing and eventually being unsubscribed, but I'd like to see the content of the bounces to see if there is any common problem. I can't see an option for Mailman to copy bounces to list or site admin, only the option for it to forward unrecognised bounces. These bounces are being recognised, but I'd still like to see their content. Is there a good way besides copying the list's bounces address to me? Cheers, Andy

2 1

Simple, yet over my head multiple domain problem
by Ty Nelson April 28, 2010

April 28, 2010

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

2 2

Virtual Domains for Mailing Lists in MailMan
by Gordon Smith April 28, 2010

April 28, 2010

Hello I found this E-Mail address on the MailMan homepage and decided to contact you as I don't seem to be able to locate the information I need elsewhere. To explain my circumstance. I am a visually impaired person, trying to get to grips with administrating a mail server under Apple Mac OS X 10.5.7 (Leopard) server. I need to host mailing lists under virtual domains hosted on our server but can't see quite how this is accomplished. Is there anywhere I can obtain this information as Apple's documentation on this subject seems poor from what I've seen. I really do apologise for any inconvenience I may cause you by contacting you - but if you could point me to the relevant information pages as to how to accomplish virtual domain list configuration under Apple's server platform I'd be very grateful. As a blind person this information is not always easy for me to locate. Thank you in advance for any help. Gordon

9 19