[Mailman-Users] Recovering from Server Fail, was FW: Make Install Fails
I've continued to fiddle with this and now have different errors, so I thought I would back up and give ya'll the big picture in case I'm approaching this from the wrong direction. Tuesday morning I had a hardware failure on my old Solaris 10 box. In 25 years in the business, I don't think I've seen a hardware failure as thorough as this that didn't involve smoke. The machine is utterly unrecoverable. So to get back into service, I decided to move the service to a different box. It's also a Solaris box, but is a Sun X4100. I have restored the directory tree from tape, but presume that the executables can't be run on the new platform. What is the quickest way to get mailman back in service? Bill McNutt -Original Message- From: mailman-users-bounces+mcnutt=utk@python.org [mailto:mailman-users-bounces+mcnutt=utk@python.org] On Behalf Of McNutt Jr, William R Sent: Wednesday, January 19, 2011 10:44 PM To: mailman-users@python.org Subject: [Mailman-Users] Make Install Fails I'm attempting to install Mailman on a Solaris 10 box and I am unable to get past make install. Sorry - not a unix guy, please use small words and explicit direction. Attached is the results of make install: Creating architecture independent directories... chmod o-r /usr/local/mailman/archives/private Creating architecture dependent directories... for f in mmsitepass newlist rmlist add_members list_members remove_members clone_member update arch sync_members check_db withlist check_perms find_member version config_list list_lists dumpdb cleanarch list_admins genaliases change_pw mailmanctl qrunner inject unshunt fix_url.py convert.py transcheck b4b5-archfix list_owners msgfmt.py show_qfiles discard rb-archfix reset_pw.py; \ do \ .././install-sh -c -m 755 ../build/bin/$f /usr/local/mailman/bin; \ done for f in crontab.in; \ do \ .././install-sh -c -m 644 $f /usr/local/mailman/cron; \ done for f in checkdbs mailpasswds senddigests gate_news nightly_gzip bumpdigests disabled; \ do \ .././install-sh -c -m 755 ../build/cron/$f /usr/local/mailman/cron; \ done for i in ./*.jpg ./*.png; \ do \ .././install-sh -c -m 644 $i /usr/local/mailman/icons; \ done for d in bin cron scripts tests; \ do \ dir=/usr/local/mailman/$d; \ .././install-sh -c -m 644 paths.py $dir; \ done .././install-sh -c -m 755 mailman /usr/local/mailman/scripts .././install-sh -c -m 644 sitelist.cfg /usr/local/mailman/data for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \ do \ gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /usr/local/lib/python2.6/distutils/dist.py:250: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant error: command 'gcc' failed with exit status 1 *** Error code 1 make: Fatal error: Command failed for target `install-packages' Current working directory /export/home/local/mailman/mailman-2.1.9/misc *** Error code 1 The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall' -- 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/mcnutt%40utk.edu -- 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] Question about reg expr matches in matches_p (in Moderate.py)
On 1/19/2011 3:35 PM, C Nulk wrote: So the question is, should the listnames in the *_these_nonmembers fields be all lowercase, all uppercase, or mixed case? So far, mixed case does not appear to be working. The list name in @listname entries in *_these_nonmembers must be the internal name of the list, i.e. it is all lower case, and in distros such as cPanel that have munged listnames, it must be the name that's used in the web interface which may be different from the name in the posting address. Again, in cPanel for example, this is the listname_domain name, not simply listname. These are the only case sensitive entries in *_these_nonmembers. regexps and literal addresses are matched case insensitively. -- 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] Recovering from Server Fail, was FW: Make Install Fails
Here's some more information: At step 3.1 of the installation instructions, the ./configure step appears to run to completion, but then ends with a warning: can't change build. I don't get this when I run as root, but the instructions pretty clearly say that I should not be root when I run it. Is this the core of my problem? -Original Message- From: mailman-users-bounces+mcnutt=utk@python.org [mailto:mailman-users-bounces+mcnutt=utk@python.org] On Behalf Of Mark Sapiro Sent: Thursday, January 20, 2011 2:03 PM To: C Nulk Cc: MailMan Subject: Re: [Mailman-Users] Question about reg expr matches in matches_p (in Moderate.py) On 1/19/2011 3:35 PM, C Nulk wrote: So the question is, should the listnames in the *_these_nonmembers fields be all lowercase, all uppercase, or mixed case? So far, mixed case does not appear to be working. The list name in @listname entries in *_these_nonmembers must be the internal name of the list, i.e. it is all lower case, and in distros such as cPanel that have munged listnames, it must be the name that's used in the web interface which may be different from the name in the posting address. Again, in cPanel for example, this is the listname_domain name, not simply listname. These are the only case sensitive entries in *_these_nonmembers. regexps and literal addresses are matched case insensitively. -- 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/mcnutt%40utk.edu -- 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] Attachment size limit (or max_message_size)
Scott Race wrote: Ah, I see what's going on. So for the particular lists were working on, all messages to the list are held for moderation. So, it seems clicking Accept will accept the message, even if the message size is too big. Yes, and further, if the messages are held because the poster is moderated, this hold is applied before any of the miscellaneous holds, so all you know is it is a post from a moderated member, and if you approve it, it is approved even if too big. We recently (4 months ago) upgraded from Debian 4 to RHEL5. On the previous box, I believe we were running Mailman 2.1.12 (not sure), messages over the max_message_size limit would not hit the list and bounce back to the user with that message. Without source modifications, the message would still be held, not rejected, but the user would be notified if respond_to_post_requests is Yes. The company I'm working with is hoping the system can kick back messages over the max_message_size before it hits moderation. Is that possible? Would adding GLOBAL_PIPELINE directives to mm_cfg.py get that done? Yes, you could reorder the pipeline to put Hold ahead of Moderate, but the downside of this is a non-member post could be held for one of the miscellaneous hold reasons and the moderator may not realize it's a non-member post. -- 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] Recovering from Server Fail, was FW: Make Install Fails
Is this a fatal error for the ./configure step? checking for --with-mailhost... no checking for --with-urlhost... no Traceback (most recent call last): File conftest.py, line 2, in module from socket import * File /usr/local/lib/python2.6/socket.py, line 46, in module import _socket ImportError: ld.so.1: python: fatal: relocation error: file /usr/local/lib/python2.6/lib-dynload/_socket.so: symbol inet_aton: referenced symbol not found checking for default mail host name... Can't open conftest.out checking for default URL host component... Can't open conftest.out checking for strerror... (cached) yes -Original Message- From: mailman-users-bounces+mcnutt=utk@python.org [mailto:mailman-users-bounces+mcnutt=utk@python.org] On Behalf Of McNutt Jr, William R Sent: Thursday, January 20, 2011 2:18 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] Recovering from Server Fail, was FW: Make Install Fails Here's some more information: At step 3.1 of the installation instructions, the ./configure step appears to run to completion, but then ends with a warning: can't change build. I don't get this when I run as root, but the instructions pretty clearly say that I should not be root when I run it. Is this the core of my problem? -Original Message- From: mailman-users-bounces+mcnutt=utk@python.org [mailto:mailman-users-bounces+mcnutt=utk@python.org] On Behalf Of Mark Sapiro Sent: Thursday, January 20, 2011 2:03 PM To: C Nulk Cc: MailMan Subject: Re: [Mailman-Users] Question about reg expr matches in matches_p (in Moderate.py) On 1/19/2011 3:35 PM, C Nulk wrote: So the question is, should the listnames in the *_these_nonmembers fields be all lowercase, all uppercase, or mixed case? So far, mixed case does not appear to be working. The list name in @listname entries in *_these_nonmembers must be the internal name of the list, i.e. it is all lower case, and in distros such as cPanel that have munged listnames, it must be the name that's used in the web interface which may be different from the name in the posting address. Again, in cPanel for example, this is the listname_domain name, not simply listname. These are the only case sensitive entries in *_these_nonmembers. regexps and literal addresses are matched case insensitively. -- 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/mcnutt%40utk.edu -- 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/mcnutt%40utk.edu -- 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] Rr: Recovering from Server Fail
If I continue to make install I get the following error: .././install-sh -c -m 755 mailman /usr/local/mailman/scripts .././install-sh -c -m 644 sitelist.cfg /usr/local/mailman/data for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \ do \ gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /usr/local/lib/python2.6/distutils/dist.py:250: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant error: command 'gcc' failed with exit status 1 *** Error code 1 make: Fatal error: Command failed for target `install-packages' Current working directory /export/home/local/mailman-2.1.9/misc *** Error code 1 The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall' -- 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] Rr: Recovering from Server Fail
McNutt Jr, William R wrote: If I continue to make install I get the following error: .././install-sh -c -m 755 mailman /usr/local/mailman/scripts .././install-sh -c -m 644 sitelist.cfg /usr/local/mailman/data for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \ do \ gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /usr/local/lib/python2.6/distutils/dist.py:250: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant error: command 'gcc' failed with exit status 1 *** Error code 1 make: Fatal error: Command failed for target `install-packages' Current working directory /export/home/local/mailman-2.1.9/misc *** Error code 1 The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall' There's a lot of stuff in the archives of this list about various solaris installation issues. Try googling site:mail.python.org inurl:mailman solaris 10 codecs syntax. -- 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] Advice on new install of Mailman to CentOS 5
Richard Damon wrote: The question comes in that the CentOS 5 distribution only has a RPM for Mailman 2.1.9, instead of the recently released 2.1.14, so the question comes do I use the RPM from the distribution and run a version several years old, or is it better to install from a direct download. Quoting from the FAQ at http://wiki.list.org/x/tIA9 It is possible to trick Plesk into recognizing newer versions installed manually but it's not for the faint of heart. I am working of a fresh install so I don't need to worry about migrating existing list on the server, but I definitely want to be able to import the existing lists from the old server. (And will probably do at least one dry run of the migration to a different domain name just to make sure I know how to do this and that things work before moving the live site). The actual migration of list data from the old to the new installation should be straightforward as long as the new installation is the same or a newer version. See the initial section of the FAQ at http://wiki.list.org/x/2oA9, and note that you may need to run fix_url to update list domains and this should be done prior to regenerating archives. -- 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] control mail distribution ..
by the way, I keep deleting the following: /var/spool/mailman/bounces/*.pck /var/lib/mailman/data/*.pck because they fill up all the space on my small hard drives on my VPS servers.. is that why mailman's bounce processor removes the subscribers or because they does actually bounce until they reach the points limit? Thanks.. -Original Message- From: Mark Sapiro Sent: Tuesday, January 18, 2011 4:18 AM To: Khalil Abbas Cc: mailman-users@python.org Subject: Re: [Mailman-Users] control mail distribution .. On 1/17/2011 3:00 PM, Khalil Abbas wrote: is there way to tell mailman to send certain number of messages per hour? The short answer is No, but see the FAQ at http://wiki.list.org/x/j4A9 for other possible solutions. -- 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] Friendly email address
Hi, I'd like to use Mailman for a distribution list and would prefer that the from address be of the form Foo Bar foo...@list.org ... rather than just foo...@list.org. Is this possible? How do I need to input this in the configuration? Thanks -- 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] control mail distribution ..
Khalil Abbas wrote: by the way, I keep deleting the following: /var/spool/mailman/bounces/*.pck It looks like BounceRunner has died and is not processing the bounce queue. Chack Mailman's qrunner and error logs for more information. /var/lib/mailman/data/*.pck Are these heldmsg-listname-*.pck files or bounce-events-*.pck files. If they are held messages, they should be removed with bin/discard or through the moderator interface, and setting the list's max_days_to_hold may help. If they are bounce-events-*.pck files, most of them are probably stale because of dying BounceRunners. Assuming you are not slicing queues, i.e., you have only one qrunner per queue, there should never be more than two of these, one with the PID of the current OutgoingRunner and one with the PID of the current BounceRunner. All the others are dead files left behind when a runner died or was killed. -- 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] Friendly email address
I'm continuing to try various combinations but without any luck. Don't see this documented either. Any ideas or confirmation that this is not possible would really help. Thanks! On Thu, Jan 20, 2011 at 11:23 AM, Stefan Alder twigbra...@gmail.com wrote: Hi, I'd like to use Mailman for a distribution list and would prefer that the from address be of the form Foo Bar foo...@list.org ... rather than just foo...@list.org. Is this possible? How do I need to input this in the configuration? Thanks -- 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] Friendly email address
Stefan Alder wrote: I'm continuing to try various combinations but without any luck. Don't see this documented either. Any ideas or confirmation that this is not possible would really help. Thanks! On Thu, Jan 20, 2011 at 11:23 AM, Stefan Alder twigbra...@gmail.com wrote: Hi, I'd like to use Mailman for a distribution list and would prefer that the from address be of the form Foo Bar foo...@list.org ... rather than just foo...@list.org. Is this possible? How do I need to input this in the configuration? If your Mailman is recent enough and if your list is anonymous_list = Yes the From: will be Foo Bar foo...@list.org where Foo Bar is the list's description. Recent enough is 2.1.6 or later. -- 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] Attachment size limit (or max_message_size)
Scott Race wrote: A few final questions to figure this out: 1. Has this always been the design? The client seems to think that on his old server the message would get kicked back before hitting the moderation queue. If so that's cool, just want to make sure I'm not missing something. I don't know what code modifications might have been in place in the old server, but it has always worked this way in Mailman 2.1.x as distributed by the GNU Mailman project. 2. To make sure I understand - if we were to use GLOBAL_PIPELINE directives in mm_cfg.py to re-order, would that mean that email addresses not signed up and confirmed as members would be able to send to the list and have it go into the modertor's queue? Yes, but only if the post were subject to any of the miscellaneous holds processed by Mailman/Handlers/Hold.py. 3. With a list of thousands of users, a 6MB attachment would kill our bandwidth if it went out. If we must moderate, is there any other solution other than the moderator looking at each email and deciding to kick it back due to size? Postfix limiting (ungraceful, I know)? I would recommend a custom handler (see the FAQ at http://wiki.list.org/x/l4A9) to be inserted in the pipeline ahead of Moderate whose job would be only to reject posts that are too big. Alternatively, you could put Hold first, but modify it to reject instead of hold. -- 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
