Mailman 3 January 2006 - Mailman-Developers

Feature Request: message_id as replaceable token for footers etc.
by J C Lawrence Jan. 18, 2006

Jan. 18, 2006

Barry, Long time no talk. Whaddya think of adding message_id as a replaceable token for footers and the like? This would allow footers to be constructed which direct URL-reference their own post in an NNTP archive. -- J C Lawrence They said, "You have a blue guitar, ---------(*) You do not play things as they are." claw(a)kanga.nu The man replied, "Things as they are http://www.kanga.nu/~claw/ Are changed upon the blue guitar."

3 2

Re: [Mailman-Developers] [Mailman-Users] Problems with uuencoded attachments
by Tokio Kikuchi Jan. 16, 2006

Jan. 16, 2006

Mark Sapiro wrote: >> File "/usr/lib/python2.3/uu.py", line 139, in decode >> sys.stderr.write("Warning: %s\n" % str(v)) >> File "/usr/lib/mailman/Mailman/Logging/MultiLogger.py", line 45, in write >> _logexc(logger, msg) >> File "/usr/lib/mailman/Mailman/Logging/Utils.py", line 22, in _logexc >> sys.__stderr__.write('Logging error: %s\n' % logger) >>IOError: [Errno 32] Broken pipe > > I think this could be fixed by changing > "/usr/lib/mailman/pythonlib/email/Message.py", line 223 from > > uu.decode(StringIO(payload+'\n'), sfp) > > to > > uu.decode(StringIO(payload+'\n'), sfp, quiet=True) > > There should be other chances that Python builtin modules spew warnings to sys.stderr. How about this patch for Logging/Utils.py to write these messages into syslog facility. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ Index: Utils.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Logging/Utils.py,v retrieving revision 2.2.2.1 diff -u -r2.2.2.1 Utils.py --- Utils.py 27 Aug 2005 01:40:16 -0000 2.2.2.1 +++ Utils.py 15 Jan 2006 02:50:11 -0000 @@ -16,12 +16,25 @@ import sys import traceback +import syslog +import StringIO + +syslog.openlog('mailman', syslog.LOG_PID, syslog.LOG_MAIL) def _logexc(logger=None, msg=''): - sys.__stderr__.write('Logging error: %s\n' % logger) - traceback.print_exc(file=sys.__stderr__) - sys.__stderr__.write('Original log message:\n%s\n' % msg) + try: + sys.__stderr__.write('Logging error: %s\n' % logger) + traceback.print_exc(file=sys.__stderr__) + sys.__stderr__.write('Original log message:\n%s\n' % msg) + except IOError: + syslog.syslog(syslog.LOG_INFO, 'Logging error: %s\n' % logger) + tbio = StringIO.StringIO() + traceback.print_exc(file=tbio) + syslog.syslog(syslog.LOG_INFO, tbio.getvalue()) + tbio.close() + syslog.syslog(syslog.LOG_INFO, 'Original log message:\n%s\n' % msg) + def LogStdErr(category, label, manual_reprime=1, tee_to_real_stderr=1):

3 5

Re: [Mailman-Developers] Dealing with DomainKeys and DKIM
by Camberwell Jan. 15, 2006

Jan. 15, 2006

Joe Peterson Sat, 10 Sep 2005 12:03:55 -0700 I've recently been testing DomainKeys (http://antispam.yahoo.com/domainkeys) and DKIM (which is supposedly a merging of DomainKeys with Cisco's scheme. I am using dk-milter and dkim-milter with sendmail. What this does is add two header lines to outgoing email that allow the receiver to determine the authenticity of the sender... Anyway, since I run a Mailman system too, I figured this might be a problem. Indeed it is, since the header lines get passed through, and when the check is done, it indicates a failure. DomainKeys recommends mail lists regenerate the keys rather than pass them through. What I tried was pretty simple: Mailman doesn't have to deal with these things itself, but if it strips the old keys from the header, the keys will be regenerated on the way out by the MTA, thereby making the whole process clean. So the receiver of the email can at least verify that the mail came from the host hosting Mailman. I suppose Mailman could also check email on the way in for valid keys if it wanted, but that's another subject... I patched Handlers/Cleanse.py as follows: 49a50,55 > # JGP: Remove all "DomainKeys" type header lines, since we want these > # to be regenerated by the MTA when this message is sent out. We need > # to let new such keys be generated because Mailman alters the message, > # and the old keys would be seen as invalid by the receiver. > del msg['domainkey-signature'] > del msg['dkim-signature'] I wanted to pass this by the developers here and see if: 1) This is a reasonable thing to do (or maybe have an option, or even a way to strip selected headers in the config?) 2) If this is the right place to do it. -Thanks, Joe -------------------------------------------------------------- Good day all, I have recently started using dkim-milter myself, and i have made these adjustments to my Cleanse.py to get around this very problem and it works great, alltho i have another little problem..... When i send a mail to list-owner@mysite, if there is a dkim-signature allready in the header (in my case my mail is signed) my dkim-milter trys to verify it instead of signing it on the way back out to the list owner. i hope that makes sense. basicaly i would like to know what i can edit to remove the dkim-signature from ALL incoming mail, not just mail to be bounced to the list. thanks in advance Martin Airs (Camberwell)

4 5

Re: [Mailman-Developers] Dealing with DomainKeys and DKIM
by Camberwell Jan. 15, 2006

Jan. 15, 2006

Joe Peterson Sat, 10 Sep 2005 12:03:55 -0700 I've recently been testing DomainKeys (http://antispam.yahoo.com/domainkeys) and DKIM (which is supposedly a merging of DomainKeys with Cisco's scheme. I am using dk-milter and dkim-milter with sendmail. What this does is add two header lines to outgoing email that allow the receiver to determine the authenticity of the sender... Anyway, since I run a Mailman system too, I figured this might be a problem. Indeed it is, since the header lines get passed through, and when the check is done, it indicates a failure. DomainKeys recommends mail lists regenerate the keys rather than pass them through. What I tried was pretty simple: Mailman doesn't have to deal with these things itself, but if it strips the old keys from the header, the keys will be regenerated on the way out by the MTA, thereby making the whole process clean. So the receiver of the email can at least verify that the mail came from the host hosting Mailman. I suppose Mailman could also check email on the way in for valid keys if it wanted, but that's another subject... I patched Handlers/Cleanse.py as follows: 49a50,55 > # JGP: Remove all "DomainKeys" type header lines, since we want these > # to be regenerated by the MTA when this message is sent out. We need > # to let new such keys be generated because Mailman alters the message, > # and the old keys would be seen as invalid by the receiver. > del msg['domainkey-signature'] > del msg['dkim-signature'] I wanted to pass this by the developers here and see if: 1) This is a reasonable thing to do (or maybe have an option, or even a way to strip selected headers in the config?) 2) If this is the right place to do it. -Thanks, Joe -------------------------------------------------------------- Good day all, I have recently started using dkim-milter myself, and i have made these adjustments to my Cleanse.py to get around this very problem and it works great, alltho i have another little problem..... When i send a mail to list-owner@mysite, if there is a dkim-signature allready in the header (in my case my mail is signed) my dkim-milter trys to verify it instead of signing it on the way back out to the list owner. i hope that makes sense. basicaly i would like to know what i can edit to remove the dkim-signature from ALL incoming mail, not just mail to be bounced to the list. i have tried the latest version 2.1.7 and it does indeed remove the domainkey signature on mail that is for the list, and my MTA does indeed re insert its own domainkey signature, BUT the domainkey signature is NOT removed for mail to list-owner. how can i remove these headers? thanks in advance Martin Airs (Camberwell)

1 0

Mysql MemberAdaptor and Mailman 2.1.6
by Adrian Wells Jan. 13, 2006

Jan. 13, 2006

3 2

Inactivity deletion of maillist users ?
by Erling Hellenäs Jan. 13, 2006

Jan. 13, 2006

Hi all ! It seems like some kind of automatic unsubscribe would be a nice maillist function. It could relieve much of the burden of keeping the member list up to date from the administrators. 1. There could be an inactivity warning after a configurable time of inactivity. If the user doesn't answer, he is automatically unsubsribed. 2. There could also be a possibility to send an activity check mail to all members. Those who doesn't answer are automatically unsubscribed. Those who are unsubscribed get a polite letter telling that they are welcome back, of course. Erling Hellenäs

8 9

creating a list of moderators
by David Benson Jan. 11, 2006

Jan. 11, 2006

Hi, I'm a site administrator and I'd like to be able to automatically compile a list of 'list moderators' so that I can send them all announcements. I can't find a way to do this in the current version, and I saw similar functionality being requested on the 'wishlist', so I assume that it has yet to be implemented. I'm new to Mailman, but I'd like to try writing a script to do this. Can anyone advise me on how to go about it/where to start? Any ideas? Many thanks! Dave Benson

4 3

A better way of doing templates?
by Barry Warsaw Jan. 11, 2006

Jan. 11, 2006

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

preferred documentation format, sources for documentation in admin/www
by Joost van Baal Jan. 6, 2006

Jan. 6, 2006

Hi, I'd like to document my patch for making Mailman OpenPGP and S/MIME aware ( http://non-gnu.uvt.nl/pub/mailman/ ). I'd like this documentation to integrate nicely with the official Mailman documenation. What is the preferred format for creating documentation? I believe it's LaTeX. However, the sources for mailman-{admin,install,member}.{ps,pdf,txt} are neither in cvs/sf/mailman/mailman/admin/www nor in mailman-2.1.7.tgz . It'd help me if these sources got published somewhere. Thanks, Bye, Joost -- Joost van Baal http://abramowitz.uvt.nl/ Tilburg University j.e.vanbaal(a)uvt.nl The Netherlands

3 3

Mailman 2.1.5 'listinfo' command slow ...
by Christiaan den Besten Jan. 6, 2006

Jan. 6, 2006

Hi all ! Could someone please tell me why the "config.pck"'s of every list is completely read, copy'ed to config.pck.last etc on a '/usr/bin/python -S /usr/lib/mailman/scripts/driver listinfo' call. We have some lists with a lot of recipients which results in a combined size of all config.pck's upto 40Mb. Having to write this much data on a 'simple' (?) listinfo call makes the call very slow (5s or something like that ...). Why does it update the configs? Should it not only read info (list names/descriptions). Perhaps it would be a nice idea to split the config and the recipients in separate files to prevent this ? Or has all this been fixed in upstream versions already? Any hint/tips would be very appreciated! bye, Chris

2 1