Re: [Mailman-Users] mailman to RSS
On Sun, Jan 10, 2010 at 08:20:46AM -0600, mark lane wrote: Hope things are going well! Do happen to know an easy way to setup a mailman to RSS feed? From the listinfo: You might want to start by reading the Mailman FAQ Wiki. Also check out the official searchable archives. There was a thread within the last few days on the very same question. -- ```Our team was the worst in the First Division and I'm sure it'll be the worst in the Premier League.'' [Sir Jack actually said] ``Our tea was the worst in the First Division and I'm sure it'll be the worst in the Premier League.'' Profuse apologies.' (correction, in The Guardian) -- 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] mailman to RSS
On Jan 10, 2010, at 9:20 AM, mark lane wrote: Hi, Hope things are going well! Do happen to know an easy way to setup a mailman to RSS feed? I have a patch set for 2.1.12 that also works with 2.1.13 that we've been using for a while now that does the job if you're interested. e. -- 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] How to change configs for ALL lists?
Well, what concerns me is that the spammers are going at these mass subscriptions via the web interface and it may become a game of whack-a-mole banning domains and IPs. Are there any plans to make the web form subscription more of a hurdle for spammers, e.g. captcha, etc? e. -- 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] API Version Mismatch
I'm calling config_list to take backups and get the following: /usr/local/mailman/pythonlib/korean/c/euc_kr.py:24: RuntimeWarning: Python C API version mismatch for module _koco: This Python has API version 1012, module _koco has version 1011. The dump appears to work correctly, is that error safe to ignore? I've seen a couple other posts regarding this but have not been able to locate any previous solutions. Pertinent environmental information: [r...@bushlms01 scripts]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.4 (Tikanga) [r...@bushlms01 scripts]# uname -a Linux bushlms01 2.6.18-164.9.1.el5 #1 SMP Wed Dec 9 03:29:54 EST 2009 i686 i686 i386 GNU/Linux [r...@bushlms01 scripts]# /usr/local/mailman/bin/version Using Mailman version: 2.1.5 [r...@bushlms01 scripts]# /usr/bin/python -V Python 2.4.3 Thanks in advance, Darren Young Systems Security Architect Computing Services University of Chicago Booth School of Business 5807 South Woodlawn Avenue Chicago, IL 60637 Voice 773.702.0331 | Fax 773.702.0233 -- 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] Mailman backup script
We've been using a config_list based shell script for the past several years to backup all of our Mailman mailing lists. While I was in making some changes today I thought I would post it, perhaps the community can get some value out of it as well. It is available at: http://home.uchicago.edu/~youngd/mailman/dump_configs.txt Darren Young Systems Security Architect Computing Services University of Chicago Booth School of Business 5807 South Woodlawn Avenue Chicago, IL 60637 Voice 773.702.0331 | Fax 773.702.0233 -- 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] API Version Mismatch
Young, Darren wrote: I'm calling config_list to take backups and get the following: /usr/local/mailman/pythonlib/korean/c/euc_kr.py:24: RuntimeWarning: Python C API version mismatch for module _koco: This Python has API version 1012, module _koco has version 1011. The dump appears to work correctly, is that error safe to ignore? Yes, but... (You probably also have the same warning in Mailman's error log from each of the qrunners whenever you start or restart Mailman.) The error occurs because the korean Codecs in /usr/local/mailman/pythonlib/korean/ were built and installed with a different Python version from the one that Mailman is running under. Probably you installed a package and then upgraded Python, or perhaps the package rpm was just built with a different Python. -- 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] How to change configs for ALL lists?
Elaine Ashton wrote: Well, what concerns me is that the spammers are going at these mass subscriptions via the web interface and it may become a game of whack-a-mole banning domains and IPs. Are there any plans to make the web form subscription more of a hurdle for spammers, e.g. captcha, etc? I'm not a big believer in captcha's (advances in tech have made a lot of them trivially easy to in an automated way, making them annoying to users for little gain) but it might be worth thinking about a plug in architecture for this in mm3 in case something better does come up, or so people can enjoy their placebos... -- 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] How to change configs for ALL lists?
On Jan 12, 2010, at 1:47 PM, Terri Oda wrote: I'm not a big believer in captcha's (advances in tech have made a lot of them trivially easy to in an automated way, making them annoying to users for little gain) but it might be worth thinking about a plug in architecture for this in mm3 in case something better does come up, or so people can enjoy their placebos... Even if it only serves to annoying and slow down spammers, I'd use it. I noted ~2000 zeusmail.org subs overnight and it concerns me that this is just the opening salvo since this will drive lists which are already closed to subscribers only to moderate traffic even from subscribers which, for sites like ours with 400 or more lists, isn't really practical. Banning the domain and blocking the IP(s) is only a temporary fix. e. -- 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] How to change configs for ALL lists?
On Tue, Jan 12, 2010 at 01:59:57PM -0500, Elaine Ashton wrote: Even if it only serves to annoying and slow down spammers, I'd use it. I noted ~2000 zeusmail.org subs overnight Have you thought about rate-limiting? -- ``What does it mean? It means I never have to work again.'' (Don McLean, on `American Pie', attrib.) -- 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] How to change configs for ALL lists?
Elaine Ashton Even if it only serves to annoying and slow down spammers, I'd use it. I noted ~2000 zeusmail.org subs overnight and it concerns me that this is just the opening salvo since this will drive lists which are already closed to subscribers only to moderate traffic even from subscribers which, for sites like ours with 400 or more lists, isn't really practical. Banning the domain and blocking the IP(s) is only a temporary fix. My .02 - every list to which someone can subscribe without admin approval should moderate new members by default. When they post, if their post is on topic, you can clear their mod bit while approving the post from the web admindb interface with one extra check in a checkbox. -- 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] Help!
I'm a new member and I'm not sure how to use the system or the capabilities of mailman to be useful to my bennefit. This may sound silly but I need to be educated some what in mailman and/or if it is even useful for me. I'm just stating to learm (some) html, long way to go, and could use help. Who or where can I get that, please. Thank you, John Create Your Own Viral Software Empire Free For A Limited Time Only! http://www.imbuzzsoftware.com/?afid=38072 -- 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] Help!
John Ditzel wrote: I'm a new member and I'm not sure how to use the system or the capabilities of mailman to be useful to my bennefit. This may sound silly but I need to be educated some what in mailman and/or if it is even useful for me. I'm just stating to learm (some) html, long way to go, and could use help. Who or where can I get that, please. You might start with the documentation at http://www.list.org/docs.html -- 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] How to change configs for ALL lists?
On Jan 12, 2010, at 2:08 PM, Mark Sapiro wrote: My .02 - every list to which someone can subscribe without admin approval should moderate new members by default. When they post, if their post is on topic, you can clear their mod bit while approving the post from the web admindb interface with one extra check in a checkbox. That's a fair point, but the number of lists I've got with somewhat *ahem* lax admins, that seems a formidable load to add to our ops team, even with the cli tools we have. But...I may consider that route. e. -- 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] many Subscription disabled messages after moving list to new server
I recently moved a list to a new host, but retained the domain name. After many travails, and help from this list, I got my list working. After about a week of function, I am suddenly getting many Subscription disabled messages (about 10% of the 4411 subscribers, so far, but still growing as I write). It is possible that these are legitimate, and these really are bad addresses, and that in the move of the list my bounce processing options changed to be more stringent. Current they are: bounce_processing=Yes bounce_score_threshold= 5.0 bounce_info_stale_after=7 bounce_you_are_disabled_warnings=5 bounce_you_are_disabled_warnings_interval=7 bounce_unrecognized_goes_to_list_owner=no bounce_notify_owner_on_disable=yes bounce_notify_owner_on_removal=yes But it seems likely that this is bogus, and good addresses are being disabled (especially if this grows to 100% of subscribers!) Has anyone experienced a similar problem? -Andrew -- 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] How to change configs for ALL lists?
Hi All-- On Tue, Jan 12, 2010 at 12:08 PM, Mark Sapiro m...@msapiro.net wrote: Elaine Ashton Even if it only serves to annoying and slow down spammers, I'd use it. I noted ~2000 zeusmail.org subs overnight and it concerns me that this is just the opening salvo since this will drive lists which are already closed to subscribers only to moderate traffic even from subscribers which, for sites like ours with 400 or more lists, isn't really practical. Banning the domain and blocking the IP(s) is only a temporary fix. My .02 - every list to which someone can subscribe without admin approval should moderate new members by default. When they post, if their post is on topic, you can clear their mod bit while approving the post from the web admindb interface with one extra check in a checkbox. Except that in this case, the new subscribers from zeusmail won't ever post; they'll lurk and snarf email addresses of those who do post. Better not to allow them to subscribe to begin with. Metta, Ivan -- Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningham.html Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours -- 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] many Subscription disabled messages after movinglist to new server
Andrew Watson wrote: I recently moved a list to a new host, but retained the domain name. After many travails, and help from this list, I got my list working. After about a week of function, I am suddenly getting many Subscription disabled messages (about 10% of the 4411 subscribers, so far, but still growing as I write). It is possible that these are legitimate, and these really are bad addresses, and that in the move of the list my bounce processing options changed to be more stringent. Current they are: bounce_processing=Yes bounce_score_threshold= 5.0 bounce_info_stale_after=7 bounce_you_are_disabled_warnings=5 bounce_you_are_disabled_warnings_interval=7 bounce_unrecognized_goes_to_list_owner=no bounce_notify_owner_on_disable=yes bounce_notify_owner_on_removal=yes But it seems likely that this is bogus, and good addresses are being disabled (especially if this grows to 100% of subscribers!) Has anyone experienced a similar problem? bounce_notify_owner_on_disable=yes so you should get a notice for each disable containing a copy of the triggering DSN. What does it say? Does it look legitimate? Also, what if anything do you see in Mailman's smtp-failure log? -- 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] many Subscription disabled messages after moving list to new server
Hi Andrew, I'd have a look to see if the email addresses that are being disabled come from similar domains... problem might be caused by reverse dns or spf records - check out http://knol.google.com/k/ruben-rubio-rey/mail-servers-spam-and-dns-records/2zt8z36uq2soj/5# for some ideas. Regards, James. I recently moved a list to a new host, but retained the domain name. After many travails, and help from this list, I got my list working. After about a week of function, I am suddenly getting many Subscription disabled messages (about 10% of the 4411 subscribers, so far, but still growing as I write). It is possible that these are legitimate, and these really are bad addresses, and that in the move of the list my bounce processing options changed to be more stringent. Current they are: bounce_processing=Yes bounce_score_threshold= 5.0 bounce_info_stale_after=7 bounce_you_are_disabled_warnings=5 bounce_you_are_disabled_warnings_interval=7 bounce_unrecognized_goes_to_list_owner=no bounce_notify_owner_on_disable=yes bounce_notify_owner_on_removal=yes But it seems likely that this is bogus, and good addresses are being disabled (especially if this grows to 100% of subscribers!) Has anyone experienced a similar problem? -Andrew -- 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/james%40thereidsonline.com -- 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] many Subscription disabled messages after movinglist to new server
The bounce notices I get look legitimate. They typically include something like: Reason: Remote SMTP server has rejected address Diagnostic code: smtp;550 alb...@cvc.uab.es... User unknown Mailman's smtp-failure log contains many instances of lines like this (edited, vsad...@mysite.com is the list administrator) Jan 12 20:48:44 2010 (70977) Low level smtp error: Connection unexpectedly closed, msgid: mailman.1063.1263328366.70976.visionl...@mysite.com Jan 12 20:48:45 2010 (70977) delivery to vsad...@mysite.com failed with code -1: Connection unexpectedly closed There are also a few like this: Jan 12 20:02:54 2010 (70977) Low level smtp error: (48, 'Address already in use'), msgid: mailman.561.1263325634.70976.visionl...@mysite.com Jan 12 20:02:54 2010 (70977) delivery to visionlist-ow...@mysite.com failed with code -1: (48, 'Address already in use') These log messages commenced on Jan 12 (today). -Andrew On Jan 12, 2010, at 1:23 PM, Mark Sapiro wrote: Andrew Watson wrote: I recently moved a list to a new host, but retained the domain name. After many travails, and help from this list, I got my list working. After about a week of function, I am suddenly getting many Subscription disabled messages (about 10% of the 4411 subscribers, so far, but still growing as I write). It is possible that these are legitimate, and these really are bad addresses, and that in the move of the list my bounce processing options changed to be more stringent. Current they are: bounce_processing=Yes bounce_score_threshold= 5.0 bounce_info_stale_after=7 bounce_you_are_disabled_warnings=5 bounce_you_are_disabled_warnings_interval=7 bounce_unrecognized_goes_to_list_owner=no bounce_notify_owner_on_disable=yes bounce_notify_owner_on_removal=yes But it seems likely that this is bogus, and good addresses are being disabled (especially if this grows to 100% of subscribers!) Has anyone experienced a similar problem? bounce_notify_owner_on_disable=yes so you should get a notice for each disable containing a copy of the triggering DSN. What does it say? Does it look legitimate? Also, what if anything do you see in Mailman's smtp-failure log? -- 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] many Subscription disabled messages after movinglist to new server
PS: I independently tested one of the offending addresses, and it bounced. So perhaps they really are bad. I looked in the bounce log on the old server, and this same address bounced many times, but bounce info got reset often. The new bounce log has many messages, largely about resetting stale bounce info, and then about bounces. Consistent with bounce processing for a list starting out with many bad addresses. Are the configuration data stored in a readable file? I could go back to the old server and find out what bounce options I used there. -Andrew On Jan 12, 2010, at 1:23 PM, Mark Sapiro wrote: Andrew Watson wrote: I recently moved a list to a new host, but retained the domain name. After many travails, and help from this list, I got my list working. After about a week of function, I am suddenly getting many Subscription disabled messages (about 10% of the 4411 subscribers, so far, but still growing as I write). It is possible that these are legitimate, and these really are bad addresses, and that in the move of the list my bounce processing options changed to be more stringent. Current they are: bounce_processing=Yes bounce_score_threshold= 5.0 bounce_info_stale_after=7 bounce_you_are_disabled_warnings=5 bounce_you_are_disabled_warnings_interval=7 bounce_unrecognized_goes_to_list_owner=no bounce_notify_owner_on_disable=yes bounce_notify_owner_on_removal=yes But it seems likely that this is bogus, and good addresses are being disabled (especially if this grows to 100% of subscribers!) Has anyone experienced a similar problem? bounce_notify_owner_on_disable=yes so you should get a notice for each disable containing a copy of the triggering DSN. What does it say? Does it look legitimate? Also, what if anything do you see in Mailman's smtp-failure log? -- 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] many Subscription disabled messages after movinglist to new server
On 1/12/2010 3:38 PM, Andrew Watson wrote: The bounce notices I get look legitimate. They typically include something like: Reason: Remote SMTP server has rejected address Diagnostic code: smtp;550 alb...@cvc.uab.es mailto:alb...@cvc.uab.es... User unknown In that case, they are probably real, legitimate bounces of bad addresses. The hard failures have probably all been disabled by now. Mailman's smtp-failure log contains many instances of lines like this (edited, vsad...@mysite.com mailto:vsad...@mysite.com is the list administrator) Jan 12 20:48:44 2010 (70977) Low level smtp error: Connection unexpectedly closed, msgid: mailman.1063.1263328366.70976.visionl...@mysite.com http://mysite.com Jan 12 20:48:45 2010 (70977) delivery to vsad...@mysite.com http://mysite.com failed with code -1: Connection unexpectedly closed There are also a few like this: Jan 12 20:02:54 2010 (70977) Low level smtp error: (48, 'Address already in use'), msgid: mailman.561.1263325634.70976.visionl...@mysite.com http://mysite.com Jan 12 20:02:54 2010 (70977) delivery to visionlist-ow...@mysite.com http://mysite.com failed with code -1: (48, 'Address already in use') These log messages commenced on Jan 12 (today). If they only started today, I don't know what the issue might be. There is a bug in the Python email library that can cause problems if you have a lot of bad addresses. See http://bugs.python.org/issue5713. But that shouldn't be the issue here. I don't have a clue what the 'Address already in use' message means. Check your MTA's logs. Also see the FAQ at http://wiki.list.org/x/-IA9. -- 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] many Subscription disabled messages after movinglist to new server
On 1/12/2010 4:07 PM, Andrew Watson wrote: Are the configuration data stored in a readable file? I could go back to the old server and find out what bounce options I used there. If you still have the installation on the old server except for web access, you can do bin/config_list -o - LISTNAME There are a couple of possibilities. If the old server was Mailman 2.1.5, that release had bounce probes enabled by default. Thus, when an address bounced, it wasn't disabled immediately, but a VERPed prob was sent and the address wasn't disabled until the probe bounced. It the MTA wasn't handling the VERPed return address properly, no-one would ever get disabled. It's also possible that bounce_info_stale_after was too short. -- 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] How to delete archives
I am trying to back up some mailman archives on a cPanel hosted website. I know your stance on cPanel, and quite understand it, but unfortunately I have to work in those constraints. I have got my provider to move all the archive files to an ftp area where I am trying to clear the message files. Archiving has now stopped working correctly - I think probably due to all the files being moved. What needs to be in the archive directory for things to work properly? I would like to provide the admin a script to enable this sort of thing to be done, but am a little lost as to the exact structure of the achive directory. Can I ask for help please? Regards David -- 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] can't display listinfo page
I recently e-mailed the list about my web server crashing and having to move to a new machine. I thought I knew what was going on, but obviously not. I started a web sever on my mail server that also has the mailman directory. Everything is on one box, so I thought this should be easy. I changed mm_cfg.py to reflect the new DEFAULT_URL_HOST = I get the following error. There currently are no publicly-advertised Mailman mailing lists on ... Is there something else I need to change? --myron = Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College my...@cs.moravian.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] can't display listinfo page
myron wrote: I changed mm_cfg.py to reflect the new DEFAULT_URL_HOST I get the following error. There currently are no publicly-advertised Mailman mailing lists on ... Is there something else I need to change? See the FAQ at http://wiki.list.org/x/mIA9. -- 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] Error Sending to newly created list
On 1/12/2010 10:28 AM, Robert Cannon wrote: Hello All, I am very new to the mailman system, I have recently taken over a client that uses this and has approx 10,000 email addresses in it. I have receive a request to create new list which I was able to successfully, and have added myself to the list and received the subscribe email. However when I send an email to the list I receive the error User unknown in local recipient table ##. All other list are working fine its just the newly created one, any help you could provide me would be great. You need to install a set of aliases for your new list. If you created the list with bin/newlist, it should have reported the required aliases. If you created the list via the web, the required aliases were emailed to mailman-ow...@... which should have been delivered to the owner of the 'mailman' site list. This assumes that the default MTA='Manual' has not been overridden in mm_cfg.py. If it has been, then whatever programmatic process that handles aliases or delivery to Mailman without aliases is not working. -- 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] How to delete archives
David Anderson wrote: What needs to be in the archive directory for things to work properly? An 'empty' list archive for a list named 'junk' looks like the following [m...@sbh16 ~]$ ls -ld mmv/archives/private/junk* drwxrwsr-x 2 mark mailman 4096 Jan 12 16:48 mmv/archives/private/junk drwxrwsr-x 2 mark mailman 4096 Jan 12 16:48 mmv/archives/private/junk.mbox [m...@sbh16 ~]$ ls -lAR mmv/archives/private/junk* mmv/archives/private/junk: total 4 -rw-rw-r-- 1 mark mailman 484 Jan 12 16:48 index.html mmv/archives/private/junk.mbox: total 0 [m...@sbh16 ~]$ i.e. two directories - archives/private/junk and archives/private/junk.mbox - both in mailman's group (owner not important) with permissions drwxrwsr-x and an index.html file archives/private/junk/index.html in mailman's group with permissions -rw-rw-r-- (contents not important, but normally a no posts yet message). I would like to provide the admin a script to enable this sort of thing to be done, but am a little lost as to the exact structure of the achive directory. Can I ask for help please? Once posts are archived, there is an archives/private/junk.mbox/junk.mbox file which is a cumulative *nix mbox containing all archived posts and a hierarchy of directories and files in archives/private/junk/ containing the pipermail archive. -- 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] many Subscription disabled messages after movinglist to new server
The old server had essentially the same bounce options as the new. It was mailman 2.1.5, and I see many probe messages in the bounce log. Maybe you are right about the VERPed probe. On Jan 12, 2010, at 4:19 PM, Mark Sapiro wrote: On 1/12/2010 4:07 PM, Andrew Watson wrote: Are the configuration data stored in a readable file? I could go back to the old server and find out what bounce options I used there. If you still have the installation on the old server except for web access, you can do bin/config_list -o - LISTNAME There are a couple of possibilities. If the old server was Mailman 2.1.5, that release had bounce probes enabled by default. Thus, when an address bounced, it wasn't disabled immediately, but a VERPed prob was sent and the address wasn't disabled until the probe bounced. It the MTA wasn't handling the VERPed return address properly, no-one would ever get disabled. It's also possible that bounce_info_stale_after was too short. -- 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] How to change configs for ALL lists?
At 12:47 PM 1/12/2010, Terri Oda wrote: Elaine Ashton wrote: Well, what concerns me is that the spammers are going at these mass subscriptions via the web interface and it may become a game of whack-a-mole banning domains and IPs. Are there any plans to make the web form subscription more of a hurdle for spammers, e.g. captcha, etc? I'm not a big believer in captcha's (advances in tech have made a lot of them trivially easy to in an automated way, making them annoying to users for little gain) but it might be worth thinking about a plug in architecture for this in mm3 in case something better does come up, or so people can enjoy their placebos... If you decide to do captcha's, please make it optional -- or offer other alternatives. I have 150 lists, and thousands of blind and visually impaired users, including myself, and captcha's are the bane of our existence! Dave -- 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] How to delete archives
David Anderson writes: I am trying to back up some mailman archives on a cPanel hosted website. I know your stance on cPanel, and quite understand it, but unfortunately I have to work in those constraints. Note that the stance on cPanel is not that we *won't* support Mailman users on cPanel, it's that we usually *can't*. The point of cPanel is to ensure that if you can do it, you can do it easily by yourself, and if you can't do it, you can't do it *at all* by yourself, and neither can we -- all we can do is tell you to get in touch with your provider. Since you've already gotten in touch with your provider, the rest *is* within the competence of Mailman-Users to advise. Except ... It would be nice if your provider's admin would join the conversation here. Have you suggested that? He should be interested. After all, it's his host that is going to be running this script! -- 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] many Subscription disabled messages after movinglist to new server
Andrew Watson The old server had essentially the same bounce options as the new. It was mailman 2.1.5, and I see many probe messages in the bounce log. Maybe you are right about the VERPed probe. If there weren't any disabling due to probe bounce received messages in the log, only sending LISTNAME list probe to messages, then the bounced probes weren't being properly returned to the list-bounces address, and members were never getting delivery disabled and never getting removed. Their scores just got incremented to threshold and were then reset when the probe was sent to start the process all over again. -- 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
