Mailman 3 December 2003 - Mailman-Developers

Re: [Mailman-checkins] mailman/messages/fr/LC_MESSAGES mailman.po, 2.64, 2.65
by Barry Warsaw 24 Dec '03

24 Dec '03

On Tue, 2003-12-23 at 18:22, p_george(a)users.sourceforge.net wrote: > Update of /cvsroot/mailman/mailman/messages/fr/LC_MESSAGES > In directory sc8-pr-cvs1:/tmp/cvs-serv12117/messages/fr/LC_MESSAGES > > Modified Files: > mailman.po > Log Message: > Christmas updates from p.george Don't forget to backport these changes to the Release_2_1-maint branch, or they won't make it into Mailman 2.1.4! -Barry

1 0

SourceForge donations for the GNU Mailman project
by Barry Warsaw 23 Dec '03

23 Dec '03

SourceForge recently instituted a donation system for projects and users, whereby you can donate some money to a PayPal account to show your appreciation for the free and open source projects you use. Donations to projects require opt-in from all the project's admins. Jeremy and I have both opted-in to the donation system for the GNU Mailman project. I have set the donations email address to the Python Software Foundation's PayPal account. This needn't be set in stone, but we had to pick an address to turn this on and the PSF seemed like a reasonable choice. Note that the Python project is accepting donations for the PSF as well. GNU Mailman remains free, in both the monetary and liberty senses of the word. I personally feel that the good will, help to others, insights, patches, bug fixes, and general good community that you already donate is enough reward. If you feel like making a monetary contribution as well, please know that the PSF is a US public charity under section 501(c)(3) of the IRS code. See http://www.python.org/psf for details. If you have comments or feedback about our choice for the recipient of donations, or about whether we should be taking donations at all, please email me directly. Cheers, and happy holidays, -Barry

2 1

AOL 9.0 categorizing mailman verification messages as SPAM
by Ken Stillson 20 Dec '03

20 Dec '03

Hey folks, I just got off the phone with someone in the postmaster group at AOL... I was calling them because recently all the subscription verification messages being generated from my lists are getting categorized a SPAM for AOL 9.0 users, and most of them aren't thinking to check their SPAM folders. The fellow mentioned that long random-looking alpha-numeric strings in the subject line are one of the things that triggers their filter. Are folks here aware of this issue? AOL suggested moving the verification "cookie" from the subject line to the contents of the message Realizing that mailman can't be specialized to meet every quirk of every ISP; but AOL isn't just any ISP, for me anyway, some 80% of my subscription requests for my several dozen lists come from there. Any thoughts? Thanks! - Ken Stillson System Administrator Point0.net

2 1

Re: [Mailman-checkins] mailman/Mailman/Handlers CookHeaders.py, 2.33.2.3, 2.33.2.4
by Tokio Kikuchi 19 Dec '03

19 Dec '03

Hi Barry, I think this one is not necessary if the encoding is non-ascii. Any special characters should be properly escaped. bwarsaw(a)users.sourceforge.net wrote: > Update of /cvsroot/mailman/mailman/Mailman/Handlers > In directory sc8-pr-cvs1:/tmp/cvs-serv26065 > > Modified Files: > Tag: Release_2_1-maint > CookHeaders.py > Log Message: > process(): Quote the description when adding it to the List-ID header, > in case there are any special characters (in the RFC 2822) in the > description. > > > Index: CookHeaders.py > =================================================================== > RCS file: /cvsroot/mailman/mailman/Mailman/Handlers/CookHeaders.py,v > retrieving revision 2.33.2.3 > retrieving revision 2.33.2.4 > diff -u -d -r2.33.2.3 -r2.33.2.4 > --- CookHeaders.py 22 Sep 2003 02:37:51 -0000 2.33.2.3 > +++ CookHeaders.py 13 Dec 2003 23:25:42 -0000 2.33.2.4 > @@ -168,7 +168,7 @@ > listid = '<%s.%s>' % (mlist.internal_name(), mlist.host_name) > if mlist.description: > # Make sure description is properly i18n'd > - listid_h = uheader(mlist, mlist.description, 'List-Id') > + listid_h = uheader(mlist, u'"' + mlist.description + u'"', 'List-Id') > listid_h.append(listid, 'us-ascii') > else: > # For wrapping > > > > _______________________________________________ > Mailman-checkins mailing list > Mailman-checkins(a)python.org > Unsubscribe: http://mail.python.org/mailman/options/mailman-checkins/tkikuchi%40is.kochi… > > -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/

2 5

Mailman consultant needed
by ljacobs 19 Dec '03

19 Dec '03

If someone who has configured Mailman 2.1.X on FreeBSD and RH Linux with Postfix as the MTA would be interested in an installation and configuration project for Mandala Designs, please contact me. I am experienced with some aspects of Mailman and have a brick wall with a recent development and problem. Thanks. ________________________________________________________________ Sent via the WebMessaging system at mandala-designs.com --- [This E-mail scanned for viruses by Declude Virus]

1 0

"Turing test" to reject email harvesting bots
by Bernhard Kuemel 18 Dec '03

18 Dec '03

Hi mailman-users! I wrote a "turing test" that keeps e.g. email harvesting bots off: http://bksys.at/bernhard/img/turing.php?who=agent%20smith source: http://bksys.at/bernhard/img/turing.txt Since it is trivial to collect "high quality" email addresses form mailman lists even if they are only available to the members I'd like such a turing test be in mailman. Either before the "view subscribers" page or as part of the subscription process. http://www.google.com/search?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=%22Click+here+fo… yields 24000 hits. http://www.google.com/search?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=%22The+subscribe… yields 40000 hits. The text image generation is a little CPU intensive (2 s on a 1800 MHz P4) so some measures may be desirable to prevent DoS attacks by flood requests of the images. E.g. Put the test after receival of the subscription email cookie was returned. This test may disable users of non graphical web browers or email only subscribers to subscribe. Bernhard -- Webspace; Low end Serverhousing ab 15 e, etc.: http://www.bksys.at Linux Admin/Programmierer: http://bksys.at/bernhard/services.html

10 35

Bug in subscribe program
by Michael Stucki 14 Dec '03

14 Dec '03

Dear all, I have found a bug which I can reproduce with Mailman 2.1.2 on Debian Woody (according to the NEWS file, it's still not fixed in Mailman 2.1.3). When a user enters the subscription web page, enters his data _and_ a passwort that contains German umlauts (ä ö ü), he will get the following error message: === Bug in Mailman version 2.1.2 We're sorry, we hit a bug! [...] Traceback: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 96, in main process_form(mlist, doc, cgidata, language) File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 176, in process_form mlist.AddMember(userdesc, remote) File "/usr/lib/mailman/Mailman/MailList.py", line 806, in AddMember cookie = Pending.new(Pending.SUBSCRIPTION, userdesc) File "/usr/lib/mailman/Mailman/Pending.py", line 80, in new hashfood = str(now) + str(n) + str(content) File "/usr/lib/mailman/Mailman/UserDesc.py", line 56, in __repr__ return '' % ( UnicodeError: ASCII decoding error: ordinal not in range(128) === I have posted a copy of this page where you can see all further information on http://www.mstucki.net/files/misc/mailman-bug.html Kind regards - michael

2 2

List-Id header special ','
by Jan Kratochvil 14 Dec '03

14 Dec '03

Hi, Mailman currently permits any list 'description' string. It is later inserted to 'List-Id' header such as: List-Id: Patches for autoconf, the GNU build system <autoconf-patches.gnu.org> This header does not comply with RFC2919 and RFC822/RFC2822 as it uses a forbidden special ','. 'description' is allowed to be only 'phrase' of RFC822. It would be needed to quote it: List-Id: "Patches for autoconf, the GNU build system" <autoconf-patches.gnu.org> Please either forbid 'special' characters such as ',' or quote the header if such offending character is found. Regards, Lace

2 1

list pickle details
by Aaron Bennett 14 Dec '03

14 Dec '03

Hi, I'm working on writing a mailman statistics program -- simple stuff, and I'm sure there are better ones out there then the one I'm writing, but I'm also teaching myself python at the same time. My first approach is to unpickle each list's configuration pickle into an array of <whatever the heck they are>. Does anyone have either a concise explanation of what's in each list object when it gets unpickled, or a link to some documentation about how mailman's internals work? Also appreciated would be pointers as to where in the mailman source code I should start my reading. thanks so much, and of course I'll release my stats program when it's done if anyone is interested in it, Aaron Bennett -- Aaron Bennett UNIX Administrator Franklin W. Olin College of Engineering

2 1

How to creating new cgi-bin scripts
by Scott C. Villinski 14 Dec '03

14 Dec '03

I've looked (in the places that I think I should) to find an answer. On my Mailman 2.1.3 server, I want to create a copy of the roster.py file but instead have it return an XML document. I copied the roster.py file to: xml-roster.py (in $prefix/Mailman/Cgi). What do I need to do to make it compile and end up in the $prefix/cgi-bin directory? I restarted mailman on my server. Are the scripts in the cgi-bin directory hardcoded somehow? Any pointers would be great. Also if this isn't the right list, let me know. I did post to the mailman-users list, but got no bites. Thanks, Scott

2 1