Mailman 3 May 2001 - Mailman-Developers

Re: [Mailman-Developers] Mailman password and administrative reminders
by Dan Mick 14 Aug '03

14 Aug '03

? This very message came to me with the following header: Errors-To: mailman-developers-admin(a)python.org All my bounces come to the list admin address, set in the admin webpage, in the second field of General Options. Do you have that set to something, and bounces still come to root? > 2. Bounces are sent to the poor postmaster instead of a -admin address. > I'm not entirely certain, but I think an Errors-To: header or something > like that in all Mailman messages might allow one to distribute that load > somewhat.

8 11

site-wide list configuration...
by Chuq Von Rospach 12 Jun '01

12 Jun '01

Just as a bit of an FYI -- I've mentioned in the past that I'd like the ability to "lock down" certain list configuration options based on site-wide standard. Having this feature has become more interesting to me, since I just has a 'situation' where it would have been really useful. I had a list admin decide he wanted to change reply-to to the list. This, despite being told not to change things. So he did. And it got involved in a situation where stuff was posted to the list (by me, in fact) that shouldn't have been because the list was configured different than everything else on the system. And that led to the "why can't we have this?" fight, and it led to a private argument with the list admin (who actually changed it twice), and all sorts of unhappiness. And one of his arguments, of course, was "if you don't want this changed, why do the pages let me"? Don't worry, my hair will grow back. Well, maybe. But take this as a real-world case where splitting out content admin from list admin from site admin and allowing the folks higher up in the hierarchy to delegate or freeze what sub-admins can do. Because while it's nice to think everyone will play nice and follow instructions, in the real world, it doesn't always happen. -- Chuq Von Rospach, Internet Gnome <http://www.chuqui.com> [<chuqui(a)plaidworks.com> = <me(a)chuqui.com> = <chuq(a)apple.com>] Yes, yes, I've finally finished my home page. Lucky you. It's a thankless job, but I've got a lot of Karma to burn off.

2 1

minor qrunner bug.
by Chuq Von Rospach 02 Jun '01

02 Jun '01

Just noticed a minor bug in qrunner. when qrunner starts up, it opens the log files, and leaves them open. this is fine -- except when the logs get rolled and restarted. When you move the logs off and gzip them for storage, qrunner continues writing to the (now unlinked) old files, not the new, zeroed ones. So all of the qrunner stat and errror and whatever data from the time you roll the logs until that instance of qrunner exits is gone (which, if you've modified qrunner lifetime values, can become significant on a busy system) Since mailman isn't oding much log processing, not a big deal. but for sites that are (for instance) charging for list usage, or sites that have implemented reporting, there are potential holes in the data, and if they're busy so they have extended qrunner times, significant holes. while open/write/close is expensive, given all of the other stuff qrunner's doing and the relative lack of logging, I don't think it's significant. Alternatively, it can notice the files have been moved/zeroed, or perhaps accept a HUP like syslog... -- Chuq Von Rospach, Internet Gnome <http://www.chuqui.com> [<chuqui(a)plaidworks.com> = <me(a)chuqui.com> = <chuq(a)apple.com>] Yes, yes, I've finally finished my home page. Lucky you. I'm out of my mind, but feel free to leave a message...

3 3

subscriber profiler patch for mailman-2.0.5
by Swee Heng 01 Jun '01

01 Jun '01

hi folks, i've written a patch to mailman-2.0.5 that lets it handle subscribers' profiles. (is this the "member profiles" feature on the wishlist?) the patch is available at: http://www.srikant.org/~sh/src/mmprofiler/mm-2.0.5-prof-0.7.gz a screenshot of it in action is at: http://www.srikant.org/~sh/src/mmprofiler/screenshot.jpg this is my first serious attempt at python. so please be warned. :) feel free to comment. swee heng ====================================================================== Brief Documentation ^^^^^^^^^^^^^^^^^^^ how to install it: ^^^^^^^^^^^^^^^^^^ 1. "patch -p0 <" the patch to mailman-2.0.5 2. do the usual "./configure; make; make install" this will create Mailman/Cgi/profile.py, cgi-bin/profile and three templates files (prof_login.html, prof_list.html, prof_user.html) in templates/. it will also modify Mailman/Cgi/edithtml.py so that list admins can change the look of the templates. how to use it: ^^^^^^^^^^^^^^ for currently existing lists, you need to copy the template files: cp templates/prof_* lists/the-existing-list/ for new lists, nothing needs to be done. finally, visit the URL: http://your.domain/mailman/profile/view/name-of-list notes: ^^^^^^ 1. profile information is made available to list members and admins when private_roster == 0 or 1. it is made available only to list admins when private_roster == 2. profile information is not available otherwise. 2. the database is really just a collection of pickles, one for each subscriber, stored in lists/name-of-list/profiles/. 3. i've used a whole slew of replacement MM tags, but they all look like <MM-P-foobar> or <MM-P--privatefoobar>. they won't pollute other tags.

2 2

Skinning Mailman (how to add a customer UI in five minutes or less...)
by Chuq Von Rospach 01 Jun '01

01 Jun '01

I've got this running now, so I figured I'd toss out a cookbook recipe on it while it's fresh. I've always hacked Mailman to install a custom interface on it so it matches the rest of my sites (for instance, see www.hockeyfanz.com/mailman/listinfo). The downside to this is that every time a new release comes out, you have to repatch all your changes. This makes it more work to upgrade than it should be, so I've been keeping an eye out for a better way to do this (and it gets worse -- on one of my sites, I also have a web board that needs custom patching, my mhonarc rcfiles that need patching, and the standard files that need tweaking every time the UI or graphics get revamped, and I'm not always in control of when they get redone...) I finally found a tool that takes care of this for me -- it's called mod_layout (www.tangent.org), and it's an apache module, so this is apache specific. If you run your apache with DSO (and if you don't, you're crazy...), installation is trivial. Download the thing, unpack it, then run "make" and "make install". It uses APXS to handle everything. To get it running, I added these lines to the httpd.conf. In my case, they're in the <virtualhost> declaration (it supports all fo the apache stuff, so it recognizes and honors virtual hosts, directories, etc... Very flexible beast) # stuff to wire in mod_layout LayoutMerge On LayoutFooter /home/httpd/html/footer.incl LayoutHeader /home/httpd/html/header.incl (I also have some lines causing it to NOT tweak files in directories I want left alone -- it can be configured on a file or directory basis, host basis, or systemwide) Then create the header and footer, and restart apache. What mod_layout does (as configured here) is put itself in the middle of everything, and when it sees the <BODY> declaration, it inserts the header. And when it sees </BODY> it inserts the footer before it. For the CGI or html page, it's completely transparent, and you don't have to worry about screwing up CSS or javascript, and it leaves cookies alone. It also doesn't affect your HTML, since it comes after the <BODY> so it can't interrupt tables or other location sensitive things. Very nice hack, IMHO, and allows you to wrap an interface around mailman quite nicely -- as well as most other CGI-based stuff that doesn't support templating. And even nicer, IMHO, is that if you need to change things, you change the included files -- and it magically propogates, no need to even restart apache. This gives me control over almost all of Mailman (and, hint hint) -- hopefully Barry will add the configuration for the rest down the road. One is that some of the text-box colors are hard-coded (see, for instance, /mailman/admin/listname/general/. It'd be nice (and it seems to be easy to do) to turn those into globals that can be set in mm_cfg.py instead of requiring someone to whack all of the source files they're sprinkled in. The other key one for me are some of the admin messages (Mailman/Handlers/Hold.py). I've modified some of the messages for various reasons, and it'd be nice if I could simply override their definitions in the mm_cfg.py file And the third place I've made custom changes are in some of the list templates (most radically templates/listinfo.html) -- but that's why they're template; you simply keep a copy somewhere and watch out for additions to the updated copy... It took me about three days and a couple of exchanges with the author of mod_layout to get it going the way I wanted (the documentation is still being fleshed out), but it's a nice improvement to the old way of doing things -- and since I know others build custom skins around their installations, I'd thought I'd pass this one along. If you want to see a version of mailman with mod_layout, see www.plaidworks.com. My mailman set up the old way is www.hockeyfanz.com (for now. I'll be working to move this to all my stuff over time...) Chuq

3 4

FR catalog!
by Ousmane Wilane 31 May '01

31 May '01

Hi, A french catalog is available at http://mint.sn/Mailman/mailman.po.gz. We have also made available a test setup (2.1a2) with a Mailman-fr list supporting es, fr. Japanese will be added in no time. Thanks in advance for helps correcting the translations. Cheers. -- -- Ousmane Wilane -- "The best laid plans sometimes go awry..."

1 0

Re: [Mailman-checkins] CVS: mailman/messages Makefile.in,2.1,2.2
by Thomas Wouters 29 May '01

29 May '01

On Tue, May 29, 2001 at 05:06:49AM -0700, Thomas Wouters wrote: > Re-BSDify the Makefiles, by not expecting make to expand '{eggs,ham}' in > globs. (BSD 'make' does not, GNU make does.) I'm sure there is a more > satisfying way to do this, but in this case, with only two alternatives in > only two cases, just writing them out was the way of least resistance. Ugh. I now see that there are a lot more things BSD make barfs over: GNU make: mailman/messages$ gmake es/LC_MESSAGES/mailman.mo [ pygettext and other stuff snipped ] Generating binary catalog msgfmt -o es/LC_MESSAGES/mailman.mo es/LC_MESSAGES/mailman.po BSD make: mailman/messages$ make es/LC_MESSAGES/mailman.mo msgfmt -o es/LC_MESSAGES/mailman.po es/LC_MESSAGES/mailman.mo es/LC_MESSAGES/mailman.mo:1: parse error es/LC_MESSAGES/mailman.mo:2: keyword "e" unknown es/LC_MESSAGES/mailman.mo:4: keyword "W" unknown Apparently, GNU make and BSD make switch the meaning of $@ and $< in: msgfmt -o $@ $< And there's more, there, too. As usual for Makefile/make bugs, they're hard to reproduce, depending as they are on the timestamps of seemingly totally irrelevant files :) I think it's safe to say that BSD make doesn't grok the '%/LC_MESSAGES/*' construct, though. I don't have a good GNU/BSD make resource at hand to help me through the differences; if anyone sees such a resource online, please let me know ;) In the mean time, Barry, if this isn't fixed before an almost-real release, we'll either have to ship .po files, or insist on GNU make (which is available almost everywhere, even on BSD systems, though usually as 'gmake' there.) The installation procedure works with BSD make now that I regenerated the .po files with GNU make. -- Thomas Wouters <thomas(a)xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!

3 5

cookie
by Angela 29 May '01

29 May '01

I want create an application where a user called a cookie, someone know where I can find more information how to create a cookie Thank you Angela Nesticò

1 0

ANNOUNCE Mailman 2.0.5
by barry＠digicool.com 26 May '01

26 May '01

Folks, I've just released Mailman 2.0.5 which fixes a problem with stale lock files that can occur under certain situations when the user hits the `Stop' button on their browser. These stale lock files can cause mailing lists to be inaccessible for long periods of time (until the stale lock file times out or is manually removed). As usual, I'm releasing this as both a complete tarball and as a patch against Mailman 2.0.4. You /must/ update your source to 2.0.4 before applying the 2.0.5 patch. Since the patch is small, I'm including it in this message. To apply, cd into your 2.0.5 source tree and apply it like so: % patch -p0 < mailman-2.0.4-2.0.5.txt Currently both http://mailman.sourceforge.net and http://www.list.org are updated, and I expect the gnu.org site to be updated soon as well. The release information on SF is at http://sourceforge.net/project/shownotes.php?release_id=31693 See also http://www.gnu.org/software/mailman http://www.list.org http://mailman.sourceforge.net My thanks to those of you who gave the 2.0.5 pre-release a try! Enjoy, -Barry Index: NEWS =================================================================== RCS file: /cvsroot/mailman/mailman/NEWS,v retrieving revision 1.25.2.5 retrieving revision 1.25.2.6 diff -u -r1.25.2.5 -r1.25.2.6 --- NEWS 2001/04/18 10:45:54 1.25.2.5 +++ NEWS 2001/05/03 21:06:56 1.25.2.6 @@ -4,6 +4,13 @@ Here is a history of user visible changes to Mailman. +2.0.5 (04-May-2001) + + Fix a lock stagnation problem that can result when the user hits + the `stop' button on their browser during a write operation that + can take a long time (e.g. hitting the membership management admin + page). + 2.0.4 (18-Apr-2001) Python 2.1 compatibility release. There were a few questionable Index: Mailman/Version.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Version.py,v retrieving revision 1.20.2.4 retrieving revision 1.20.2.5 diff -u -r1.20.2.4 -r1.20.2.5 --- Mailman/Version.py 2001/04/18 04:43:29 1.20.2.4 +++ Mailman/Version.py 2001/05/03 20:58:19 1.20.2.5 @@ -15,7 +15,7 @@ # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. # Mailman version -VERSION = "2.0.4" +VERSION = "2.0.5" # And as a hex number in the manner of PY_VERSION_HEX ALPHA = 0xa @@ -27,7 +27,7 @@ MAJOR_REV = 2 MINOR_REV = 0 -MICRO_REV = 4 +MICRO_REV = 5 REL_LEVEL = FINAL # at most 15 beta releases! REL_SERIAL = 0 Index: Mailman/Cgi/admin.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Cgi/admin.py,v retrieving revision 1.82.2.2 retrieving revision 1.82.2.3 diff -u -r1.82.2.2 -r1.82.2.3 --- Mailman/Cgi/admin.py 2001/01/03 16:47:47 1.82.2.2 +++ Mailman/Cgi/admin.py 2001/05/03 21:03:48 1.82.2.3 @@ -18,11 +18,13 @@ """ +import sys import os import cgi import string import types import rfc822 +import signal from Mailman import Utils from Mailman import MailList @@ -63,53 +65,86 @@ # get the list object listname = string.lower(parts[0]) try: - mlist = MailList.MailList(listname) + mlist = MailList.MailList(listname, lock=0) except Errors.MMListError, e: FormatAdminOverview('No such list <em>%s</em>' % listname) syslog('error', 'Someone tried to access the admin interface for a ' 'non-existent list: %s' % listname) return + + if len(parts) == 1: + category = 'general' + category_suffix = '' + else: + category = parts[1] + category_suffix = category + + # If the user is not authenticated, we're done. + cgidata = cgi.FieldStorage(keep_blank_values=1) try: - if len(parts) == 1: - category = 'general' - category_suffix = '' - else: - category = parts[1] - category_suffix = category - - # If the user is not authenticated, we're done. - cgidata = cgi.FieldStorage(keep_blank_values=1) - try: - Auth.authenticate(mlist, cgidata) - except Auth.NotLoggedInError, e: - Auth.loginpage(mlist, 'admin', e.message) - return - - # Is this a log-out request? - if category == 'logout': - print mlist.ZapCookie('admin') - Auth.loginpage(mlist, 'admin', frontpage=1) - return - - if category not in map(lambda x: x[0], CATEGORIES): - category = 'general' - - # is the request for variable details? - varhelp = None - if cgidata.has_key('VARHELP'): - varhelp = cgidata['VARHELP'].value - elif cgidata.has_key('request_login') and \ - os.environ.get('QUERY_STRING'): - # POST methods, even if their actions have a query string, don't - # get put into FieldStorage's keys :-( - qs = cgi.parse_qs(os.environ['QUERY_STRING']).get('VARHELP') - if qs and type(qs) == types.ListType: - varhelp = qs[0] - if varhelp: - FormatOptionHelp(doc, varhelp, mlist) - print doc.Format(bgcolor="#ffffff") - return + Auth.authenticate(mlist, cgidata) + except Auth.NotLoggedInError, e: + Auth.loginpage(mlist, 'admin', e.message) + return + + # Is this a log-out request? + if category == 'logout': + print mlist.ZapCookie('admin') + Auth.loginpage(mlist, 'admin', frontpage=1) + return + + if category not in map(lambda x: x[0], CATEGORIES): + category = 'general' + # is the request for variable details? + varhelp = None + if cgidata.has_key('VARHELP'): + varhelp = cgidata['VARHELP'].value + elif cgidata.has_key('request_login') and \ + os.environ.get('QUERY_STRING'): + # POST methods, even if their actions have a query string, don't + # get put into FieldStorage's keys :-( + qs = cgi.parse_qs(os.environ['QUERY_STRING']).get('VARHELP') + if qs and type(qs) == types.ListType: + varhelp = qs[0] + if varhelp: + FormatOptionHelp(doc, varhelp, mlist) + print doc.Format(bgcolor="#ffffff") + return + + # From this point on, the MailList object must be locked. However, we + # must release the lock no matter how we exit. try/finally isn't + # enough, because of this scenario: user hits the admin page which may + # take a long time to render; user gets bored and hits the browser's + # STOP button; browser shuts down socket; server tries to write to + # broken socket and gets a SIGPIPE. Under Apache 1.3/mod_cgi, Apache + # catches this SIGPIPE (I presume it is buffering output from the cgi + # script), then turns around and SIGTERMs the cgi process. Apache + # waits three seconds and then SIGKILLs the cgi process. We /must/ + # catch the SIGTERM and do the most reasonable thing we can in as + # short a time period as possible. If we get the SIGKILL we're + # screwed (because its uncatchable and we'll have no opportunity to + # clean up after ourselves). + # + # This signal handler catches the SIGTERM and unlocks the list. The + # effect of this is that the changes made to the MailList object will + # be aborted, which seems like the only sensible semantics. + # + # BAW: This may not be portable to other web servers or cgi execution + # models. + def sigterm_handler(signum, frame, mlist=mlist): + # Make sure the list gets unlocked... + mlist.Unlock() + # ...and ensure we exit, otherwise race conditions could cause us to + # enter MailList.Save() while we're in the unlocked state, and that + # could be bad! + sys.exit(0) + + mlist.Lock() + try: + # Install the emergency shutdown signal handler + signal.signal(signal.SIGTERM, sigterm_handler) + if cgidata.has_key('bounce_matching_headers'): pairs = mlist.parse_matching_header_opt() @@ -135,8 +170,12 @@ FormatConfiguration(doc, mlist, category, category_suffix, cgidata) print doc.Format(bgcolor="#ffffff") - finally: mlist.Save() + finally: + # Now be sure to unlock the list. It's okay if we get a signal here + # because essentially, the signal handler will do the same thing. And + # unlocking is unconditional, so it's not an error if we unlock while + # we're already unlocked. mlist.Unlock() Index: Mailman/Cgi/admindb.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Cgi/admindb.py,v retrieving revision 1.36.2.1 retrieving revision 1.36.2.4 diff -u -r1.36.2.1 -r1.36.2.4 --- Mailman/Cgi/admindb.py 2001/03/03 06:02:01 1.36.2.1 +++ Mailman/Cgi/admindb.py 2001/05/04 15:54:23 1.36.2.4 @@ -16,10 +16,12 @@ """Produce and process the pending-approval items for a list.""" +import sys import os import string import types import cgi +import signal from errno import ENOENT from Mailman import mm_cfg @@ -62,7 +64,7 @@ return # now that we have the list name, create the list object try: - mlist = MailList.MailList(listname) + mlist = MailList.MailList(listname, lock=0) except Errors.MMListError, e: handle_no_list(doc, 'No such list <em>%s</em><p>' % listname) syslog('error', 'No such list "%s": %s\n' % (listname, e)) @@ -71,14 +73,34 @@ # now we must authorize the user to view this page, and if they are, to # handle both the printing of the current outstanding requests, and the # selected actions + cgidata = cgi.FieldStorage() try: - cgidata = cgi.FieldStorage() - try: - Auth.authenticate(mlist, cgidata) - except Auth.NotLoggedInError, e: - Auth.loginpage(mlist, 'admindb', e.message) - return + Auth.authenticate(mlist, cgidata) + except Auth.NotLoggedInError, e: + Auth.loginpage(mlist, 'admindb', e.message) + return + + # We need a signal handler to catch the SIGTERM that can come from Apache + # when the user hits the browser's STOP button. See the comment in + # admin.py for details. + # + # BAW: Strictly speaking, the list should not need to be locked just to + # read the request database. However the request database asserts that + # the list is locked in order to load it and it's not worth complicating + # that logic. + def sigterm_handler(signum, frame, mlist=mlist): + # Make sure the list gets unlocked... + mlist.Unlock() + # ...and ensure we exit, otherwise race conditions could cause us to + # enter MailList.Save() while we're in the unlocked state, and that + # could be bad! + sys.exit(0) + mlist.Lock() + try: + # Install the emergency shutdown signal handler + signal.signal(signal.SIGTERM, sigterm_handler) + # If this is a form submission, then we'll process the requests and # print the results. otherwise (there are no keys in the form), we'll # print out the list of pending requests @@ -91,8 +113,8 @@ PrintRequests(mlist, doc) text = doc.Format(bgcolor="#ffffff") print text - finally: mlist.Save() + finally: mlist.Unlock() Index: Mailman/Cgi/handle_opts.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Cgi/handle_opts.py,v retrieving revision 1.30 retrieving revision 1.30.2.2 diff -u -r1.30 -r1.30.2.2 --- Mailman/Cgi/handle_opts.py 2000/11/09 16:19:03 1.30 +++ Mailman/Cgi/handle_opts.py 2001/05/03 21:05:06 1.30.2.2 @@ -1,4 +1,4 @@ -# Copyright (C) 1998,1999,2000 by the Free Software Foundation, Inc. +# Copyright (C) 1998,1999,2000,2001 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License @@ -20,6 +20,7 @@ import os import string import cgi +import signal from Mailman import mm_cfg from Mailman import Utils @@ -61,7 +62,7 @@ user = parts[1] try: - mlist = MailList.MailList(listname) + mlist = MailList.MailList(listname, lock=0) except Errors.MMListError, e: doc.AddItem(Header(2, "Error")) doc.AddItem(Bold('No such list <em>%s</em>' % listname)) @@ -69,10 +70,30 @@ syslog('error', 'No such list "%s": %s\n' % (listname, e)) return + # We need a signal handler to catch the SIGTERM that can come from Apache + # when the user hits the browser's STOP button. See the comment in + # admin.py for details. + # + # BAW: Strictly speaking, the list should not need to be locked just to + # read the request database. However the request database asserts that + # the list is locked in order to load it and it's not worth complicating + # that logic. + def sigterm_handler(signum, frame, mlist=mlist): + # Make sure the list gets unlocked... + mlist.Unlock() + # ...and ensure we exit, otherwise race conditions could cause us to + # enter MailList.Save() while we're in the unlocked state, and that + # could be bad! + sys.exit(0) + + mlist.Lock() try: + # Install the emergency shutdown signal handler + signal.signal(signal.SIGTERM, sigterm_handler) + process_form(mlist, user, doc) - finally: mlist.Save() + finally: mlist.Unlock() Index: Mailman/Cgi/subscribe.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Cgi/subscribe.py,v retrieving revision 1.29 retrieving revision 1.29.2.1 diff -u -r1.29 -r1.29.2.1 --- Mailman/Cgi/subscribe.py 2000/09/29 00:05:05 1.29 +++ Mailman/Cgi/subscribe.py 2001/05/03 21:05:43 1.29.2.1 @@ -1,4 +1,4 @@ -# Copyright (C) 1998,1999,2000 by the Free Software Foundation, Inc. +# Copyright (C) 1998,1999,2000,2001 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License @@ -20,6 +20,7 @@ import os import string import cgi +import signal from Mailman import Utils from Mailman import MailList @@ -41,18 +42,38 @@ listname = string.lower(parts[0]) try: - mlist = MailList.MailList(listname) - mlist.IsListInitialized() + mlist = MailList.MailList(listname, lock=0) except Errors.MMListError, e: doc.AddItem(Header(2, "Error")) doc.AddItem(Bold('No such list <em>%s</em>' % listname)) print doc.Format(bgcolor="#ffffff") syslog('error', 'No such list "%s": %s\n' % (listname, e)) return + + # We need a signal handler to catch the SIGTERM that can come from Apache + # when the user hits the browser's STOP button. See the comment in + # admin.py for details. + # + # BAW: Strictly speaking, the list should not need to be locked just to + # read the request database. However the request database asserts that + # the list is locked in order to load it and it's not worth complicating + # that logic. + def sigterm_handler(signum, frame, mlist=mlist): + # Make sure the list gets unlocked... + mlist.Unlock() + # ...and ensure we exit, otherwise race conditions could cause us to + # enter MailList.Save() while we're in the unlocked state, and that + # could be bad! + sys.exit(0) + + mlist.Lock() try: + # Install the emergency shutdown signal handler + signal.signal(signal.SIGTERM, sigterm_handler) + process_form(mlist, doc) - finally: mlist.Save() + finally: mlist.Unlock() Index: admin/www/download.ht =================================================================== RCS file: /cvsroot/mailman/mailman/admin/www/download.ht,v retrieving revision 1.5.2.5 retrieving revision 1.5.2.6 diff -u -r1.5.2.5 -r1.5.2.6 --- admin/www/download.ht 2001/04/18 10:44:14 1.5.2.5 +++ admin/www/download.ht 2001/05/03 21:09:36 1.5.2.6 @@ -65,9 +65,9 @@ <h3>Downloading</h3> <p>Version -(<!-VERSION--->2.0.4<!-VERSION--->, +(<!-VERSION--->2.0.5<!-VERSION--->, released on -<!-DATE--->Apr 18 2001<!-DATE--->) +<!-DATE--->May 4 2001<!-DATE--->) is the current GNU release. It is available from the following mirror sites: <ul> Index: admin/www/download.html =================================================================== RCS file: /cvsroot/mailman/mailman/admin/www/download.html,v retrieving revision 1.6.2.7 retrieving revision 1.6.2.8 diff -u -r1.6.2.7 -r1.6.2.8 --- admin/www/download.html 2001/04/18 10:44:14 1.6.2.7 +++ admin/www/download.html 2001/05/03 21:09:36 1.6.2.8 @@ -1,6 +1,6 @@ <HTML>  - +   2.0.4<!-VERSION--->, +(<!-VERSION--->2.0.5<!-VERSION--->, released on -<!-DATE--->Apr 18 2001<!-DATE--->) +<!-DATE--->May 4 2001<!-DATE--->) is the current GNU release. It is available from the following mirror sites: <ul>

5 10

forwarded message from noreply@sourceforge.net
by barry＠digicool.com 25 May '01

25 May '01

Looks like it might be a while... -Barry

1 0

CVS access problem
by Juan Carlos Rey Anaya 25 May '01

25 May '01

Has anybody noted anything strange accesing CVS? [jcrey@joker mailman]$ cvs -d:pserver:anonymous@cvs.mailman.sourceforge.net:/cvsroot/mailman login CVS password: cvs login: authorization failed: server cvs.mailman.sourceforge.net rejected access :-( -- ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey(a)uma.es) | | Servicio Central de informática | | Universidad de Málaga - España | #----------------------------------------------#

2 1

Feature request: regexp for posters
by Pavel Roskin 25 May '01

25 May '01

Hello! I'm administering two mailing lists (mc(a)gnome.org and mc-devel(a)gnome.org) running Mailman 2.0.5. In order to stop spam, the messages from non-members are held for approval. Unfortunately, sometimes a message gets crossposted to a another list on a different site. Then we have a wave of posts from non-members. I want to accept messages from certain domains without approval. While including the mailing list domain (gnome.org) would be risky (some spammers use the victim's address in From:), other domains should be safe. I would like to be able to use regular expressions in the "poster" list, for example: .*(a)suse.com .*(a)ximian.com .*@.*mit.edu and so on. From what I see in the sources of Mailman 2.0.5, regular expressions are not used when the address is matched against the poster list. Would it be possible to use regular expressions in the future versions of Mailman? -- Regards, Pavel Roskin

1 0

Post of white paper
by Michael Neel 23 May '01

23 May '01

Hi all, I'm new to the mailman project and have email Barry briefly on some ideas I have for 3.0 mailman. I've added a white paper under MailmanThreePointOh on the zope site for your feedback. I look forward to working with you all! Mike -- Michael C. Neel Senior Programmer/Analyst Mediapulse, Inc. The Pulse of Your eBusiness Phn: 865.482.4455 x30 Fax: 4465 <http://www.mediapulse.com/>

1 0

Mailman install from CVS bug
by Juan Carlos Rey Anaya 22 May '01

22 May '01

I have been experiencing a bug when I have tried to install mailman from CVS: When I execute './configure': [snip] creating Mailman/Queue/Makefile creating Mailman/MTA/Makefile sed: can't read ./Mailman/MTA/Makefile.in: No such file or directory creating templates/Makefile creating cron/Makefile creating filters/Makefile creating scripts/Makefile creating messages/Makefile sed: can't read ./messages/Makefile.in: No such file or directory creating cron/crontab.in creating Makefile and then when I execute 'make install' [snip] make[2]: Entering directory `/tmp/mailman/Mailman/MTA' make[2]: *** No rule to make target `install'. Stop. make[2]: Leaving directory `/tmp/mailman/Mailman/MTA' make[1]: *** [install] Error 2 make[1]: Leaving directory `/tmp/mailman/Mailman' [snip] I have noticed this for some weeks but I have not paid much attention. Has anybody experienced this too? Cheers -- ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey(a)uma.es) | | Servicio Central de informática | | Universidad de Málaga - España | #----------------------------------------------#

2 1

Trivial stats on Postfix
by J C Lawrence 21 May '01

21 May '01

I just did a very quick check: 1 message delivered to a list with 1,000 members Distribution list is pretty atypical (very low AOL, MSN, Hotmail etc counts). Its a tehcnical/professional audience. The largest number of members in the distribution list all at the same domain is AOL with 27. Average number of members per domain is 2.6. MAX_RCPT_TO is set to 5. MTA is postfix with a very close to default config (no DNS check tho) Local cacheing nameserver via DJBDNS Nameserver is pre-stuffed with records for distribution list (previous list activity). Postfix spool was compleatly empty prior to run. Machine in question is a dual PII-333 with 512Meg RAM. Spool is on the same spindle as /var/log, and is under ResierFS Postfix is logging through syslog to localhost. Postfix is configured for 10 parallel deliveries to responsive MXes. Host OS is Debian/Testing. Total time required to hand off the message (200 spool entries) and deliver the spool down to the point of only slow MX'es left: 53 seconds (might be a bit faster, my stopwatch finger was lazy). Total number of spool entries left after 53 seconds: 16/16 targets Total number of spool entries after two minutes: 14/14/targets Total number of spool entries after 10 minutes: 14/14/targets Translation: Every slow spool entry has only one RCPT TO and the slow MXes really are slow. Outbound bandwith is via 100bT to a couple T3s and a T1. Relatively meaningless numbers given the artificiality of the conditions the extremely light load, and the rather unexamined distribution pattern of the membership base, but kinda interesting none the less. Surprised me too. -- J C Lawrence claw(a)kanga.nu ---------(*) http://www.kanga.nu/~claw/ The pressure to survive and rhetoric may make strange bedfellows

1 0

disabling feature question
by Bradford Shaw 21 May '01

21 May '01

Hello everyone, I am new to this list. I am the Mailing List Administrator for our company. I am impressed with the quality of the Mailman program and look forward to running the program. We just installed it for our list hosting (mainly to replace Majordomo to give our customers a web-based program for their lists). I have a question that I am not able to find answers for in the archives and am hoping that you can direct me to where I can find the answer. Simply, we need to remove the "Edit the HTML for the public list pages" under the 'Other Administrative Activities' on the General Options page. Our take on this is that once we have the list set up for our customer, we don't want them messing with the html. First, because we want our logo to stay on the list pages and, second, because many of our customers are not proficient in html and a minor slip could render the output unreadable. So can you direct me to where I can get this item removed? Well, I said a couple questions but I'll hold off on the others. I need an answer to the above question right away as I am not comfortable going public with this until I can disable that feature. I appreciate your help and I hope that I can reciprocate in the near future. Best wishes, Bradford "Biff" Shaw List Administrator PerilPoint Communications Inc. http://www.perilpoint.com

2 1

OT -- Webmail IMAP clients
by J C Lawrence 20 May '01

20 May '01

Forget who asked about this recently. At the time I recommended Twig (its what I use). I'm currently evaluating SilkyMail: http://www.cyrusoft.com/silkymail/ If you don't need the groupware features of Twig (I don't) SilkyMail makes a compelling argument. The basic user interface if quite a bit sweeter than Twig's. And yes, its GPL. -- J C Lawrence claw(a)kanga.nu ---------(*) http://www.kanga.nu/~claw/ The pressure to survive and rhetoric may make strange bedfellows

1 0

Template file lookup
by barry＠digicool.com 20 May '01

20 May '01

I'm about to change the search order for templates -- you know, those pesky .html and .txt files that live in $prefix/templates and $prefix/lists/$mylist. This change is necessary to properly support language templates, and also provides a much requested feature, namely that you will only need to specialize templates that you actually want to change, and that you have multiple levels of specialization. Here's how it works. There are 4 levels of template specialization: list-centric, vhost-centric, site-centric, and default, corresponding to the directories $prefix/lists/$listname $prefix/templates/$host_name $prefix/templates/site $prefix/templates Each of these locations is further organized by language subdirectories. So let's say you were looking for the listinfo.html template for list foobar in language es. You'd actually end up searching 12 directories, with of course, the first hit stopping the search. Let's say further that list foobar is in the www.foobar.com virtual domain, and that it's list-preferred language is fr, while the server's default language is en. Here's the files you'd search for: $prefix/lists/foobar/es/listinfo.html $prefix/templates/www.foobar.com/es/listinfo.html $prefix/templates/site/es/listinfo.html $prefix/templates/es/listinfo.html $prefix/lists/foobar/fr/listinfo.html $prefix/templates/www.foobar.com/fr/listinfo.html $prefix/templates/site/fr/listinfo.html $prefix/templates/fr/listinfo.html $prefix/lists/foobar/en/listinfo.html $prefix/templates/www.foobar.com/en/listinfo.html $prefix/templates/site/en/listinfo.html $prefix/templates/en/listinfo.html Note that the Mailman 2.0.x search directories of $prefix/lists/*.{html,txt} and $prefix/templates/*.{html,txt} are deprecated and no longer searched. The bin/upgrade script will actually md5 checksum all the old files and remove any templates in more-specific locations that exactly match their more-general counterparts. Any template in $prefix/lists or $templates will have to be moved manually. It is highly discouraged that you will ever manually edit a file in $prefix/templates/$lang, and Mailman's install target will have every right to overwrite them on an upgrade. That's what the templates/site subdirectory is for; upgrading will never touch site-centric, domain-centric, or list-centric templates. Of course, that means it's up to site administrators to merge in changes to the default templates. Watch for checkins shortly. Comments? -Barry

3 2

[전체회신] [Mailman-i18n] can't decode in web using mailman.
by bakyh＠etri.re.kr 19 May '01

19 May '01

I'm a korean. I installed a mailman to Linux 2.2.18. I succeed in sending and receiving msg, but in web failed. In web, I can't read msg in Korean. How can I do it? I think, its reason is that in web browser can't decoding that msg. Shoud I patch about it? What is the patch program and where I can get it? Please, help me. Bak, Yuhyeon.

2 1

Moderator approval
by Jesper Jensen 17 May '01

17 May '01

I saw this on the Mailman 2.1 Wiki page: "Provide an email interface to all administrative commands" Does this include the approval of moderated messages? If so, has any work been done on this or do you know how it will work? Will it be (or is it already) possible to have the approval sent to more than one person? Thanks, Jesper.

3 3

Error in bin/config_list
by Juan Carlos Rey Anaya 17 May '01

17 May '01

I have received a message with the error description: Vizi Szilard <vizisz(a)freemail.hu> > - I found an error: > [root@tatooin bin]# ./config_list -o /root/config test > Traceback (most recent call last): > File "./config_list", line 261, in ? > main() > File "./config_list", line 254, in main > do_output(listname, outfile) > File "./config_list", line 115, in do_output > info = config[k] > KeyError: altalanos > > altalanos means general in English. What is the problem? I have taken a glance to Mailman code and I have found: in MailList.py.GetConfigInfo: config_info['general'] = [_( "Fundamental list characteristics, including descriptive" " info and basic behaviors."), ('real_name', mm_cfg.String, 50, 0, _('The public name of this list (make case-changes only).'), and in config_list.do_output: config = mlist.GetConfigInfo() categories = (_('general'), _('privacy'), _('nondigest'), _('digest'), _('bounce'), _('archive'), _('gateway'), _('autoreply')) for k in categories: info = config[k] So 'k' must be untranslated, that's because that key does not exists in array 'config' -- ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey(a)uma.es) | | Servicio Central de informática | | Universidad de Málaga - España | #----------------------------------------------#

1 0

Mailman error Bad Marshal
by Kory Wheatley 17 May '01

17 May '01

Received this for a hour and then it went away everything worked after that, but is there any solution to this problem. ----- The following addresses had permanent fatal errors ----- "|/home/mailman/mail/wrapper mailowner ccaussec" (expanded from: ccaussec-admin) ----- Transcript of session follows ----- Traceback (innermost last): File "/home/mailman/scripts/mailowner", line 33, in ? from Mailman import MailList ValueError: bad marshal data 554 "|/home/mailman/mail/wrapper mailowner ccaussec"... unknown mailer error 1

1 0

How about Auto Discard
by Tokio Kikuchi 17 May '01

17 May '01

Hi! Developers, It is cumbersome to click 'Discard' on the admindb page each time a spam message come to the list address or at least every day basis. If we have an automatic discard function which will be ivoked by cron, we can just check the admin notice and do nothing. The held message will disappear two or three days later. Following script will do the job (I hope). Please review it and comment! Would it be better to define the expiration period in mm_cfg.py ? (I omitted the copyright/license notices) Regards, Tokio Kikuchi #!/usr/bin/env python # import sys import paths import time from Mailman import mm_cfg from Mailman import MailList from Mailman import Utils expire = 2 * 24 * 60 * 60 # 2 days now = time.time() def auto_discard(mlist): if not mlist.NumRequestsPending(): return heldmsgs = mlist.GetHeldMessageIds() total = len(heldmsgs) if total: for id in heldmsgs: info = mlist.GetRecord(id) ptime,sender,subject,reason,filename,msgdata = info if now - ptime > expire: print 'DISCARD',id, ptime, sender, subject mlist.HandleRequest(id, mm_cfg.DISCARD) mlist.Save() def main(): confined_to = sys.argv[1:] for listname in Utils.list_names(): if confined_to and listname not in confined_to: continue mlist = MailList.MailList(listname, lock=0) mlist.Lock() auto_discard(mlist) mlist.Unlock() if __name__ == '__main__': main()

1 0

Feature request
by Marc MERLIN 16 May '01

16 May '01

Looking at it now, it's surprising that this hasn't happened sooner: SF's mailman was abused with someone creating a bogus project with a mailing list which was then used to subscribe about 10,000 people and then spam them into oblivion. The best/worst part is how people made it a lot worse by complaining to the list itself and spamming one another after that: http://www.geocrawler.com/lists/3/SourceForge/10386/0/ Anyway, I patched admin.py to just disallow admin web subscribes altogether. In order of preference, for a future mailman version, it'd be nice if mailman would: - Have a config.db entry: allow web subscribes, that can only be changed by the mailman owner (i.e. master password, not list password) - Easier: have a sitewide mm_cfg.py variable to allow/disallow web subscribes by the list admin Thanks, Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

3 4

Virtual hosting
by barry＠digicool.com 16 May '01

16 May '01

I've started to sketch out some requirements for improving the virtual hosting support for Mailman. It's not finished, but I'm soliciting comments anyway. Please see http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/VirtualHosting and please add comments to the Wiki page. I'm not sure whether this stuff will make it into Mailman 2.1 or will have to be postponed. Cheers, -Barry

1 0