Mailman 3 July 2002 - Mailman-Developers

[ mailman-Bugs-577685 ] sh syntax problem in configure
by noreply＠sourceforge.net July 11, 2002

July 11, 2002

Bugs item #577685, was opened at 2002-07-05 03:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=577685&group_i… Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: sh syntax problem in configure Initial Comment: in 2.0.12 configure script includes a statement: if [ "$?" == "1" ] which should be in a traditional sh: if [ "$?" = "1" ] (Note single =, not double =) configure fails on solaris 8 with double =, while the error was ignored on FreeBSD. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-11 18:28 Message: Logged In: YES user_id=12800 Can you please try the attached patch? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=577685&group_i…

1 0

Re: [Mailman-Developers] .lower() for older pythons
by barry＠zope.com July 11, 2002

July 11, 2002

>>>>> "MD" == Matt Domsch <Matt_Domsch(a)Dell.com> writes: MD> Thanks for this update. I've run across one problem. In MD> Mailman/MailCommandHandler.py, ParseMailCommands function: | + precedence = msg.get('precedence', '').lower() | + ack = msg.get('x-ack', '').lower() MD> With my python (1.5.2-30 as in Red Hat Linux 7.1), this MD> generates lots of errors in mailman/logs/error: Damn! It's really getting hard to keep Python 1.5.2 in mind. :( MD> I believe the proper fix is: MD> + precedence = string.lower(msg.get('precedence', '')) + ack = MD> string.lower(msg.get('x-ack', '')) MD> instead. With this, it works and doesn't generate those MD> errors. I'm not on mailman-developers, so please cc me on any MD> replies. You're exactly right. Attached is a patch. I guess I have to generate a 2.0.13. :( -Barry -------------------- snip snip -------------------- Index: MailCommandHandler.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Attic/MailCommandHandler.py,v retrieving revision 1.70.2.1 diff -u -r1.70.2.1 MailCommandHandler.py --- MailCommandHandler.py 2 Jul 2002 16:33:23 -0000 1.70.2.1 +++ MailCommandHandler.py 11 Jul 2002 21:16:47 -0000 @@ -120,8 +120,8 @@ # of these clues, so there's little we can do to break loops in that # case, except throttle the number of responses sent to any one # requester in a day. That's a job for MM2.1. - precedence = msg.get('precedence', '').lower() - ack = msg.get('x-ack', '').lower() + precedence = string.lower(msg.get('precedence', '')) + ack = string.lower(msg.get('x-ack', '')) beenthere = msg.get('x-beenthere', '') listid = msg.get('list-id', '') if (precedence in ('bulk', 'list', 'junk') or

1 0

Re: [Mailman-Developers] .lower() for older pythons
by barry＠zope.com July 11, 2002

July 11, 2002

>>>>> "MD" == Matt Domsch <Matt_Domsch(a)Dell.com> writes: MD> Thanks for this update. I've run across one problem. In MD> Mailman/MailCommandHandler.py, ParseMailCommands function: | + precedence = msg.get('precedence', '').lower() | + ack = msg.get('x-ack', '').lower() MD> With my python (1.5.2-30 as in Red Hat Linux 7.1), this MD> generates lots of errors in mailman/logs/error: Damn! It's really getting hard to keep Python 1.5.2 in mind. :( MD> I believe the proper fix is: MD> + precedence = string.lower(msg.get('precedence', '')) + ack = MD> string.lower(msg.get('x-ack', '')) MD> instead. With this, it works and doesn't generate those MD> errors. I'm not on mailman-developers, so please cc me on any MD> replies. You're exactly right. Attached is a patch. I guess I have to generate a 2.0.13. :( -Barry

1 0

.lower() for older pythons
by Matt_Domsch＠Dell.com July 11, 2002

July 11, 2002

> I' released Mailman 2.0.12 which fixes a cross-site scripting > vulnerability, among other changes. I recommend that folks upgrade > their 2.0.x systems to this new version. See below for a NEWS file > excerpt. Thanks for this update. I've run across one problem. In Mailman/MailCommandHandler.py, ParseMailCommands function: + precedence = msg.get('precedence', '').lower() + ack = msg.get('x-ack', '').lower() With my python (1.5.2-30 as in Red Hat Linux 7.1), this generates lots of errors in mailman/logs/error: Jul 11 15:30:00 2002 qrunner(17873): Traceback (innermost last): Jul 11 15:30:00 2002 qrunner(17873): File "/home/mailman/cron/qrunner", line 283, in ? Jul 11 15:30:00 2002 qrunner(17873): kids = main(lock) Jul 11 15:30:00 2002 qrunner(17873): File "/home/mailman/cron/qrunner", line 253, in main Jul 11 15:30:00 2002 qrunner(17873): keepqueued = dispose_message(mlist, msg, msgdata) Jul 11 15:30:00 2002 qrunner(17873): File "/home/mailman/cron/qrunner", line 157, in dispose_message Jul 11 15:30:00 2002 qrunner(17873): mlist.ParseMailCommands(msg) Jul 11 15:30:00 2002 qrunner(17873): File "/home/mailman/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands Jul 11 15:30:00 2002 qrunner(17873): precedence = msg.get('precedence', '').lower() Jul 11 15:30:00 2002 qrunner(17873): AttributeError : 'string' object has no attribute 'lower' I believe the proper fix is: + precedence = string.lower(msg.get('precedence', '')) + ack = string.lower(msg.get('x-ack', '')) instead. With this, it works and doesn't generate those errors. I'm not on mailman-developers, so please cc me on any replies. Thanks, Matt -- Matt Domsch Sr. Software Engineer, Lead Engineer, Architect Dell Linux Solutions www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com #1 US Linux Server provider for 2001 and Q1/2002! (IDC May 2002)

1 0

RELEASED Mailman 2.0.12
by barry＠zope.com July 11, 2002

July 11, 2002

I' released Mailman 2.0.12 which fixes a cross-site scripting vulnerability, among other changes. I recommend that folks upgrade their 2.0.x systems to this new version. See below for a NEWS file excerpt. As usual, I've made both full source tarballs and patches available. See http://sourceforge.net/project/showfiles.php?group_id=103 for links to download all the patches and the source tarball. If you decide to install the patches, please do read the release notes first: http://sourceforge.net/project/shownotes.php?release_id=97760 See also: http://www.gnu.org/software/mailman http://www.list.org http://mailman.sf.net Cheers, -Barry -------------------- snip snip -------------------- 2.0.12 (02-Jul-2002) - Implemented a guard against some reply loops and 'bot subscription attacks. Specifically, if a message to -request has a Precedence: bulk (or list, or junk) header, the command is ignored. Well-behaved 'bots should always include such a header. - Changes to the configure script so that you can pass in the mail host and web host by setting the environment variables MAILHOST and WWWHOST respectively. configure will also exit if it can't figure out these values (usually due to broken dns). - Closed another minor cross-site scripting vulnerability.

1 0

[ mailman-Bugs-579908 ] Very poor configuration design
by noreply＠sourceforge.net July 11, 2002

July 11, 2002

Bugs item #579908, was opened at 2002-07-10 19:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=579908&group_i… Category: configuring/installing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Bob Tanner (tanner) Assigned to: Nobody/Anonymous (nobody) Summary: Very poor configuration design Initial Comment: The way configure is setup it seems to assume that you are building mailman ON the box you will be installing it. This is a terrible design decision. Make for creating packages a total nightmare. Forcing a package builder to add entries into /etc/passwd and /etc/group, is another bad design decision. Forcing a package builder to have all the directories setup and proper permissions during build it a another bad design decision. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=579908&group_i…

1 0

[ mailman-Bugs-565706 ] user wrongly detected
by noreply＠sourceforge.net July 10, 2002

July 10, 2002

Bugs item #565706, was opened at 2002-06-07 01:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=565706&group_i… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Enrico Cherubini (bestkevin) Assigned to: Nobody/Anonymous (nobody) Summary: user wrongly detected Initial Comment: Hi, I'm using mailman 2.0.6 and a user, that is in the mailing list, is not able to write in it after I closed the list to members only. He is member as I can see in the members list, here is what happen: Jun 07 09:31:06 2002 (29505) post to lugvr from ., size=1350, success the poster is identified as '.'....here are headers of an email he sent: From: .::Spark::. <valid(a)email.here> If you need any further information you are welcome ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-07-10 11:51 Message: Logged In: NO Has the user turned off mail delivery? ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2002-06-07 01:43 Message: Logged In: YES user_id=227443 Ciao Enrico! did you remember me? I was pioppo on #linux-it @ IrcNET :) I think 1st of all you should upgrade to Mailman 2.0.11 and/or to a more recent Python (I guess you are using 1.5.2) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=565706&group_i…

1 0

2 pgms to assist in maintaining lists
by Dave Alden July 10, 2002

July 10, 2002

Hi, I've written 2 programs to help me maintain my mailing lists. The first I call "add_nonmembers". This program is based on add_members (I copied add_members to add_nonmembers and modified it :-). What it does is give me a simple command line interface to modifying the 4 options: accept_these_nonmembers hold_these_nonmembers reject_these_nonmembers discard_these_nonmembers 3 of my mailing lists are for the particular type of employee: faculty, grads and staff. I want anyone on any of the lists to be able to post to any of the lists. Under majordomo I could point their equivalent of "accept_these_nonmembers" to a file which I would generate by listing all the members of all 3 lists. Under mailman I need to add everyone from the "other 2 lists" to the first list's accept_these_nonmembers option. I didn't see an easy way to do this, so I wrote add_nonmembers. The second program I wrote I call "subscribe_lists". It's similar to add_members, except it takes an address and as many lists as you want and subscribes the address to all of the lists. When we setup a new user, we usually subscribe them to multiple lists -- I felt it was easier to have a straightforward way to do this (rather than running add_members <n> times for <n> lists with the address coming from stdin each time. I'll include them (since they are short) -- or is there a better way to submit these? (if anyone is even interested :-) ...dave alden ps These are based on 2.1b2.

1 0

[ mailman-Bugs-555627 ] subject prefic encoding
by noreply＠sourceforge.net July 10, 2002

July 10, 2002

Bugs item #555627, was opened at 2002-05-13 14:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=555627&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Norbert Bollow (bollow) Assigned to: Nobody/Anonymous (nobody) Summary: subject prefic encoding Initial Comment: In Mailman 2.1b2 on Python 2.1.3 with a mailing list that has German as its default language, the subject prefix gets encoded unneccessarily, e.g. [MNO] becomes =?iso-8859-1?q?=5BMNO=5D_?= . ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-07-09 19:46 Message: Logged In: NO It happens the same for mailman in spanish as default language, besides it reencode de original subject so one subject like: =?iso-8859-1?Q? prueba__no_leer:_el_parag=FCas=2C_el_cami=F3n_y_el_ni= F1o_?= becomes: =?iso-8859-1?q?=5BMON=5D_?= =?iso-8859-1?q?=3D=3Fiso-8859- 1=3FQ=3Fprueba=5F=5Fno=5Fleer=3A=5Fel=5Fpa?= =?iso-8859-1?q? rag=3DFCas=3D2C=5Fel=5Fcami=3DF3n=5Fy=5Fel=5Fni=3 DF1o=5F?= =?iso-8859-1?q?=3F=3D?= where it should be: =?iso-8859-1?q?=5BMON=5D_?= =?iso-8859-1?Q? prueba__no_leer:_el_parag=FCas=2C_el_cami=F3n_y_el_ni= F1o_?= or even: [MON] =?iso-8859-1?Q? prueba__no_leer:_el_parag=FCas=2C_el_cami=F3n_y_el_ni= F1o_?= why the incoming subject line (with the "subject :" part striped) isn't copied verbatim to the next line of the message sended? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=555627&group_i…

1 0

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

July 10, 2002

Patches item #534577, was opened at 2002-03-25 16:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_i… 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: James Henstridge (jhenstridge) Date: 2002-07-10 08:19 Message: Logged In: YES user_id=146903 The Mailman installation on mail.gnome.org also uses this filter. I don't think there are any stability problems with the filter. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-07-10 05:16 Message: Logged In: YES user_id=81797 FYI, I ran the previous version since installation and it seemed to work fine. I didn't run into any problems, with probably 500 messages handled. I've updated to the new version and it seems ok so far, but I've only sent about 10 messages through. Sean ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-03 12:02 Message: Logged In: YES user_id=146903 Yet another version. There were some bugs in handling of certain error conditions when talking to spamd. These would result in exceptions and the messages staying in the delivery queue :( With the new version, the message will be passed through unchecked under these conditions, and a message will be added to the error log. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-06-13 05: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 14: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 14: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 09: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: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_i…

1 0