Re: [Mailman-Users] Mailman 2.1.10 has been released

2008-05-23 Thread Barry Finkel
On April 23 Mark Sapiro wrote: | I am happy to announce the release of Mailman 2.1.10. I have discovered a few problems with the release. None is a major show stopper, but the most significant so far is that I broke cmd_subscribe so that email subscribe to the -subscribe or -join address or the

[Mailman-Users] Help! Recipient list too long message is held for approval

2008-05-23 Thread webct
Hi, We are using mailman which comes with Mac OS X server 10.5. I think, I have set it up correctly for most of the part but there is one lingering issue with sending a message with other email addresses. I get Recipient list too long error message and the email is held for moderator's

Re: [Mailman-Users] Help! Recipient list too long message is held for approval

2008-05-23 Thread Knabe, Troy
On 5/23/08 8:14 AM, webct [EMAIL PROTECTED] wrote: Hi, We are using mailman which comes with Mac OS X server 10.5. I think, I have set it up correctly for most of the part but there is one lingering issue with sending a message with other email addresses. I get Recipient list too long error

[Mailman-Users] Major problems with privacy and mailman lists and harvesters

2008-05-23 Thread Steve Murphy
Hello! I'm quite concerned about what I'm seeing in mailman installations, and the amount of spam I've been getting because I participate in mailman based lists! I'm not talking about halting spam that gets submitted to the list for mailing. I'm not talking about spambots automatically joining

Re: [Mailman-Users] Major problems with privacy and mailman lists and harvesters

2008-05-23 Thread Gadi Evron
Hi Steve. Thank you for your email, it is well researched and conveys your point of view. Your points on inconsistency in protecting email addresses in the archives are interesting. Also, I am no lover of spammers. That said, can you break down your suggestions to those relevant to the

Re: [Mailman-Users] Help! Recipient list too long message is held for approval

2008-05-23 Thread Bill Christensen
The acceptable number of recipients can be adjusted at: http://list domain/mailman/admin/listname/privacy/recipient Ceiling on acceptable number of recipients for a posting. (Details for max_num_recipients) Defaults to 10 At 8:48 AM -0700 5/23/08, Knabe, Troy wrote: On 5/23/08 8:14 AM,

Re: [Mailman-Users] Major problems with privacy and mailman lists and harvesters

2008-05-23 Thread Jim Popovitch
On Fri, May 23, 2008 at 1:03 PM, Steve Murphy [EMAIL PROTECTED] wrote: Within MINUTES of my first posting on asterisk-users, I was getting spam on an email address that was brand-new. How do you know that it was your archived post that the spammers picked up on?It is also possible that the

Re: [Mailman-Users] Major problems with privacy and mailman lists andharvesters

2008-05-23 Thread Andrew Hodgson
Steve Murphy wrote: I'm quite concerned about what I'm seeing in mailman installations, and the amount of spam I've been getting because I participate in mailman based lists! What I'm concerned about is the fact that email harvesters are being given so much information. I've noticed in the

[Mailman-Users] high memory usage and long running time for mailman Python process

2008-05-23 Thread Terrence Brannon
Hello, I am running Debian/etch and the user list has a Python process which takes up 83.2% of my memory and has been running for more than 40 minutes. My suspicion is that some sort of queue of moderator messages is very large. In fact, /var/lib/mailman/ is very large... I cannot access

Re: [Mailman-Users] Major problems with privacy and mailman lists and harvesters

2008-05-23 Thread Michael Welch
Steve Murphy wrote at 10:03 AM 5/23/2008: I've noticed in the mailman-users archives, that if I view info by thread (using the mailman archives as an example,) which site is 2.1.10 based, that all email addresses are present, but with a simple obfuscation. (the @ has been changed to at .) I

Re: [Mailman-Users] Major problems with privacy and mailman lists and harvesters

2008-05-23 Thread Bill Christensen
When creating archives for one of the lists I run (until recently with another listserv software) I wrote a relatively simple find/replace grep which replaces the domain names so that email addresses become [EMAIL PROTECTED] In this case, the list itself is by invitation only but the archives