Re: [Mailman-Users] Send Mail delay
Mark Sapiro wrote: > >You can't do this directly in mailman. There are some discussions of >these kinds of issues in the archives for the mailman-users list, but >I can't find any right now. Shame on me. There's a FAQ on this at http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.051.htp. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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=show&file=faq01.027.htp
Re: [Mailman-Users] Send Mail delay
smeg <[EMAIL PROTECTED]> (Chris) wrote: >I have recently set up mailman (2.1.5p2) and am very impressed with it. >I have a question though, is it possible to have it delay the >sending of the messages? >If send to many emails in period x through my mail server it locks >me out for about 1 hour. If i could specify a time delay between each >message, this would fix the problem. >What i find is my mail server will only allow about 100 emails >/hour. My list has about 80 people on it, so if 2 messages are sent in >in one hour i have a problem. You can't do this directly in mailman. There are some discussions of these kinds of issues in the archives for the mailman-users list, but I can't find any right now. Even if you could do as you suggest, I don't think it would be a good idea. Suppose your list started getting more than 24 posts per day. You'd never work through the backlog. Here's a thought. Set your list so only digest subscribers are allowed (nondigestable = No on Non-digest options), make sure digest_send_periodic is Yes and set all your current subscribers to digest. Then set the crontab for the senddigests job to run it every hour. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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=show&file=faq01.027.htp
[Mailman-Users] Send Mail delay
I have recently set up mailman (2.1.5p2) and am very impressed with it. I have a question though, is it possible to have it delay the sending of the messages? If send to many emails in period x through my mail server it locks me out for about 1 hour. If i could specify a time delay between each message, this would fix the problem. What i find is my mail server will only allow about 100 emails /hour. My list has about 80 people on it, so if 2 messages are sent in in one hour i have a problem. Thanks for any help u can give on this issue. Cheers Chris -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Uncaught runner exception
Salada, Duncan S.wrote: > >I have a follow-up question. Is there a source for information about the >contents of the qfiles and logs directories? Part of my time in dealing with >this problem was spent trying to figure out how to follow the path of a >message through mailman's different logs and qfile directories. > A high level overview is in comments in Mailman/Queue/IncomingRunner.py. This does not cover the detail of the post from receipt to delivery. Basically, this consists of the IncomingRunner passing the message through the pipeline of Mailman/Handlers/* modules defined by GLOBAL_PIPELINE in Defaults.py/mm_cfg.py. The qfiles/* directories are the queues for the various runners. the files therein each contain a message and various processing information about the message. The contents is best viewed with bin/show_qfiles although if there is a problem with the queue entry that causes a processing error, bin/show_qfiles will probably get the same error. In this case, bin/dumpdb might be helpful. As far as I know, there is no documentation of log entries other thatn looking at the code that writes them. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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=show&file=faq01.027.htp
Re: [Mailman-Users] Bounce-events pck files...
Mark Sapiro said the following on 6/8/2005 4:19 PM: >Yes, they are mostly if not all garbage and yes, they contain >unprocessed bounce messages. > > Ah-hah! Thank you, Mark! I think I can code up a script to safely clean these out. :) Thanks again! Best, --Glenn -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." ~Benjamin Franklin, Historical Review of Pennsylvania, 1759 -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Bounce-events pck files...
Glenn Sieb wrote: > >I was just looking in my mailman/data directory and noticed that I have >155 of these bounce-events-#.pck files taking up about 24 meg of >space there. > >They date back as far as January 18th of this year. Are these garbage >files? Unprocessed bounce messages? What does one do with these--I >didn't see anything on the FAQ or FAQ-wizard... Yes, they are mostly if not all garbage and yes, they contain unprocessed bounce messages. The # in bounce-events-#.pck is the pid of the bounce runner that wrote the file. Here are comments from BounceRunner.py describing the file: # Registering a bounce means acquiring the list lock, and it would be # too expensive to do this for each message. Instead, each bounce # runner maintains an event log which is essentially a file with # multiple pickles. Each bounce we receive gets appended to this file # as a 4-tuple record: (listname, addr, today, msg) # # today is itself a 3-tuple of (year, month, day) # # Every once in a while (see _doperiodic()), the bounce runner cracks # open the file, reads all the records and registers all the bounces. # Then it truncates the file and continues on. We don't need to lock # the bounce event file because bounce qrunners are single threaded # and each creates a uniquely named file to contain the events. If the pid is not that of a running bounce runner, the file is dead and can be deleted. Presumably, these dead files can come about if the bounce runner dies or mailman is stopped or restarted when a non-empty file exists. The contents of these files can be examined with bin/dumpdb. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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=show&file=faq01.027.htp
Re: [Mailman-Users] Finding abandoned lists and most recent activity
Quoting Mike Alberghini <[EMAIL PROTECTED]>: > I'm the admin of a Mailman system with several hundred lists. I'm trying to > write some scripts that will scan the mailman directory tree and find lists > that are abandoned, never used, etc. > The following is what I use to find 'potentially' dead lists. Mailman modifies the /list/config.pck every night processing digests, so finding an access or modified time on those was not an option. I used the theory that if an owner hasn't accessed their admin page in a year, it either means their list is _very_ stable, or the list is dead. There may also be lists that are only used once a year. I determine the last time a list's admin page was accessed by using a webpage counter by Muhammad A Muquit, [EMAIL PROTECTED] from http://www.muquit.com/muquit/software/Count/Count.html The counter is hidden on the list admin page, but I have the access time recorded in /usr/local/etc/Counter/data in the form listname.dat: 16 Jun 6 08:00 list1.dat 16 May 28 22:39 list2.dat 16 Jun 2 12:27 list3.dat In a year's time, I'll run a script like #!/bin/sh # Find lists that haven't been modified in the last year and mail report. cd /usr/local/etc/Counter/data find . -name '*.dat' -ctime +365 -print > /tmp/oldys if [ -s /tmp/oldys ]; then cat /tmp/oldys | mailx -s "Mailman unused list check" somebody fi rm /tmp/oldys exit At that point, I can email the owners and ask if they still want the list. Or change the script above to email each owner in a 'for..do' loop. Dennis Black Internet Applications Computing and Network Services Ph:(780)492-9329 Fx:(780)492-1729 news stats http://news.srv.ualberta.ca mailman stats http://www.mailman.srv.ualberta.ca/graph/mailgraph -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Finding abandoned lists and most recent activity
Mike Alberghini wrote: > >The main thing I'm trying to figure out is how to know when the last post to >a list was. Lists have an attribute last_post_time which is equal to zero if the list has never been posted to. Otherwise it is result of the Python library time.time() function at the time of the last post. See http://docs.python.org/lib/module-time.html#l2h-1944 -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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=show&file=faq01.027.htp
[Mailman-Users] Bounce-events pck files...
I run Mailman 2.1.5 on FreeBSD 4.11-RELEASE, with Apache 2.0.54, and Postfix 2.2.3 I was just looking in my mailman/data directory and noticed that I have 155 of these bounce-events-#.pck files taking up about 24 meg of space there. They date back as far as January 18th of this year. Are these garbage files? Unprocessed bounce messages? What does one do with these--I didn't see anything on the FAQ or FAQ-wizard... Thanks in advance! Best, --Glenn -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." ~Benjamin Franklin, Historical Review of Pennsylvania, 1759 -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Uncaught runner exception
Thanks for the code snippet. It worked very well. I also appreciate the warning about the indentation. I work mostly in Perl, so I don't generally have to worry about indentation. I have a follow-up question. Is there a source for information about the contents of the qfiles and logs directories? Part of my time in dealing with this problem was spent trying to figure out how to follow the path of a message through mailman's different logs and qfile directories. Duncan --- Duncan Salada Titan Corporation 301-925-3222 x375 > -Original Message- > From: Mark Sapiro [mailto:[EMAIL PROTECTED] > Sent: Monday, June 06, 2005 4:21 PM > To: Salada, Duncan S.; mailman-users@python.org > Subject: Re: [Mailman-Users] Uncaught runner exception > > > Salada, Duncan S.wrote: > > >I have a problem with one of my lists. I have 4 lists, and > 3 seem to be working fine. The fourth one worked fine for > the first couple of weeks, but then started having problems. > No changes were made to the configuration during that time. > The problem is this: mail will not go out to any of the users. > > > >This list was configured to have only one recipient and > allow anyone to post to it (sort of a spam catcher). I've > checked everything in the most applicable FAQ > (http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03. > 014.htp). In the error log, I keep getting "Uncaught runner > exception: len() of unsized object" (the full log entry with > Traceback is at the bottom of the email). > > > >I am running Mailman 2.1.4 installed from source on Solaris > 6 with sendmail. > > > >Any help, information, suggestions would be greatly appreciated. > > > > ERROR LOG = > >Jun 06 15:10:09 2005 (27089) Uncaught runner exception: > len() of unsized object > >Jun 06 15:10:09 2005 (27089) Traceback (most recent call last): > > File "/usr/local/mailman-2.1.4/Mailman/Queue/Runner.py", > line 110, in _oneloop > >self._onefile(msg, msgdata) > > File "/usr/local/mailman-2.1.4/Mailman/Queue/Runner.py", > line 160, in _onefile > >keepqueued = self._dispose(mlist, msg, msgdata) > > File > "/usr/local/mailman-2.1.4/Mailman/Queue/IncomingRunner.py", > line 130, in _dispose > >more = self._dopipeline(mlist, msg, msgdata, pipeline) > > File > "/usr/local/mailman-2.1.4/Mailman/Queue/IncomingRunner.py", > line 153, in _dopipeline > >sys.modules[modname].process(mlist, msg, msgdata) > > File > "/usr/local/mailman-2.1.4/Mailman/Handlers/ToDigest.py", line > 91, in process > >send_digests(mlist, mboxfp) > > File > "/usr/local/mailman-2.1.4/Mailman/Handlers/ToDigest.py", line > 132, in send_digests > >send_i18n_digests(mlist, mboxfp) > > File > "/usr/local/mailman-2.1.4/Mailman/Handlers/ToDigest.py", line > 306, in send_i18n_digests > >msg = scrubber(mlist, msg) > > File > "/usr/local/mailman-2.1.4/Mailman/Handlers/Scrubber.py", line > 262, in process > >size = len(payload) > >TypeError: len() of unsized object > > > >Jun 06 15:10:09 2005 (27089) SHUNTING: > 1118084879.080544+37fc5a2467c00ef900e9933a77c481ec4aa67de3 > > END ERROR LOG = > > > The error is because of a badly formed mime multipart message. The > Mailman 2.1.6 version of Scrubber.py contains the following insert > before the 'size = len(payload)'. > > > # XXX Under email 2.5, it is possible that payload will be None. > # This can happen when you have a Content-Type: multipart/* with > # only one part and that part has two blank lines between the > # first boundary and the end boundary. In email 3.0 you end up > # with a string in the payload. I think in this case > it's safe to > # ignore the part. > if payload is None: > continue > size = len(payload) > > The reference to email 2.5 is the Python library email module. > > These errors put the message in the shunt queue (qfiles/shunt/). > Presumably the message or some residue of it is still elsewhere, > probably in lists//digest.mbox, causing this error to occur > for each new message. > > You could install the above code in Scrubber.py. If so, be careful - > the above isn't indented the right amount and indentation counts. > > Otherwise, you could try to identify the bad message in the > shunt queue > and delete it and also edit digests.mbox to remove it from there too. > Then you can probably run bin/unshunt and be OK, or if you just want > to get things started again without worrying about lost messages, you > can just remove the digests.mbox and delete the messages from the > shunt queue. > > -- > Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http:/
Re: [Mailman-Users] Finding abandoned lists and most recent activity
* Mike Alberghini <[EMAIL PROTECTED]>: > I'm the admin of a Mailman system with several hundred lists. I'm > trying to write some scripts that will scan the mailman directory tree > and find lists that are abandoned, never used, etc. For these unused lists it's probably the easiest to scan the mail.log. > The main thing I'm trying to figure out is how to know when the last post to > a list was. mail.log > We have lists that archive (easy) lists that don't archive and lists > that used to archive but no longer do. Mailman logs that kind of stuff in the mailman "post" or "smtp" log. > Is there a flag or a file with a last-modified date that will tell me when the > last post to a list was? I'm looking for actual posts, not messages that were > sent and rejected, deferred or held. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] -- 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=show&file=faq01.027.htp
[Mailman-Users] Finding abandoned lists and most recent activity
I'm the admin of a Mailman system with several hundred lists. I'm trying to write some scripts that will scan the mailman directory tree and find lists that are abandoned, never used, etc. The main thing I'm trying to figure out is how to know when the last post to a list was. We have lists that archive (easy) lists that don't archive and lists that used to archive but no longer do. Is there a flag or a file with a last-modified date that will tell me when the last post to a list was? I'm looking for actual posts, not messages that were sent and rejected, deferred or held. I'm trying to find the following kinds of lists: 1. Lists that have been posted to in the past six months 2. Lists that have not been posted to in the past six months 3. Lists that have never been posted to. I'm having trouble figuring out the difference between a list that has had no activity and one that does not archive. Any suggestions would be greatly appreciated. -- Michael Alberghini Software Systems Engineer Georgia State University [EMAIL PROTECTED] -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Forwarding a Moderated Message/Content Type
Hunter Hillegas wrote: >I want to ask something before I send out a message to a huge list. > >The message is an HTML message. I setup the list and subscribed three >people, then sent the message as a test. It came through perfectly. > >I have now subscribed all my users and am ready to send the message to the >list. Right now it is in the moderated queue. > >>From that Web page, I used the option: >" Forward messages (individually) to:" > >The message I received from this forward DID NOT look correct. > >The content types of the two messages are different: > >Correct HTML: Content-Type: multipart/alternative; >Incorrect (Forward): Content-Type: message/rfc822 When you forward a message from the admindb interface, it is "forwarded as an attachment". Thus the entire message, including all its headers, mime structure, etc., becomes the message/rfc822 contents of the delivered "forwarded" message. If you look at the contents of the message/rfc822 part, it should be your original message with Content-Type" multipart/alternative and all the original subparts, and it is this message that will be delivered to the list upon approval. >Looking at the headers for the forwarded message, it looks like it wraps the >original content in a plain text message... Actually, a message/rfc822, not text/plain, message >If that is true, when I approve >the message it should go through with the correct Content-Type, yes? Yes, it will. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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=show&file=faq01.027.htp
Re: [Mailman-Users] Messages silently dropped after being approved
Ryan Rempel wrote: >I am having a problem with messages sometimes being silently dropped >after being approved. I don't know if this is happening in your case, but one way this can happen is if content filtering discards the message after it is approved. Content filtering is not normally applied until after moderation and other holds are checked, so an approved post can still have all its content removed by content filtering and then be handled according to filter_action. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://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=show&file=faq01.027.htp
Re: [Mailman-Users] listinclusion patch (was: Messages not delivered *RESOLVED*)
Robert Haack wrote:
>
>I setup another copy of Mailman on a different server and created all of
>the exact same test lists I had on my live server. However on this
>server I did not install Jim Tittsler's patch to allow another list to
>post to a list. I just copied the users who could post to the list into
>the "Addresses that should be accepted". I created a quick and dirty
>program to send emails to all of the lists as different user names.
>After running 30 tests I had no problems with any messages getting
>lost. So today I changed all of my test lists on my live server so that
>they no longer use a list name to verify who can post to the list. I
>just took their names and pasted them in. I ran another 30 tests and
>again had no problem. So to me it seems to be this patch that caused my
>problems and the patch works great if a user only posts to a single
>list, but if they post to multiple lists then that's when the problem
>arose for me.
I think I see the problem with the listinclusion patch. It locks the
@list list and doesn't unlock it. I don't see a need to lock the list,
so I suggest changing the following piece of the patch
+elif are.startswith('@'):
+ try:
+ mother = MailList(are[1:])
+ if mother.members.has_key(sender):
+ return 1
+except Errors.MMUnknownListError:
+syslog('error', 'filter references non-existent list
%s',
+are[1:])
to
+elif are.startswith('@'):
+ try:
+ mother = MailList(are[1:], lock=0)
+ if mother.members.has_key(sender):
+ return 1
+except Errors.MMUnknownListError:
+syslog('error', 'filter references non-existent list
%s',
+are[1:])
>So now I have another question. Is there some way that I can
>automatically add a name to the "List of non-member addresses whose
>postings should be automatically accepted?" For us this list changes on
>a regular basis and I'd hate to have to go through our 20+ lists and
>update them all manually?
You could create a shell script that would use bin/list_members to
build a file of addresses for the accept_these_nonmembers list, even
sorting and dropping dups from it, then use awk or sed or ? to turn it
into input for bin/config_list and run config_list.
You might want to make the above change to the patch and try it on your
test system first.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://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=show&file=faq01.027.htp
