Mailman 3 July 2005 - Mailman-Developers

please update list.org/devs.html IRC channel listing
by Jim Tittsler 22 Jul '05

22 Jul '05

I believe <http://www.list.org/devs.html> should be updated to change the IRC network name from openprojects.net to freenode.net. -- Jim Tittsler http://www.OnJapan.net/ GPG: 0x01159DB6 Python Starship http://Starship.Python.net/crew/jwt/ Mailman IRC irc://irc.freenode.net/#mailman

2 1

Re: [Mailman-Developers] XML-RPC interface to mailman
by Joseph Tate 22 Jul '05

22 Jul '05

On 7/22/05, David Gibbs <david(a)midrange.com> wrote: > Joseph Tate wrote: > > I've created a patch to Mailman to add XML-RPC based remote procedure > > calls to mailman. > > Joseph: > > I'm very interested in this functionality ... I'm working with a local > computer user group to integrate their membership system with mailman, > so they can add and remove list subscribers when membership information > changes. > > Sorry to say, but I'm not very fluent in Python ... could you tell me > what functions you have exposed via this interface? How hard do you > think it would be to invoke the functions from a Java program? > > Thanks very much! > > david > > -- Joseph Tate Personal e-mail: jtate AT dragonstrider DOT com Web: http://www.dragonstrider.com

1 0

PGP and Mailman
by Joost van Baal 22 Jul '05

22 Jul '05

Hi, I will write and publish a patch which integrates PGP signature validation and re-encryption of encrypted posts to mailman. Specs are: - A post will be distributed only if the PGP signature on the post is from one of the list members. - For sending encrypted email, a list member encrypts to the public key of the list. The post will be decrypted and re-encrypted to the public keys of all list members. (Later, the patch will handle RFC 2633 (S/MIME) messages too, next to RFC 2440 (OpenPGP)). I've taken a look at the NAH6 secure list patch #646989 at http://sourceforge.net/tracker/index.php?func=detail&aid=646989&group_id=10… and at Ben Laurie's patch #645297 at http://sourceforge.net/tracker/index.php?func=detail&aid=645297&group_id=10… , but I believe none of these completely implements the listed requirements (although these will help me implementing, of course). I am asking you to take a look at my plan for implementation. Am I on the right track? So, the plan: I think one way to implement it would be to add two modules to GLOBAL_PIPELINE: in front, before SpamDetect, there would be 'PGPCheck'. PGPCheck would check wether the message is encrypted, and, if so, make a temporary decrypted copy in order to verify with which key is was signed. If the message is unencrypted, it would check the signature. It would store this information in new properties of the Mailman Message object. A second new module in GLOBAL_PIPELINE would be 'PGPRecrypt', to be called after CookHeaders' and before 'ToDigest'. This would, if needed, decrypt the message and reencrypt it to all recipients, and would sign it. If for instance a list member erroneously signs a post with a wrong public key, and encrypts the message, this message should be handled carefully. I believe the Hold module should be adapted for this. A copy of the original encrypted message should be kept. The message should be decrypted, signed with the listkey, encrypted to the list moderator key, and sent for acknowledgement. If the moderator chooses to deny the message, the poster should get her original message back. (I guess.) For all PGP handling, I plan to use Frank J. Tobin's GnuPGInterface ( http://py-gnupg.sourceforge.net/ ). I plan to write the patch against current stable Mailman. Any insight to share on this? Thanks! Bye, Joost -- Joost van Baal http://abramowitz.uvt.nl/ Tilburg University j.e.vanbaal(a)uvt.nl The Netherlands

4 12

version mismatch?
by Ian Eiloart 20 Jul '05

20 Jul '05

Hi, Yesterday, I upgraded python on solaris 8 to version 2.4.1 in preparation to upgrade Mailman - as that's the currently recommended version. Today I upgraded Mailman to version 2.1.6, and the web pages said they'd hit a bug. I checked the error log and found these entries (I've altered the whitespace for legibility): Jul 20 15:11:54 2005 admin(25535): /usr/local/mailman/pythonlib/japanese/c/euc_jp.py:3: RuntimeWarning: Python C API version mismatch for module _japanese_codecs: This Python has API version 1012, module _japanese_codecs has version 1011. import codecs, japanese.c._japanese_codecs admin(25535): /usr/local/mailman/pythonlib/korean/c/euc_kr.py:24: RuntimeWarning: Python C API version mismatch for module _koco: This Python has API version 1012, module _koco has version 1011. import _koco Am I right in thinking this means that I need to downgrade my python version to make this work? Well, that seems to be working. Did I miss something that would make 2.1.6 work with python 2.4.1? If not, then this page needs fixing: <http://www.list.org/requirements.html> -- Ian Eiloart Servers Team Sussex University ITS

4 3

OSCON session..
by Darrell Fuhriman 16 Jul '05

16 Jul '05

Are any Mailman developers planning to be at OSCON? I wouldn't mind having a Mailman BOF. Darrell

2 1

content filtering bug (text/html and text/plain in multipart emails)
by Michael Dunlap 13 Jul '05

13 Jul '05

Hello, I've been reading the archives and it looks as if the problem of having content filtering on and passing multi-part emails (plain and html) isn't really solvable. One email to the users list summarizes the problem this way: > There is a basic design decision in content filtering that makes this > difficult. Namely, after filtering, only the first remaining sub-part > from a multipart/alternative part is retained. > > What this means in practice is if you want to allow both text/plain > parts and text/html parts, the only way to get html to the list is to > insure that the MUA (e-mail client) that creates the post creates an > html only message, not a multipart/alternative message with both > text/plain and text/html sub-parts. > > If you want Mailman content filtering to pass the html part from a > multipart/alternative post, the only way to do this is to disallow > text/plain and require everyone to post html, or to turn off content > filtering and allow everything. My question is two parts. One, is there a work-around available, and two is this a "feature" which the developers intend to fix? Thank you for your time, Michael -- Michael Dunlap UNIX Systems Administrator michael.dunlap(a)yale.edu Workstation Support, ITS (203) 432-1256 Yale University

6 9

unicode traceback
by Jeroen Ruigrok/asmodai 10 Jul '05

10 Jul '05

Gents and ladies, on the freedesktop.org site we encountered a lot of troubles with moderation queues. Some emails got stuck due to Logger.py dying. This is with 2.1.5. I verified with a trunk version and spotted the problem has not been corrected. Find attached a suggested patch which I think should solve this issue. I find more unicode() calls in the Mailman 2.1.x source tree that do not seem to guard against encoding failing or forget ValueError. Perhaps these also need either a(n) (additional) safeguard or 'replace' addition? To note: Mailman/Archiver/HyperArch.py: charset = unicode(charset[2], charset[0]) Mailman/Archiver/HyperArch.py: body = unicode(body, charset) Mailman/Utils.py: u = unicode(s, charset) Awaiting your feedback, first time I delved into the Mailman sources. :) -- Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono Free Tibet! http://www.savetibet.org/ | http://ashemedai.deviantart.com/ http://www.tendra.org/ | http://www.in-nomine.org/ Seize from every moment its unique novelty and do not prepare your joys...

2 3

Re: [Mailman-Developers] Mailman-Developers Digest, Vol 195, Issue 6
by steve＠cuppett.com 07 Jul '05

07 Jul '05

I will be away from e-mail from July 6, 2005 until July 14, 2005 on vacation. I will not be responding until after that time.

1 0

UnicodeDecodeError
by Andrew D. Clark 05 Jul '05

05 Jul '05

Hi, I consistently get shunted messages with errors like so in logs/errors: Jul 01 10:28:39 2005 (26124) Uncaught runner exception: 'ascii' codec can't decode byte 0xc5 in position 0: ordinal not in range(128) Jul 01 10:28:39 2005 (26124) Traceback (most recent call last): File "/home/services/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/home/services/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/home/services/mailman/Mailman/Archiver/Archiver.py", line 216, in ArchiveMail h.processUnixMailbox(f) File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 573, in processUnixMailbox self.add_article(a) File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 625, in add_article article.parentID = parentID = self.get_parent_info(arch, article) File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 657, in get_parent_info article.subject) File "/home/services/mailman/Mailman/Archiver/HyperDatabase.py", line 311, in getOldestArticle self.__openIndices(archive) File "/home/services/mailman/Mailman/Archiver/HyperDatabase.py", line 251, in __openIndices t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) File "/home/services/mailman/Mailman/Archiver/HyperDatabase.py", line 65, in __init__ self.load() File "/home/services/mailman/Mailman/Archiver/HyperDatabase.py", line 179, in load self.__sort(dirty=1) File "/home/services/mailman/Mailman/Archiver/HyperDatabase.py", line 73, in __sort self.sorted.sort() UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 0: ordinal not in range(128) Jul 01 10:28:39 2005 (26124) SHUNTING: 1119004634.531249+fd4e0ba403a784a3545f4d8e32c66015e33c5870 The message is in GB2312: %./show_qfiles ../qfiles/shunt/1119004634* ====================> ../qfiles/shunt/1119004634.531249+fd4e0ba403a784a3545f4d8e32c66015e33c5870.pck Received: from [61.144.65.81] (helo=service.netease.com) by ucsb.edu with esmtp id 1DjEDp-000Mp5-Se for webmaster(a)ucsb.edu; Fri, 17 Jun 2005 03:37:14 -0700 From: =?GB18030?B?0MLGt73pydw=?= <ivpinfo(a)service.netease.com> To: webmaster(a)ucsb.edu Content-Type: text/html;charset="GB18030" Content-Transfer-Encoding: 8bit ... Any tips or is this a mailman bug? -- Andrew Clark Campus Network Programmer Office of Information Technology University of California, Santa Barbara andrew.clark(a)ucsb.edu (805) 893-5311

2 2

[Patch] Accesskey for 'Next message'
by Gabriel Wicke 04 Jul '05

04 Jul '05

Hi, this one-liner adds the access key n to the 'Next message' link in the web archive ui. Rationale: Speeds up reading, especially with mozilla-based browsers where alt-n directly follows the link to the next message. Other browsers only select the link (IE) or require more obscure keys to be pressed (Opera), but still profit from it. Screen readers also take advantage of access keys. Kind regards Gabriel Wicke Index: Mailman/Archiver/HyperArch.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Archiver/HyperArch.py,v retrieving revision 2.41 diff -r2.41 HyperArch.py 490c490 < ' <A HREF="%s">%s\n</A></li>' --- > ' <A HREF="%s" ACCESSKEY="n">%s\n</A></li>' -- Gabriel Wicke

1 0