Re: [Mailman-Users] mailman + postfix + Debian - does not deliver any messages
I am sorry, i posted it wrong. It is un-commented But it is solved now I don't know if i upgraded any package coz /etc/aliases had to be in a diferent syntax: *profs-val:|/var/lib/mailman/mail/mailman post profs-val* profs-val-admin |/var/lib/mailman/mail/mailman admin profs-val profs-val-bounces |/var/lib/mailman/mail/mailman bounces profs-val profs-val-confirm |/var/lib/mailman/mail/mailman confirm profs-val profs-val-join |/var/lib/mailman/mail/mailman join profs-val profs-val-leave |/var/lib/mailman/mail/mailman leave profs-val profs-val-owner |/var/lib/mailman/mail/mailman owner profs-val profs-val-request |/var/lib/mailman/mail/mailman request profs-val profs-val-subscribe |/var/lib/mailman/mail/mailman subscribe profs-val profs-val-unsubscribe |/var/lib/mailman/mail/mailman unsubscribe profs-val *tecadm-val:|/var/lib/mailman/mail/mailman post tecadm-val* tecadm-val-admin |/var/lib/mailman/mail/mailman admin tecadm-val tecadm-val-bounces |/var/lib/mailman/mail/mailman bounces tecadm-val tecadm-val-confirm |/var/lib/mailman/mail/mailman confirm tecadm-val tecadm-val-join |/var/lib/mailman/mail/mailman join tecadm-val tecadm-val-leave |/var/lib/mailman/mail/mailman leave tecadm-val tecadm-val-owner |/var/lib/mailman/mail/mailman owner tecadm-val tecadm-val-request |/var/lib/mailman/mail/mailman request tecadm-val tecadm-val-subscribe |/var/lib/mailman/mail/mailman subscribe tecadm-val tecadm-val-unsubscribe |/var/lib/mailman/mail/mailman unsubscribe tecadm-val On Thu, Oct 23, 2008 at 12:15 PM, Brad Knowles [EMAIL PROTECTED]wrote: Bruno Guimarães Sousa wrote: *#profs-val |/var/lib/mailman/mail/mailman post profs-val #profs-val-admin |/var/lib/mailman/mail/mailman admin profs-val #profs-val-bounces |/var/lib/mailman/mail/mailman bounces profs-val #profs-val-confirm |/var/lib/mailman/mail/mailman confirm profs-val #profs-val-join |/var/lib/mailman/mail/mailman join profs-val #profs-val-leave |/var/lib/mailman/mail/mailman leave profs-val #profs-val-owner |/var/lib/mailman/mail/mailman owner profs-val #profs-val-request |/var/lib/mailman/mail/mailman request profs-val #profs-val-subscribe |/var/lib/mailman/mail/mailman subscribe profs-val #profs-val-unsubscribe |/var/lib/mailman/mail/mailman unsubscribe profs-val So you commented out all the aliases in question? That won't work very well. Mailing lists always worked for me creating them like this. But this time, when i restarted mailman, it showed me an error message and filled / partition with files in /var/lib/mailman (i don't know which files are these). Then / partition had zero of free space and postfix stopped working well. Yeah, that's a totally separate problem. You need to make sure the machine is configured correctly and working correctly, before we have a chance of hoping that Mailman will operate correctly. After i reduced disk usage, mailman is up and postfix is delivering messages fine. The problem is that none of the mailing lists are working, neither the 2 new ones nor the old ones. Try un-commenting the aliases, rebuild the alias file, then restart Mailman. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Bruno Guimarães Sousa www.brunosousa.co.nr COINF-CEFET-BA Ciência da Computação UFBA Registered Linux user #465914 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Question about footers (again)
I found this: http://mail.python.org/pipermail/mailman-developers/2005-February/017850.html If you want to go HTML all the way w/headers and footers and body. I have no idea if it works. Let us know if you try it! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Blocking a person from getting a single email
Hello, I administer a list and I want to send an email to everyone on the list except one person (we're getting him a Christmas gift and want it to stay secret from him). My plan is to set his nomail flag to on and then send the email then after getting the email in my inbox turning off his nomail (so that he'll get mail again). It's a low traffic list so there is no real risk of him missing any other emails. He doesn't get a digest and he is a list administrator and I'm using version 2.1.11.cp2. He'll never look in the archives, so that's not an issue. Can anyone see any reason why this wouldn't work? I've checked the documentation and it seems like this is the best plan but I'd thought I'd get y'alls input. Thanks. -Kevin -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Mark Sapiro wrote: Prior to 2.1.10, check_perms had a bug and didn't check the owner and group permissions on the archives/private directory itself. Permissions should be 2771 or maybe 2770 (drwxrws--x or drwxrws---). If archives/private is not o+x, it needs to be owned by the web server for public archive URLs to work. I changed it to 2771 (I just needed too do a chmod o-r). Subordinate directories should be 2775 (drwxrwsr-x) and subordinate files 0664 (-rw-rw-r--) except for the archives/private/*/database/ directory and subordinate files which should not have 'other' permissions. OK, this is confusing. The public archive directories are links (lrwxrwxrwx) to the private archive directories which contain the actual archives. Those directories are drwxrwsr-x. The files are 755. It is not clear to my why a help command to the -request address would try to lock the archive. Is (was) 2271 the pid of CommandRunner? No, it is 2273. I'm not sure I understand this question. The pid would depend on when qrunner was launched. I have stopped and started mailman several times so the pid could be anything, couldn't it? signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Blocking a person from getting a single email
Kevin Rector wrote: I've checked the documentation and it seems like this is the best plan but I'd thought I'd get y'alls input. Hmm. Sounds about like: If we hold our mouth right, and we hop up and down while spinning in a triangle-wise manner, and throat-sing Hava Nagila while drinking ten gallons of the worst rot-gut Tequila, we think this will work. But we wanted to check with you. I wouldn't recommend either procedure for any particular purpose, and if you're on a University campus and you're trying to get someone else to do something like this then you might get arrested for hazing. For what you want to achieve, why not just set up a separate mailing lists with all the same subscribers (except the intended victim), closed archives, and a different listowner password? There's still a number of different ways that things could leak out of that idea, but at least it's got a few smaller holes than depending on the victim not reading the archives, no one else responding to the message after his delivery is turned back on, etc -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Dennis Putnam wrote: Mark Sapiro wrote: Prior to 2.1.10, check_perms had a bug and didn't check the owner and group permissions on the archives/private directory itself. Permissions should be 2771 or maybe 2770 (drwxrws--x or drwxrws---). If= archives/private is not o+x, it needs to be owned by the web server for public archive URLs to work. I changed it to 2771 (I just needed too do a chmod o-r). Then that wasn't the problem. Subordinate directories should be 2775 (drwxrwsr-x) and subordinate files 0664 (-rw-rw-r--) except for the archives/private/*/database/ directory and subordinate files which should not have 'other' permissions. OK, this is confusing. The public archive directories are links (lrwxrwxrwx) to the private archive directories which contain the actual archives. Those directories are drwxrwsr-x. The files are 755. If the files are 755, that's OK, but they aren't executable so they really should be 644. And yes, the contents of archives/public are symlinks (the permissions of which are irrelevant). That's so archives can be changed from public to private and vice versa by just removing/creating symlinks. It is not clear to my why a help command to the -request address would try to lock the archive. Is (was) 2271 the pid of CommandRunner? No, it is 2273. I'm not sure I understand this question. The pid would depend on when qrunner was launched. I have stopped and started mailman several times so the pid could be anything, couldn't it? Yes, that's why I said (was). However, if CommandRunner is now 2773, it is likely that 2771 is another runner and was at the time. In any case, 2771 was the pid of the process that tried to create the lock. I asked, because I don't believe that the IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.2271.2' error came from your 'help' command mailed to -request. In any case, where did this error come from?. If it is in Mailman's error log, there should also be a traceback. What is that? -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] mailman + postfix + Debian - does not deliverany messages
Bruno Guimarães Sousa wrote: I am sorry, i posted it wrong. It is un-commented But it is solved now I don't know if i upgraded any package coz /etc/aliases had to be in a diferent syntax: *profs-val:|/var/lib/mailman/mail/mailman post profs-val* The colon : is correct it should be on all the aliases, not just the posting address. profs-val-admin |/var/lib/mailman/mail/mailman admin profs-val profs-val-bounces |/var/lib/mailman/mail/mailman bounces profs-val profs-val-confirm |/var/lib/mailman/mail/mailman confirm profs-val profs-val-join |/var/lib/mailman/mail/mailman join profs-val profs-val-leave |/var/lib/mailman/mail/mailman leave profs-val profs-val-owner |/var/lib/mailman/mail/mailman owner profs-val profs-val-request |/var/lib/mailman/mail/mailman request profs-val profs-val-subscribe |/var/lib/mailman/mail/mailman subscribe profs-val profs-val-unsubscribe |/var/lib/mailman/mail/mailman unsubscribe profs-val -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] How did I break my mailman?
I took an existing mailman web account that was working just fine and moved it from our test directory to our production directory. Mailman remains unchanged. Relative paths are all the same as they were before. I checked that. Subscriptions still work (as long as confirm is turned off in the privacy options) and all the admin functions seem to work as well. Yet, suddenly mailman seems unable to send out emails to any of its subscribers. It can't even send out new subscriber confirmation emails or your message was held for approval emails. In fact when I tried to turn enrollment confirmation on, pretty much everything stopped working but when I turned it back off again then users could once again sign up; but none of the messages mailman should be sending out to list members are actually getting mailed. All this stuff worked FINE yesterday before the move; so somehow this is clearly related to the move; but I'm not exactly sure what could be wrong. Any troubleshooting suggestions would be greatly appreciated. I'd like to answer these questions: 1. Why don't confirmations work? 2. 2. Why can't mailman send emails to list members? 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 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] How did I break my mailman?
TGPlatt, WebMaster wrote: All this stuff worked FINE yesterday before the move; so somehow this is clearly related to the move; but I'm not exactly sure what could be wrong. Any troubleshooting suggestions would be greatly appreciated. I'd like to answer these questions: See the FAQ at http://wiki.list.org/x/A4E9 for a troubleshooting check list. -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] How did I break my mailman?
On Fri, 24 Oct 2008, TGPlatt, WebMaster wrote: All this stuff worked FINE yesterday before the move; so somehow this is clearly related to the move; but I'm not exactly sure what could be wrong. Any troubleshooting suggestions would be greatly appreciated. I'd like to answer these questions: 1.Why don't confirmations work? 2.2. Why can't mailman send emails to list members? Did you by any chance forget to (re)install the crontab that runs most of Mailman's background tasks? -- L | I haven't lost my mind; it's backed up on tape somewhere. + Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130 IT Director / SysAdmin / WebSmith . 800.441.3873 x130 Photo Craft Laboratories, Inc.. 3550 Arapahoe Ave. #6 http://www.pcraft.com . . .. Boulder, CO 80303, U.S.A. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] How did I break my mailman?
Ashley M. Kirchner wrote: On Fri, 24 Oct 2008, TGPlatt, WebMaster wrote: All this stuff worked FINE yesterday before the move; so somehow this is clearly related to the move; but I'm not exactly sure what could be wrong. Any troubleshooting suggestions would be greatly appreciated. I'd like to answer these questions: 1. Why don't confirmations work? 2. 2. Why can't mailman send emails to list members? Did you by any chance forget to (re)install the crontab that runs most of Mailman's background tasks? Mailman 2.1.x does not rely on cron for anything to do with mail delivery except for periodic digests and the news-mail gateway. -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] How did I break my mailman?
Thanks Mark... obviously one of those things was exactly the enema mailman needed because as soon as I finished them (and restarted our server) I found a whole boatload of emails in each of my test subscriber inboxes. I guess that means all the other list members probably got them too. Although I've absolutely nothing that should have changed permissions in DAYS now (and when I last checked permissions, it was clean, check_perms still did find a single permissions error on aliases.db Could THAT have somehow been the cause of mailman's sudden bout of email constipation? If so, do you any idea what might have caused the permission change when I'd done nothing to those files? I'm going back to do some further testing now, but it looks like we managed to break the log jam. Thanks again. -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Friday, October 24, 2008 12:34 PM To: [EMAIL PROTECTED]; mailman-users@python.org Subject: Re: [Mailman-Users] How did I break my mailman? TGPlatt, WebMaster wrote: All this stuff worked FINE yesterday before the move; so somehow this is clearly related to the move; but I'm not exactly sure what could be wrong. Any troubleshooting suggestions would be greatly appreciated. I'd like to answer these questions: See the FAQ at http://wiki.list.org/x/A4E9 for a troubleshooting check list. -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] How did I break my mailman?
TGPlatt, WebMaster wrote: Thanks Mark... obviously one of those things was exactly the enema mailman needed because as soon as I finished them (and restarted our server) I found a whole boatload of emails in each of my test subscriber inboxes. I guess that means all the other list members probably got them too. Although I've absolutely nothing that should have changed permissions in DAYS now (and when I last checked permissions, it was clean, check_perms still did find a single permissions error on aliases.db Could THAT have somehow been the cause of mailman's sudden bout of email constipation? If so, do you any idea what might have caused the permission change when I'd done nothing to those files? Creating/deleting lists with MTA = 'Postfix' updates data/aliases and then runs POSTFIX_ALIAS_CMD (default '/usr/sbin/postalias') to update aliases.db. This can change the ownership/permissions on aliases.db, but it shouldn't cause any problem, and if it did cause a problem, it would cause Postfix to reject incoming mail; it wouldn't affect outgoing mail delivery. The likely cause of no outgoing mail in this case is OutgoingRunner not running or hung waiting for an SMTP response from the outgoing MTA. Check Mailman's 'error', 'qrunner' and 'smtp-failure' logs for any error reports. -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] What happened to my archive? Why isn't the archive process running?
Okay, so now that I've got finally mailman moved and running on the new server and working with postfix and apache2 and sending and receiving emails and all that basic stuff, I still have one question I haven't been able to answer. I seem to be missing two full months worth of archives. From what I can tell looking at my backups, it appears that the last time the archive process actually ran on our old server was in early August. Then for some reason it stopped funning and thee have been no archive updates since then. I suspect those lost messages aren't really lost at all but are merely caught in some sort of internal blockage in mailman. What I'm trying to figure out here is how to clear the clogged drain pipe and get the archive working again. When I first installed the backup from the old server to the new one and then checked the list's configuration parameters, I saw some parameters on the Archiving options page that provided for rebuilding the archive. But now those options seem to have disappeared now too. Can Mark or someone else tell me how I go about figuring out where my missing messages have gone and get the archive working again as it should be? 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 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] What happened to my archive? Why isn't the archiveprocess running?
TGPlatt, WebMaster wrote: I seem to be missing two full months worth of archives. From what I can tell looking at my backups, it appears that the last time the archive process actually ran on our old server was in early August. Then for some reason it stopped funning and thee have been no archive updates since then. I suspect those lost messages aren't really lost at all but are merely caught in some sort of internal blockage in mailman. What I'm trying to figure out here is how to clear the clogged drain pipe and get the archive working again. There are a few possibilities: 1) ArchiveRunner died on the old server in early August. In this case, the messages would be on the old server in the qfiles/arch/ directory. If that is the case, you could just move the contents of that directory to the corresponding directory on the new server and that should do it. 2) Some error was shunting the archived messages in which case they may be in qfiles/shunt/ and they may or may not be in the individual archives/private/listname.mbox/listname.mbox files. If the messages are in qfiles/shunt/, you could just move them and rin bin/unshunt, but you need to be careful as not all the files in qfiles/shunt/ may be messages you want. You can look at these entries with bin/show_qfiles or bin/dumpdb. If the messages are in the listname.mbox files, the easiest thing is probably to rebuild the archives with bin/arch --wipe. When I first installed the backup from the old server to the new one and then checked the list's configuration parameters, I saw some parameters on the Archiving options page that provided for rebuilding the archive. But now those options seem to have disappeared now too. I don't know what you say, but there's nothing in the web Archiving Options page about rebuilding archives. -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] What happened to my archive? Why isn't thearchiveprocess running?
Mark Sapiro wrote: I don't know what you say, but there's nothing in the web Archiving Options page about rebuilding archives. That should be I don't know what you saw, ... -- 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
