Mailman 3 November 2005 - Mailman-Developers

PHP Wrappers?
by Adrian Wells 17 Mar '06

17 Mar '06

Hello. How might one configure Mailman (version 2.1.6) list settings using PHP scripts? The goal is to configure Mailman list settings such as domain name of list, non-digest footer, set welcome/goodbye messages, etc. An approach that comes to mind is to use bin/config_list. This would require writing/reading files and using bin/config_list to process them. Is there another recommended or preferred way to accomplish this? There was a post about "PHP Wrappers" which suggested, "...just use a setuid mailman wrapper script that does caller-checking to see if it's called correctly, by the right user, and with 'safe' values" <http://mail.python.org/pipermail/mailman-developers/2001-March/008421.html>. This was recommended over simply adding the www user to the mailman group. I do not completely understand how one creates a setuid mailman wrapper script. Is this a matter of creating something similar to mail-wrapper.c? If someone has written a wrapper script or has some good resources further explaining this to share and is willing to do so, I would appreciate it. Thank you, -Adrian

16 64

XMLRPC Patch
by Joshua Ginsberg 13 Feb '06

13 Feb '06

I'm developing a patch to add an XMLRPC-based management interface to Mailman. Would this be something that you would be interested in trying to incorporate in the 2.1.x branch? Thanks! -jag -- Joshua Ginsberg <jag(a)fsf.org> Free Software Foundation - Senior Systems Administrator

5 14

A better way of doing templates?
by Barry Warsaw 10 Jan '06

10 Jan '06

Jordi Mallach brings up a good point on the rosetta-users mailing list, in response to my queries there. Rosetta doesn't really work with non-po files, so the fact that we have templates that need translating will cause us some grief. Well, even more grief than it has over the years. ;) Does anybody have any good ideas for handling this in the Mailman 2 tree? For MM3, it's a top priority that any templating system we use must support po-ification for i18n. For Mailman 2.2 it's more difficult because I don't think we should adopt an entirely new template system. It's even worse for 2.1 because we're not accepting new features, although if we came up with something simple and minimally disruptive, I'd consider it for the benefit of improving the translation process. Ideas are welcome! -Barry

5 7

Scrubber mungs Quoted Printable
by Mark Sapiro 17 Dec '05

17 Dec '05

A couple of posts on the mailman-users list (<http://mail.python.org/pipermail/mailman-users/2005-September/046400.html> and <http://mail.python.org/pipermail/mailman-users/2005-October/047367.html>) have pointed out that there is a problem with Scrubber.py. The basic issue is that under some circumstances, the scrubbed message is quoted-printable encoded, but Scrubber unconditionally adds a 'Content-Transfer-Encoding: 8bit' header resulting in garbled content when the message is viewed. The addition of the header was a small part of the patch at <http://sourceforge.net/tracker/index.php?func=detail&aid=655214&group_id=10…> and the associated comment is - Fixes a bug in the scrubber, where a content-transfer-encoding might have survived flattening of the message. I think the fix for the current problem is the following patch - --- mailman-2.1.6/Mailman/Handlers/Scrubber.py +++ mailman-mas/Mailman/Handlers/Scrubber.py @@ -376,9 +376,8 @@ # Now join the text and set the payload sep = _('-------------- next part --------------\n') del msg['content-type'] - msg.set_payload(sep.join(text), charset) del msg['content-transfer-encoding'] - msg.add_header('Content-Transfer-Encoding', '8bit') + msg.set_payload(sep.join(text), charset) return msg I have checked this with Tokio, and he agrees, but I don't have any message that would have triggered the original bug to test against nor do I know what the characteristics of such a message would be or if subsequent changes in the Python email library have taken care of it. Thus, before committing this patch, I'd like to see it get a bit more exposure/testing and/or get feedback from someone who knows something about the original bug. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 4

Bouncer.py syslog differences
by Adrian Wells 06 Dec '05

06 Dec '05

Hello. The following is portion of an exchange of ideas between Mark Sapiro and myself (initial comments) which occurred not too long ago on this list: >>>>> >>>>As a minor side note, I noticed the bounce log receives two different >>>>formatted messages for the first bounce and subsequent bounces. An >>>>example: >>>>... >>>>Oct 25 10:50:51 2005 (2687) samplelist: falseaddresstest(a)somedomain.net >>>>bounce score: 1.0 >>>>Oct 25 11:06:54 2005 (2687) falseaddresstest(a)somedomain.net: samplelist >>>>current bounce score: 2.0 >>>>... >>>>This is not a major issue but it is inconsistent and it not clear why >it >>>>should be this way. Is there reason is should be different? >>> >>> >>>I don't think so. All the other log messages from Bouncer are "list: >>>member". I don't see any reason why this one shouldn't also be that >>>way. >> >> >>OK. Should this be entered as a bug on SF? > > Yes, I think so, but I'd be inclined to wait a bit and see if there are more comments from the list. >>>>> It does not appear that more comments have been made on this issue. I am trying to work with the output of the Mailman logs (Brad Knowles has a great script <http://sourceforge.net/tracker/index.php?func=detail&aid=1123383&group_id=1…> for this but, it would be preferred to store more information in a database for reporting- not sure the best way to do this yet) and this minor difference is slightly annoying. Additionally, as Mark noted, no reason has been given to explain difference from other "current bounce score" messages. Here is a patch that should correct this difference: --- Bouncer.py.10.25.2005.original 2005-10-25 12:21:57.000000000 -0400 +++ Bouncer.py.log.patch 2005-11-11 11:27:08.000000000 -0500 @@ -145,7 +145,7 @@ info.score += weight info.date = day syslog('bounce', '%s: %s current bounce score: %s', - member, self.internal_name(), info.score) + self.internal_name(), member, info.score) # Continue to the check phase below # # Now that we've adjusted the bounce score for this bounce, let's Unless there is a case against filing this as a bug on SourceForge, I'm willing to file one within the next couple weeks. -Adrian

2 2

Use of tabs when folding header lines
by Nathan Herring 28 Nov '05

28 Nov '05

I am a member of a list which uses mailman 2.1.2, and I am experiencing strangeness in Outlook as a result of the modifications mailman performs on list posts. Specifically, when it (re)folds the Subject: and/or Thread-Topic: headers, it replaces a space character in the original subject with a tab character. According to RFC 2822 §2.2.3, unfolding one of these lines consists of only removing the CRLF. As a result, what had been a subject of the form "source_line1 source_line2" is now "source_line1\tsource_line2" in the mailman-altered mail, which is incorrect, and is displayed oddly by Outlook (due to some differences between tabs and space characters). (The other modification to the subject line, specifically, the addition of the "[mailinglist] " string, is fine.) When wrapping header lines, mailman should only insert (or move around) CRLFs and retain the original WSP characters from the original, lest issues like these arise. Is this a known issue, or should I post a new bug? Thanks in advance, Nathan ---- Nathan Herring MacBU SDE/Development

1 0

Pipermail threading and Debian bug 167758
by Max Bowsher 28 Nov '05

28 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pipermail's threadKeys currently assume that the Date header of each mail message sent to the list is unique. If two messages with the same Date both start new threads, then the thread display in the pipermail archives will erroneously intermingle the two threads. This is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=167758 . Debian have applied a patch to fix this, by including Message-IDs in the threadKeys too. Ironically, this actually creates an even worse bug, since they have failed to notice that '-' is a perfectly legal character in a message-id, thus, when pipermail counts the number of '-' characters in the threadKey to determine the nesting depth, it often gets a totally wrong answer. This happens often, since all it needs is a message-id containing a dash. Exim message-ids always contain at least two, and message-ids often include domain names, which sometimes include dashes. So, after that little bit of rambling, my essential question is: Was there ever any previous discussion about this issue, or did the Debian folks not raise the issue upstream? Max. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) iD8DBQFDivZ5fFNSmcDyxYARAuroAJ9o7fzyy4kBtepLPg9PkEVKp5F+AACghh7f RyhxrGfae810YN1K8zfpGnE= =BOP5 -----END PGP SIGNATURE-----

2 1

Make web_page_url visible in the admin GUI?
by Max Bowsher 28 Nov '05

28 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've taken over responsibility for an old Mailman installation which used to be configured with incorrect vhost information. As a result, web_page_url is incorrect for many lists. I have found the info about using config_list to adjust web_page_url, and now I have some questions/suggestions: Is there any reason not to add web_page_url to the configurable options in the admin GUI? Right below host_name in the general category would be a good place. Or, if the web_page_url is to remain hidden, should it not be re-calculated based on the current mm_cfg.py settings whenever the host_name setting for a list is changed - or even, calculated every time that information is required? Thanks, Max. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) iD8DBQFDh35bfFNSmcDyxYARAnY/AJwIKOQvvDevwtunG2+iLhOBI/AUiACfZAoS Hth3dW+nc6NWmFNax7cndf0= =KsI8 -----END PGP SIGNATURE-----

6 16

Parsing templates with '%' in them?
by Bob Tanner 26 Nov '05

26 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I wanted to change the article.html template and do some CSS in it, but I found mailman -silently- failed to parse the template files. I've submitted the attached patch to at least log the fact the template parsing failed. - ----------------------- snip -------------------------------- - --- HyperArch.py 2003-12-26 14:41:30.000000000 -0600 +++ HyperArch.py-bob 2005-11-23 03:19:13.000000000 -0600 @@ -217,8 +217,9 @@ Utils.GetCharSet(lang), 'replace') text = sdict.interpolate(utemplate) - - except (TypeError, ValueError): + except (TypeError, ValueError), e: # The template is really screwed up + syslog('error', 'The template is really screwed up: %s\n', e) pass # Make sure the text is in the given character set, or html-ify any # bogus # characters. - ----------------------- snip -------------------------------- Next, I could not seem to isolate the "bug", but my CSS had the following entries: div#main { margin-right: 20%; } div#menu { width: 15%; float: right; } The html template parser was failing on the 20% and the 15%, looking like it was keying off the '%' for key=value in the SafeDict class and failing. I "solved" the problem by making the CSS an external html reference, but I thought I'd post this info to the developer list as a FYI. - -- Bob Tanner <tanner(a)real-time.com> | Phone : (952)943-8700 http://www.real-time.com, Minnesota, Linux | Fax : (952)943-8500 Key fingerprint = AB15 0BDF BCDE 4369 5B42 1973 7CF1 A709 2CC1 B288 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDiS0bfPGnCSzBsogRAjO2AJ94i5AM4VyQbMGTppwwILeygUALSwCdHpkj mw8ylEsCQxXZzqKfSAFbxiw= =rTtc -----END PGP SIGNATURE-----

1 0

Default Spam Header Filter Rules hack
by Magnus Danielson 26 Nov '05

26 Nov '05

Hi! As I am working on setting up a multilist/multidomain setup using Mailman 2.1.6, I encountered the need that I wanted to be able to set the default header filter rules so that the lists I create will all have the same basic rule (since we concluded we want one as default). It proved to be a fairly small hack, so I thought I contribute it to you. diff MailList.py.orig MailList.py 342c342,343 < self.header_filter_rules = [] --- > self.header_filter_rules = \ > mm_cfg.DEFAULT_HEADER_FILTER_RULES diff Defaults.py.orig Defaults.py 908a909,918 > # New style SPAM Privacy header filtering > # Mailman can match the patterns of header content and decide upon different > # actions (Defer, Hold, Reject Discard and Accept). These properties is > # configured per list, and here can the list default be set. > # A list of rules where each entry contains the matching string, the action > # code and an empty flag (set False). > # Example (discard mails marked by SpamAssassin): > #DEFAULT_HEADER_FILTER_RULES = [('X-Spam-Status: Yes', DISCARD, False)] > DEFAULT_HEADER_FILTER_RULES = [] > OK, it certainly could be cleaned up in the aspect of comments/documentation, but it should be the trivia part for you guys. It has been tested to work. Cheers, Magnus

1 0