Mailman 3 June 2002 - Mailman-Developers

[ mailman-Patches-510415 ] Improve MIME header handling
by noreply＠sourceforge.net June 19, 2002

June 19, 2002

Patches item #510415, was opened at 2002-01-30 00:19 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id… Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Improve MIME header handling Initial Comment: This patch fixes a number of problems for non-English archives. In particular: - it normalizes the encoding name (converting to lower-case, splitting of potential \r characters, and splitting off potential quotes) - if the article and the header encoding differ, it tries to preserve the decoded header as a Unicode string, instead of immediately falling back to the MIME-encoded one (if the encoding is not known to Python it will still fall back) - if a Unicode string needs to be formatted, it uses character references for all non-ASCII characters. ---------------------------------------------------------------------- >Comment By: Martin v. Löwis (loewis) Date: 2002-06-19 20:17 Message: Logged In: YES user_id=21627 The patch applies to version 2.13 of HyperArch.py, just as the patch header says. It was current for the mailman CVS at the time of its creation. It has been applied to the mailman CVS by now (as 2.14), so it is now useless. Feel free to back-port it to mailman 2.0.8 if you want. ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-19 18:55 Message: Logged In: YES user_id=105527 I tried to apply this patch to mailman 2.0.8 and 2.0.9, and both times the patch didn't apply cleanly. In fact 6 out of 10 hunks failed here. Any hints on that? For which version was the patch created? ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-04-02 07:40 Message: Logged In: YES user_id=21627 The second version of this patch expects and ignores LookupError from unicode(), and it decodes the subjects from the next and previous articles. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id…

1 0

[ mailman-Patches-510415 ] Improve MIME header handling
by noreply＠sourceforge.net June 19, 2002

June 19, 2002

Patches item #510415, was opened at 2002-01-30 00:19 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id… Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Improve MIME header handling Initial Comment: This patch fixes a number of problems for non-English archives. In particular: - it normalizes the encoding name (converting to lower-case, splitting of potential \r characters, and splitting off potential quotes) - if the article and the header encoding differ, it tries to preserve the decoded header as a Unicode string, instead of immediately falling back to the MIME-encoded one (if the encoding is not known to Python it will still fall back) - if a Unicode string needs to be formatted, it uses character references for all non-ASCII characters. ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-19 18:55 Message: Logged In: YES user_id=105527 I tried to apply this patch to mailman 2.0.8 and 2.0.9, and both times the patch didn't apply cleanly. In fact 6 out of 10 hunks failed here. Any hints on that? For which version was the patch created? ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-04-02 07:40 Message: Logged In: YES user_id=21627 The second version of this patch expects and ignores LookupError from unicode(), and it decodes the subjects from the next and previous articles. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id…

1 0

Finding restrcit post to members options
by Kory Wheatley June 19, 2002

June 19, 2002

In Mailman is there a command line utility I can use to find out all the mailing lists that have the "Restrict post to members only" set as yes or 1? I've current installed Mailman 2.0.11 on Red Hat Linux 7.2 . -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him.

1 0

[ mailman-Bugs-571004 ] member_posting_only does not work
by noreply＠sourceforge.net June 19, 2002

June 19, 2002

Bugs item #571004, was opened at 2002-06-19 07:28 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=571004&group_id… Category: security/privacy Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Josef Grosch (jgrosch) Assigned to: Nobody/Anonymous (nobody) Summary: member_posting_only does not work Initial Comment: Version 2.0.11 on FreeBSD 4.6 Mailman allows people who are not on the list are allowed to post. member_posting_only is set yes but non members are still posting. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=571004&group_id…

1 0

Mail forwarding loops - discovered!
by Bob Puff＠NLE June 14, 2002

June 14, 2002

Hello all, I have been recently seeing a bunch of "Mail forwarding Loop" messages in my Postfix mail log. After pouring over this stuff for several hours, I think I found the problem... Microsoft! Seriously, here's the scoop: a user sends a message to the list, which gets properly distributed. Sometime later (I've seen a few hours to a few days), the exact message that went out of the list mysteriously comes back to the list, with the same FROM: (usually the list's admin address), and the same TO: address (the list posting address). Postfix catches the loop, as it sees it's "Delivered-To" line in there, and bounces the message back to the sender, which sometimes is the real sender, other times is the list bounce address. The sender gets the bounce, and thinks their message didn't go out, when it really did. I've seen at least three different mail servers that have caused this: a roadrunner server, xt1.xtlab.com, and some other one in Australia. The common thread is that they are all running Microsoft mail server software. One of the messages had a header line that indicated it came from some webmail server, so it's possible that the webmail server software itself is somehow buggered up, and sends out these messages when the user does something. If it is user interaction, that would explain the random delay I saw (up to 2 days on one message). Here's a sample header, with some comments: >From DRSpoelhof(a)cs.com Thu Jun 13 22:09:44 2002 Return-Path: <DRSpoelhof(a)cs.com> Delivered-To: cscmsgs(a)nlenet.net <--- my separate test mailbox to collect this message Received: from mail8.nc.rr.com (fe8.southeast.rr.com [24.93.67.55]) by list.nlenet.net (Postfix) with ESMTP id 65DA9128 for <csc(a)lists.churchsoundcheck.com>; Thu, 13 Jun 2002 22:09:44 -0400 (EDT) Received: from mail pickup service by mail8.nc.rr.com with Microsoft SMTPSVC; Thu, 13 Jun 2002 21:58:19 -0400 <--- HERE'S THE REMAILED MESSAGE GOING OUT! Received: from ncmx01.mgw.rr.com ([24.93.67.251]) by mail8.nc.rr.com with Microsoft SMTPSVC(5.5.1877.757.75); <-- Here's where the original message got delivered Wed, 12 Jun 2002 08:01:15 -0400 <--- NOTICE THE DATE CHANGE! Received: from list.nlenet.net (list.nlenet.net [208.178.159.75]) by ncmx01.mgw.rr.com (8.12.2/8.12.2) with ESMTP id g5CC1FbC010819; Wed, 12 Jun 2002 08:01:15 -0400 (EDT) Received: from list.nlenet.net (localhost.localdomain [127.0.0.1]) by list.nlenet.net (Postfix) with ESMTP id 0368EFE; Wed, 12 Jun 2002 08:01:11 -0400 (EDT) Delivered-To: csc(a)nlenet.net Received: from imo-r07.mx.aol.com (imo-r07.mx.aol.com [152.163.225.103]) by list.nlenet.net (Postfix) with ESMTP id 60E2EF8 for <csc(a)lists.churchsoundcheck.com>; Wed, 12 Jun 2002 08:00:56 -0400 (EDT) Received: from DRSpoelhof(a)cs.com by imo-r07.mx.aol.com (mail_out_v32.5.) id 7.cb.23799993 (657) for <csc(a)lists.churchsoundcheck.com>; Wed, 12 Jun 2002 08:00:50 -0400 (EDT) From: DRSpoelhof(a)cs.com Message-ID: <cb.23799993.2a3891f2(a)cs.com> Subject: Re: [CSC] surge protection To: csc(a)lists.churchsoundcheck.com My solution (for now) was to insert procmail into the picture, scan the message for the "Delivered-To" the list address header, and if present, dump the message to the bit-bucket. Otherwise, the message gets passed on to Mailman. But the mail server software needs to be fixed! I'm sure others out there are going to see this same thing happening. I've seen it on a few different servers of my own, so I know it's not just one specific machine. Bob

2 3

Searchable Archives
by Stephen Montgomery June 13, 2002

June 13, 2002

Hi, I was wondering if mailman offers the opportunity for keyword searchable archives. How do I go about implementing it? With my list I'm envisioning getting tired of answering the same questions and would like users to be able to search the archives easily. Cheers, Stephen -- Stephen Montgomery Graduate Student, Bioinformatics Genome Science Centre Vancouver, BC Canada Tel 604-877-6000 ext. 2543

3 2

[ mailman-Bugs-568456 ] base64 messages not decoded in archives
by noreply＠sourceforge.net June 13, 2002

June 13, 2002

Bugs item #568456, was opened at 2002-06-13 10:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=568456&group_id… Category: Pipermail Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Benjamin Geer (beroul) Assigned to: Nobody/Anonymous (nobody) Summary: base64 messages not decoded in archives Initial Comment: It appears that messages in base-64 encoding are not decoded in pipermail archives with Mailman 2.0.8. For example: http://lists.southspace.net/pipermail/esf-uk-coordinators/2002-June/000009.… In some cases I can tell people to switch to 8-bit or quoted-printable encoding, but some people are using web-based email services that don't give them any choice. The result is that their messages are shown as garbage in the archives. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=568456&group_id…

1 0

cron/disabled error
by Jon Parise June 13, 2002

June 13, 2002

I've been getting the attached error for a couple of weeks (just now getting the time to investigate it). I started occuring after my last cvs upgrade to Mailman 2.1b2+. Any hints on where to start looking to resolve the problem? -- Jon Parise (jon(a)csh.rit.edu) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member

1 0

[ mailman-Patches-534577 ] Add SpamAssassin filter to mail pipeline
by noreply＠sourceforge.net June 12, 2002

June 12, 2002

Patches item #534577, was opened at 2002-03-25 08:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id… Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: Add SpamAssassin filter to mail pipeline Initial Comment: This filter adds support for discarding or holding spam sent to the mailing list. It contacts a spamd daemon (from SpamAssassin -- http://spamassassin.taint.org) to score the message. If the score is above a certain threshold (default 10), the message is discarded and an entry is written to the vette log. If the score is above another lower threshold (default 5), the message is held for moderation. The SpamAssassin.py file should be installed in Mailman/Handlers/. The LIST_PIPELINE variable in Mailman/Handlers/HandlerAPI.py should be modified to include a 'SpamAssassin' item (I put it just after the existing 'SpamDetect' item). To change the defaults, the following can be added to the mm_cfg.py file: SPAMASSASSIN_HOST = 'host:port' # how to contact SA SPAMASSASSIN_DISCARD_SCORE = 10 SPAMASSASSIN_HOLD_SCORE = 5 If you don't want to discard messages, then DISCARD_SCORE can be set to something very high (1000 should do it). It looks the MM2.1 filter APIs have changed a bit, so this filter will need some modifications to work with that version. When I get round to upgrading, I might look into updating it. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-06-12 21:48 Message: Logged In: YES user_id=81797 FYI: I've been running the 2002-05-14 version of this patch with spamassassin 2.20 for the last day on our main mailman box and it seems to be working great. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-05-14 06:04 Message: Logged In: YES user_id=146903 This version is essentially the same as the previous version, but adds compatibility with python > 1.5.2, which doesn't like you passing two arguments to socket.connect(). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-04-27 06:17 Message: Logged In: YES user_id=146903 Just attached my updated version of the patch. This version requires SpamAssassin 2.20 (for the extra commands that the spamd daemon understands). It now displays a list of which rules were triggered for held messages, and can give messages from list members a bonus (defaults to 2), so that they are less likely to get held as spam. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-03-26 01:21 Message: Logged In: YES user_id=146903 There is a fairly easy optimisation for this filter that I missed when writing it. It calls str() on the message object twice. It would be quicker to call str() on the message once. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id…

1 0

mailman installation request
by cerdil＠ttnet.net.tr June 12, 2002

June 12, 2002

Hello, This is a very well written software, but we fall short in Python.Is there any mailman installation provided in this community, or could anybody install it for a fee. Thank you. Shawn Erdil. www.e-zbanner.com

1 0