Mailman 3 April 2003 - Mailman-Developers

Mailman with Exim: README.EXIM to correct
by Leonhard Knauff 28 Apr '03

28 Apr '03

Hallo, I use (will use) Mailman 2.1.1 in a Solaris 8 Sun Cluster 3.0 High Availability Environment (with Exim 3.36). Therefore I installed the binaries, configurations, ... on each host of the cluster (so I can update on each host separate), and the variable data only one times on the shared disks: ./configure --prefix=/usr/local/mailman --with-var-prefix=/global/web/mailman The different prefixes ($prefix, $varprefix) must reflect in the Exim 3 "configure" file now: > MAILMAN_HOME = /usr/local/mailman # OK, $prefix > MAILMAN_VAR = /global/web/mailman # NEW, $varprefix !!! > > mailman_director: > require_files= MAILMAN_VAR/lists/$local_part/config.pck ^^^^^^^^^^^ CORRECTED !!!!! Use of MAILMAN_HOME is wrong! I think the same must be done in the mailman_router under Exim 4. So the file README.EXIM should be updated. The mailman_transport under Exim 3 seens to work. :-) Regards, Leonhard Knauff -- /---------------------------------------------------------------------------\ | Leonhard Knauff Phone: +49 345 55-21890 | | Martin-Luther-Universitaet Halle-Wittenberg Fax: +49 345 55-27008 | | Universitaetsrechenzentrum, Kurt-Mothes-Str. 1, D-06120 Halle (Saale) | | EMail: knauff(a)urz.uni-halle.de | \---------------------------------------------------------------------------/

1 0

RELEASED Mailman 2.1.2
by Barry Warsaw 27 Apr '03

27 Apr '03

I've just released Mailman 2.1.2 which includes many bug fixes and language updates, as well as support for two new languages, Portuguese/Portugal and Polish. I recommend all Mailman 2.1 users upgrade to this release. The full source tarball has been made available from the usual sites. Currently, there is no patch available, but you should be able to install 2.1.2 over your existing 2.1.x installation. See http://sourceforge.net/project/showfiles.php?group_id=103 for links to download all the patches and the source tarballs. Be sure you restart your mailman daemon by doing a "mailmanctl restart" after installing. See also: http://www.gnu.org/software/mailman http://www.list.org (not yet updated) http://mailman.sf.net Cheers, -Barry -------------------- snip snip -------------------- 2.1.2 (22-Apr-2003) - New languages Portuguese (Portugal) and Polish. - Many convenient constants have been added to the Defaults.py module to (hopefully) make it more readable. - Email addresses which contain 8-bit characters in them are now rejected and won't be subscribed. This is not the same as 8-bit characters in the realname, which is still allowed. - The X-Originating-Email header is removed for anonymous lists. Hotmail apparently adds this header. - When running make to build Mailman, you can specify $DESTDIR to the install target to specify an alternative location for installation, without influencing the paths stored in e.g. Defaults.py. This is useful to package managers. - New Defaults.py variable DELIVERY_RETRY_WAIT which controls how long the outgoing qrunner will wait before it retries a tempfailure delivery. - The semantics for the extend.py hook to MailList objects has changed slightly. The hook is now called before attempting to lock and load the database. - Mailman now uses the email package version 2.5.1 - bin/transcheck now checks for double-%'s - bin/genaliases grew a -q / --quiet flag - cron/checkdbs grew a -h / --help option. - The -c / --change-msg option has been removed from bin/add_members - bin/msgfmt.py has been added, taken from Python 2.3's Tools/i18n directory. The various .mo files are now no longer distributed with Mailman. They are generated at build time instead. - A new file misc/sitelist.cfg which can be used with bin/config_list provides a small number of recommended settings for your site list. Be sure to read it over before applying! sitelist.cfg is installed into the data directory. - Many bug fixes, including these SourceForge bugs closed and patches applied: 677668, 690448, 700538, 700537, 673294, 683906, 671294, 522080, 521124, 534297, 699900, 697321, 695526, 703941, 658261, 710678, 707608, 671303, 717096, 694912, 707624, 716755, 661138, 716754, 716702, 667167, 725369, 726415

2 1

RELEASED Mailman 2.1.2
by Barry Warsaw 27 Apr '03

27 Apr '03

I've just released Mailman 2.1.2 which includes many bug fixes and language updates, as well as support for two new languages, Portuguese/Portugal and Polish. I recommend all Mailman 2.1 users upgrade to this release. The full source tarball has been made available from the usual sites. Currently, there is no patch available, but you should be able to install 2.1.2 over your existing 2.1.x installation. See http://sourceforge.net/project/showfiles.php?group_id=103 for links to download all the patches and the source tarballs. Be sure you restart your mailman daemon by doing a "mailmanctl restart" after installing. See also: http://www.gnu.org/software/mailman http://www.list.org (not yet updated) http://mailman.sf.net Cheers, -Barry -------------------- snip snip -------------------- 2.1.2 (22-Apr-2003) - New languages Portuguese (Portugal) and Polish. - Many convenient constants have been added to the Defaults.py module to (hopefully) make it more readable. - Email addresses which contain 8-bit characters in them are now rejected and won't be subscribed. This is not the same as 8-bit characters in the realname, which is still allowed. - The X-Originating-Email header is removed for anonymous lists. Hotmail apparently adds this header. - When running make to build Mailman, you can specify $DESTDIR to the install target to specify an alternative location for installation, without influencing the paths stored in e.g. Defaults.py. This is useful to package managers. - New Defaults.py variable DELIVERY_RETRY_WAIT which controls how long the outgoing qrunner will wait before it retries a tempfailure delivery. - The semantics for the extend.py hook to MailList objects has changed slightly. The hook is now called before attempting to lock and load the database. - Mailman now uses the email package version 2.5.1 - bin/transcheck now checks for double-%'s - bin/genaliases grew a -q / --quiet flag - cron/checkdbs grew a -h / --help option. - The -c / --change-msg option has been removed from bin/add_members - bin/msgfmt.py has been added, taken from Python 2.3's Tools/i18n directory. The various .mo files are now no longer distributed with Mailman. They are generated at build time instead. - A new file misc/sitelist.cfg which can be used with bin/config_list provides a small number of recommended settings for your site list. Be sure to read it over before applying! sitelist.cfg is installed into the data directory. - Many bug fixes, including these SourceForge bugs closed and patches applied: 677668, 690448, 700538, 700537, 673294, 683906, 671294, 522080, 521124, 534297, 699900, 697321, 695526, 703941, 658261, 710678, 707608, 671303, 717096, 694912, 707624, 716755, 661138, 716754, 716702, 667167, 725369, 726415

1 0

Wanted: canned replies
by Tom Neff 26 Apr '03

26 Apr '03

The OTHER most-wanted feature for me, besides per-member aliases, is moderator editable canned rejection reasons. Most lists have a slowly growing and changing - but otherwise quasi-stable - list of "most popular reasons" for rejecting a posting. This is the comet announcement list - asteroids go to ASTEROID-ANNOUNCE(a)XYZ.EDU. There was no text in your message. We don't post for-sale-by-owner ads here on PLUTONIUM-DIGEST. :) etcetera, etcetera. I'm sure most moderators would jump at the chance to select from a customizable set of canned reasons when plowing through the admindb queue. If you needed something new or different you could always type it in, as now - but there could also be a "Save this as a canned response" button. Or maybe it's simpler to do all that maintenance on a separate admin subscreen.

3 2

Problems subclassing Mailman.Archiver.Archiver
by Kevin Murphy 25 Apr '03

25 Apr '03

Bewildered newbie seeks aid. For sinister reasons known only to myself, I want to subclass Mailman.Archiver.Archiver to extend the ArchiveMail method to do some extra work on each invocation. I created Mailman.Archiver.MyArchiver, subclassed Archiver, and made my changes. It compiles fine. I then changed MailList.py, replacing all references to Mailman.Archiver.Archiver to MyArchiver. It compiles fine. However, when install my changes and restart with mailmanctl, I get the following error: [root]# /home/mailman/bin/mailmanctl start Traceback (most recent call last): File "/home/mailman/bin/mailmanctl", line 538, in ? main() File "/home/mailman/bin/mailmanctl", line 357, in main check_for_site_list() File "/home/mailman/bin/mailmanctl", line 275, in check_for_site_list sitelist = MailList(sitelistname, lock=0) TypeError: 'module' object is not callable I suspect this has something to do with some pickled MailList object that's different than my altered MailList. But what do I know? I learned Python last week. :) Is there a way to get this to work, or am I going about it all wrong? -- Kevin Murphy

1 0

Re: [Mailman-Developers] English (USA)
by mch＠cix.compulink.co.uk 24 Apr '03

24 Apr '03

In-Reply-To: <E198MfK-0001nq-02(a)mail.python.org> Quoth Norbert Bollow <nb(a)thinkcoach.com>: > What ever happened to rationality? When did emotional moping take > precedence over sanity? When was there ever a rational definition of "sanity"? Start with some Foucault (in French, s'il te plait) - not that he's right, but that'll get you set on the questions. Including how the concept "sanity" may be used as a coercive instrument of power. Which, to get back to software, is the whole point of internationali{s|z}ation: to take account of local preferences and expectations *as they exist* so that the product is usable, with the fewest rough edges, by all. Think Oxford Dictionary (descriptive of how language *is* used) not Fowler (prescriptive). So, we go for the ISO codes. With 'en-co' - Cockney, innit, love - as the default, and list other variants for the weird :-) Mike

3 3

English (USA)
by Roger Lynn 24 Apr '03

24 Apr '03

On Tue 18 Mar, Thomas Wouters thomas(a)xs4all.net wrote: > On Wed, Mar 12, 2003 at 12:44:46PM +0100, CARTER Anthony wrote: > >> I would like to know if there is any way that we can remove the "USA" >> bit from the language options? For example, instead of "English (USA)" >> have just "English" > > Well, you can certainly do that for your own Mailman installation; just > search for 'USA' and remove the string where you see it :) Whether we want > that by default in the distributed Mailman is something else. I'd personally > be against it, because there is a real difference between, for instance, > English for the British and English for the Americans. Calling it English > (USA) at least makes it clear which version it is, even if there isn't > (yet) a British variant. Or is there ? I think having "English (USA)" appear as the only available language is more annoying for non-Americans than any Americanisms that might be in Mailman (and which are to be expected in most software anyway). So far, I've only noticed one, the spelling of "internationalisation", and that only appears on an admin page. Unless alternative English translations appear I would prefer the option to just be "English". To the original poster, if you haven't already discovered this: The languages can be renamed at the bottom of the Mailman/Defaults.py file. "internationalization" appears in Mailman/Gui/Language.py Roger

11 24

Re: Mailman-Developers Weird encoding problem
by Charlie Clark 24 Apr '03

24 Apr '03

Has anything changed on the digest side recently? My mailer (Beam, http://beam.sourceforge.net/) has been complaining that the digest isn't actually ASCII although it claims to be so the conversion to UTF-8 doesn't work properly. I've passed a few to the developer to see if this is a mail client issue but he says it seems to be Mailman's fault... any ideas? Charlie Clark accepted languages: en-EN, fr-FR, de-DE, nl-NL, se-SE, it-IT

1 0

[Patch] [long] Reply-To munging: stop the madness
by Joseph Knapka 23 Apr '03

23 Apr '03

And by "the madness", I mean the fact that I've seen more list traffic devoted to reply-to munging in the past year than to any other single subject. That's just silly; but Reply-To flamewars seem to break out every three months or so on every list I'm subscribed to. It's a tragic waste of bandwidth. It seems to me that the obvious way to make everyone happy is to make the presence of "Reply-To: list" headers a per-subscriber option. I have implemented something simple that achieves this goal in a fairly icky way; patch and explanation below. However, the main purpose of this message is to suggest that in some future Mailman release, "Reply-To: list" be a subscriber-centric option rather than a list-centric one. --- The patch below permits a list's accept_these_nonmembers attribute to contain entries of the form "^+listname", which causes Mailman to assume, for post-moderation purposes, that all subscribers to "listname" are also subscribed to the list being managed. For example, if list A's accept_these_nonmembers contains ^+B, then all subscribers to B will be allowed to post to A. This permits the following (suboptimal) solution to the Reply-To munging controversy: For each list L for which L.reply_goes_to_list="This list", create a second list L-no-reply-to with L-no-reply-to.reply_goes_to_list="Poster". Add L-no-reply-to to L's subscriber list. Add ^+L-no-reply-to to L.accept_these_nonmembers. Add ^+L to L-no-reply-to.accept_these_nonmembers. Now, anyone who doesn't want to get Reply-To headers subscribes to L-no-reply-to instead of L. Everyone still posts to L, however, and all traffic posted to L appears on both lists. Due to the ^+ options, anyone subscribed to either list can post to L and have their posts picked up by L-no-reply-to. (Of course, we could have allowed nonsubscribers to post to both lists, but no one on the particular list for which I produced these patches wanted to do that, due to spam problems.) This is obviously a less-than-perfect solution, which is why I'm suggesting it be done differently in a future release. I'm willing to look into implementing Reply-To as a subscriber option, but I may not have time to do so. Here are the patches, to GUIBase.py and Moderate.py. The patch to GUIBase.py simply relaxes the input validation to allow the ^+listname entries; the Moderate.py patch implements the additional moderation logic. ===File /usr/local/mailman/GUIBase.py.diff================== --- /usr/local/mailman/src/mailman-2.1.1/Mailman/Gui/GUIBase.py 2002-08-14 18:02:27.000000000 -0600 +++ GUIBase.py 2003-04-21 07:16:55.000000000 -0600 @@ -73,10 +73,11 @@ # See if this is a context that accepts regular # expressions, and that the re is legal if wtype == mm_cfg.EmailListEx and addr.startswith('^'): - try: - re.compile(addr) - except re.error: - raise ValueError + if not addr.startswith('^+'): + try: + re.compile(addr) + except re.error: + raise ValueError else: raise addrs.append(addr) ============================================================ ===File /usr/local/mailman/Moderate.py.diff================= --- /usr/local/mailman/src/mailman-2.1.1/Mailman/Handlers/Moderate.py 2002-12-30 20:28:41.000000000 -0700 +++ Moderate.py 2003-04-21 09:43:18.000000000 -0600 @@ -16,7 +16,6 @@ """Posting moderation filter. """ - import re from email.MIMEMessage import MIMEMessage from email.MIMEText import MIMEText @@ -28,6 +27,7 @@ from Mailman.i18n import _ from Mailman.Handlers import Hold from Mailman.Logging.Syslog import syslog +import Mailman.MailList @@ -115,14 +115,27 @@ def matches_p(sender, nonmembers): - # First strip out all the regular expressions - plainaddrs = [addr for addr in nonmembers if not addr.startswith('^')] + # First do list inclusions. + incAdd = [] + for linc in nonmembers: + if linc.startswith('^+'): + otherListName = linc[2:] + try: + otherList = Mailman.MailList.MailList(otherListName,lock=0) + otherMembers = otherList.getMembers() + incAdd = incAdd + otherMembers + except: + syslog.write("Moderator","Could not process list inclusion %s"%otherListName) + pass + nonmembers = nonmembers+incAdd + # Strip out all the regular expressions and list inclusions + plainaddrs = [addr for addr in nonmembers if not addr.startswith('^')] addrdict = Utils.List2Dict(plainaddrs, foldcase=1) if addrdict.has_key(sender): return 1 # Now do the regular expression matches for are in nonmembers: - if are.startswith('^'): + if are.startswith('^') and not are.startswith('^+'): try: cre = re.compile(are, re.IGNORECASE) except re.error: ============================================================ Cheers, -- Joe Knapka

7 8

Header & Footer for non-ASCII messages
by M.-A. Lemburg 23 Apr '03

23 Apr '03

We have run into a problem which is probably not uncommon for international mailing lists: whenever a message is sent that does not have US-ASCII as content type, header and footer are attached to this message via additional mime parts. This doesn't really look nice in the mail applications. Wouldn't it be wise to decode the message payload and prepend/ append the header and footer properly encoded to the payload instead ? -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, Apr 22 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 63 days left

5 7