[Mailman-Users] How do I assign a default password when doing mass subscriptions
Hi, I'm setting up a mailman list for the folks over in the anthropology department and they have a list of around email addresses that they wish to initially subscribe. How do I assign a default password to each subscriber so they can get in via the web interface and change preferences, access private archives, etc? Thanks. Rob Tanner UNIX Services Manager Linfield College, McMinnville Oregon ITS will never ask you for your password. Please don’t share yours with anyone! -- 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] Neither the list admin or moderator getting notications on new susbriptions
On 3/23/11 6:54 PM, Mark Sapiro m...@msapiro.net wrote: On 3/23/2011 5:04 PM, Rob Tanner wrote: That I'm aware of. I subscribed myself via my personal email to avoid any confusion with me as a list admin. My request did not appear as a pending subscription request until after I clicked the link on the confirmation email. At that point an email notifying me of a pending request should have been sent to my list admin email address. No such message was sent, and that's the problem. Are other notices from Mailman being sent such as the list welcome message to a new subscriber? If not, perhaps VirginRunner is not running? Do you have enough access to the server to verify that and/or to see Mailman's logs? If you send an email to listname-owner@... does it get delivered to the admins? If not, does it bounce? I was able to access the mailman logs and the whole things turns out to have been an aliasing problem and not a mailman issue. Works perfect now. Thanks, Rob -- 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] Neither the list admin or moderator getting notications on new susbriptions
Hi, I forgot to mention, the option “Should the list moderators get immediate notice of new requests, as well as daily notices about collected ones?” is set to yes, so is there another switch as well or is something broken on my site? ~ Rob On 3/23/11 3:27 PM, Rob Tanner rtan...@linfield.edu wrote: Hi, I set up a list that requires confirm and approval for new subscriptions. There are two list admins (one email address per line and no comma between them) and neither admin gets notification or the subscription request. I also tried adding them as moderators as well to know avail. Is there some other switch that needs to be checked to enable notifications or is something broken on the site? I’m running v2.1.13 on RHEL 5. Thanks. Rob Tanner UNIX Services Manager Linfield College, McMinnville Oregon ITS will never ask you for your password. Please don’t share yours with anyone! -- 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] Neither the list admin or moderator getting notications on new susbriptions
Hi, I set up a list that requires confirm and approval for new subscriptions. There are two list admins (one email address per line and no comma between them) and neither admin gets notification or the subscription request. I also tried adding them as moderators as well to know avail. Is there some other switch that needs to be checked to enable notifications or is something broken on the site? I’m running v2.1.13 on RHEL 5. Thanks. Rob Tanner UNIX Services Manager Linfield College, McMinnville Oregon ITS will never ask you for your password. Please don’t share yours with anyone! -- 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] Neither the list admin or moderator getting notications on new susbriptions
On 3/23/11 4:51 PM, Mark Sapiro m...@msapiro.net wrote: On 3/23/2011 3:42 PM, Rob Tanner wrote: I forgot to mention, the option ³Should the list moderators get immediate notice of new requests, as well as daily notices about collected ones?² is set to yes, so is there another switch as well or is something broken on my site? On 3/23/11 3:27 PM, Rob Tanner rtan...@linfield.edu wrote: I set up a list that requires confirm and approval for new subscriptions. Since admin_immed_notify is Yes, the explanation is probably confirm and approval. With this subscribe policy, the subscription requires confirmation by the user before it is passed to the admins/moderators for approval. There will be nothing requiring moderator action until the user confirms via web or email. That I'm aware of. I subscribed myself via my personal email to avoid any confusion with me as a list admin. My request did not appear as a pending subscription request until after I clicked the link on the confirmation email. At that point an email notifying me of a pending request should have been sent to my list admin email address. No such message was sent, and that's the problem. ~ Rob -- 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] Waiting moderator requests not found
Hi, I just upgraded from version 2.1.9 to 2.1.13 to hopefully solve a couple of problems, and the upgrade solved all but one. The moderator of one of the lists gets email that tells him there are two requests pending, but when he clicks on the link to go to the administrative database the message is ³There are no requests pending². Since this issue was also in 2.1.9, I¹m assuming it¹s not a software bug but rather a configuration error of some kind, but I have no idea what that might be. Can anyone offer me ome useful advice? Thanks, Rob Rob Tanner UNIX Services Manager Linfield College, McMinnville Oregon -- 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] Getting python errors with bin/arch
Hi, I am trying to rebuild archives -- actually porting archives over from another machine and then doing a rebuild, but the problem below shows up inb all the archives. I run the command bin/arch small_centers and get the following error: #0 [EMAIL PROTECTED] figuring article archives 2008-February Pickling archive state into /var/lib/mailman/archives/private/small_centers/pipermail.pck Traceback (most recent call last): File bin/arch, line 200, in module main() File bin/arch, line 188, in main archiver.processUnixMailbox(fp, start, end) 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 624, in add_article author = fixAuthor(article.decoded['author']) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 62, in fixAuthor while i0 and (L[i-1][0] in lowercase or UnicodeDecodeError: 'ascii' codec can't decode byte 0xb5 in position 26: ordinal not in range(128) This actually looks like a problem in a specific email message in the archive. How do I identify the mesand how do I fix it? Thanks, Rob -- Rob Tanner UNIX Services Manager Linfield College, McMinnville OR -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Porting from a 2.1.5 installation to 2.1.7
Hi, I am retiring a server running Mailman 2.1.5 and need to port everything to a server running 2.1.7 (Fedora Core distribution). Can I take the lists directory and simply copy it from one server to another (i.e., is the format of the various files the same)? Is there anything else that needs to be copied? Thanks, Rob -- Rob Tanner UNIX Services Manager Linfield College, McMinnville OR -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Porting from a 2.1.5 installation to 2.1.7
That was very very helpful. Thanks! -- Rob Mark Sapiro said the following on 02/05/2008 01:22 PM: Rob Tanner wrote: I am retiring a server running Mailman 2.1.5 and need to port everything to a server running 2.1.7 (Fedora Core distribution). Can I take the lists directory and simply copy it from one server to another (i.e., is the format of the various files the same)? Is there anything else that needs to be copied? There are many threads on this in the archives of the mailman-users list. The FAQ at http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.004.htp points to a few of them. In short, for 2.1.5 to 2.1.7, you can move the lists/ directory and Mailman will transparently update config.pck formats as necessary as lists are accessed. Note the following: If you move the lists/*/request.pck files, you also need to move any data/heldmsg-* files. OTOH, you can ignore any held messages on the old server, in which case, it's better to not move the request.pck files. If you want to move archives, you can move the entire archives/private/ directory. You don't really need to worry about archives/public/ as the symlinks therein will be recreated on the new system as the lists are accessed, but if you want to move archives/public/, make sure that you move the symlinks and not the directories they point to. If you want to be selective about which archives to move, make sure that you move both the archives/private/listname/ and the archives/private/listname.mbox/ directories for each list. You also have to deal with MTA aliases on the new server if the MTA uses aliases for Mailman. If the domain names for web and email will be the same on the new server, that's all. If not, you need to run fix_url to update the lists. Also, in this case, it might be better to just move the archives/private/listname.mbox/ directories and rebuild the archives with bin/arch --wipe so that the listinfo links in the archives will have the correct host name. If you are going to rebuild archives, it is good to first check the archives/private/listname.mbox/listname.mbox file with bin/cleanarch. See: bin/arch --help bin/cleanarch --help http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.069.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] getting python errorss with check_perms
Hi, Running this as root so that it can fix any perm problems, but I'm getting what I assume to be python errors: [EMAIL PROTECTED] mailman]# bin/check_perms -f Traceback (most recent call last): File bin/check_perms, line 382, in module checkarchives() File bin/check_perms, line 216, in checkarchives print _(\ NameError: global name '_' is not defined I get the same errors without the '-f' argument. Any ideas? Thanks, Rob -- Rob Tanner UNIX Services Manager Linfield College, McMinnville OR -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] getting python errorss with check_perms
Todd, I think the bug URL you gave me is a wrong URL. Bug 132495 is a Japanese encoding bug and its status is closed (which I presume means fixed). That doesn't sound like the problem I'm seeing. In answer to your questions, the Fedora release is Fedora release 7 (Moonshine) and the mailman package installed is mailman-2.1.9-5.1 (output of rpm -qa). I just no checked, and there is not a more current package to download via yum. -- Rob Todd Zullinger said the following on 02/05/2008 04:34 PM: Rob Tanner wrote: Running this as root so that it can fix any perm problems, but I'm getting what I assume to be python errors: [EMAIL PROTECTED] mailman]# bin/check_perms -f Traceback (most recent call last): File bin/check_perms, line 382, in module checkarchives() File bin/check_perms, line 216, in checkarchives print _(\ NameError: global name '_' is not defined I get the same errors without the '-f' argument. Any ideas? You said in another thread that you're migrating to a Fedora Core system. Are you using the Fedora rpm packages of Mailman? This looks like a bug in one of the patches that is applied in the Fedora/Red Hat rpms. If you're using the rpms, what version of Fedora are you running, and what is the version and release of the mailman package? The changes I'm thinking of were discussed at https://bugzilla.redhat.com/132495 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/rtanner%40linfield.edu Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] getting python errorss with check_perms
Todd, That update took case of it. Thanks. -- Rob On 02/05/2008 05:56 PM, Todd Zullinger wrote: Rob Tanner wrote: I think the bug URL you gave me is a wrong URL. Bug 132495 is a Japanese encoding bug and its status is closed (which I presume means fixed). That doesn't sound like the problem I'm seeing. The bug summary may not sound like what you're seeing, but the patch that was applied to correct the initial problem does redefine _() and can cause the sort of errors you're seeing. I know this because I ran into some places where the patch was incomplete and caused just such a problem for me. :) In answer to your questions, the Fedora release is Fedora release 7 (Moonshine) and the mailman package installed is mailman-2.1.9-5.1 (output of rpm -qa). I just no checked, and there is not a more current package to download via yum. There may still be problems with the patch, as the maintainer noted in the last comment. The bug is closed with the resolution rawhide, which means that the latest updated patch may not have been pushed to F7 (I haven't looked closely, though you can by looking at the Fedora CVS: http://cvs.fedoraproject.org/viewcvs/rpms/mailman/) There does happen to be an update that is in the updates-testing repository, and the patch in question has been updated in that version (mailman-2.1.9-5.3.i386.rpm). You can download that directly or enable the updates-testing repo to install it with yum like so: yum --enablerepo=updates-testing update mailman This package should hit the standard updates repo very soon as it fixes CVE-2006-3636 (multiple cross-site scripting vulnerabilities). -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/rtanner%40linfield.edu Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Problem with URL host installing v2.1.9
Hi, This is a new install and not an update. I first ran configure with no options and then built/installed mailman. Then I reran configure with the argument: --with-urlhost=www.linfield.edu. I also verified Defaults.py: DEFAULT_URL_HOST = 'www.linfield.edu'. The problem is that the banners (stuff in the blue bar at the top of the page) all show the host name of the machine and not the URL host. Also, how do I give myself the authority to create lists from the web as opposed to running newlist from the command line. Whenever I try I get an error back saying that I'm not authorized. Thanks, Rob -- Rob Tanner UNIX Services Manager Linfield College, McMinnville OR -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Getting notifications for admin requests that don'eexist
Thanks. The crontab was the issue. -- Rob On 05/25/2006 10:29 PM, Mark Sapiro wrote: Rob Tanner wrote: I have at l;east one list owner (only one list owner has complained anyway) who is regularly getting email from Mailman with the subject 19 Small_centers admin request(s) waiting. When he clicks on the link, the page displays There are no pending requests. Click here to reload this page. I'm presuming that the web page is correct and the email wrong (but I'm not sure). Other than the web interface, how can I determine if there are, in fact, admin requests waiting. bin/dumpdb lists/listname/request.pck And if there aren't what would be causing the email message to get repeatedly generated. A crontab still running the cron/checkdbs job from a prior install/version in a different location. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Getting notifications for admin requests that don'e exist
Hi, I have at l;east one list owner (only one list owner has complained anyway) who is regularly getting email from Mailman with the subject 19 Small_centers admin request(s) waiting. When he clicks on the link, the page displays There are no pending requests. Click here to reload this page. I'm presuming that the web page is correct and the email wrong (but I'm not sure). Other than the web interface, how can I determine if there are, in fact, admin requests waiting. And if there aren't what would be causing the email message to get repeatedly generated. Thanks, Rob -- Rob Tanner UNIX Services Manager Linfield College, McMinnville OR -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Problem integrating v2.1.5 into the mail system
I upgraded from Mailman 2.0.6 to 2.1.5, and I'm having a problem with the aliases. My MTA is Postfix. Here's my problem. Our mail system uses the LDAP server for all the MTA required local aliases. However, on the specific server hosting Mailman, I modified the following line in the Postfix main.cf file to include the Mailman aliases file: alias_database = dbm:/etc/postfix/aliases,dbm:/opt/mailman_2.1.5/data/aliases Apart from hosting Mailman, that server is not part of our regular mail system. When a message is sent to listname@linfield.edu, Postfix, on which ever one of the mail gateway servers that first sees the message, looks up the alias, and then using the mailroutingaddress attribute, re-routes the mail to listname@calvin.linfield.edu, which is the actual name of the host. However, when the mail hits the Mailman server, Postfix reject it with the error: 550 listname@calvin.linfield.edu: User unknown in local recipient table The other pertinent setting in main.cf is: local_recipient_maps = $alias_maps, dbm:/opt/mailman_2.1.5/data/aliases I've played extensively with the various Postfix parameters, and I've not been able to resolve this problem. It probobly is a Postfix settings issue, and I'm hoping someone has had and resolved a similar issue. Thanks, Rob -- Rob Tanner UNIX Services Manager Linfield College, McMinnville OR -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem integrating v2.1.5 into the mail system
Cockpit error on my part. Your suggestions ended up pointing me right to it. Thanks, Rob John Dennis said the following on 09/13/2005 09:45 AM: On Tue, 2005-09-13 at 09:25 -0700, Rob Tanner wrote: I upgraded from Mailman 2.0.6 to 2.1.5, and I'm having a problem with the aliases. My MTA is Postfix. Here's my problem. Our mail system uses the LDAP server for all the MTA required local aliases. However, on the specific server hosting Mailman, I modified the following line in the Postfix main.cf file to include the Mailman aliases file: alias_database = dbm:/etc/postfix/aliases,dbm:/opt/mailman_2.1.5/data/aliases Apart from hosting Mailman, that server is not part of our regular mail system. When a message is sent to listname@linfield.edu, Postfix, on which ever one of the mail gateway servers that first sees the message, looks up the alias, and then using the mailroutingaddress attribute, re-routes the mail to listname@calvin.linfield.edu, which is the actual name of the host. However, when the mail hits the Mailman server, Postfix reject it with the error: 550 listname@calvin.linfield.edu: User unknown in local recipient table The other pertinent setting in main.cf is: local_recipient_maps = $alias_maps, dbm:/opt/mailman_2.1.5/data/aliases I've played extensively with the various Postfix parameters, and I've not been able to resolve this problem. It probobly is a Postfix settings issue, and I'm hoping someone has had and resolved a similar issue. Here are some things to check: In your main.cf file you've specified a file_type of dbm but I don't see anything in your mail saying you've told Mailman's Postfix.py to use that file format. Have you? It defaults to whatever is the default database type in your postfix installation. You should verify the file types are in fact in harmony with one another. You could take a look at postfix error logging to see if its complaining or use the postmap command to simulate the lookup. Also, it looks like you're performing domain mapping when you re-route to the primary server. If the alias lookup's include domain information you may fail the local_recipient_maps lookup because although the user part of the address is correct it may include a domain part not recognized by the server fielding the request. I would use the postmap command to simulate an alias lookup and see what is returned and make sure domains are not part of the alias or if they are that they match. -- Rob Tanner UNIX Services Manager Linfield College, McMinnville OR -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
