Mailman 3 March 2008 - Mailman-Developers

Documentation status?
by A.M. Kuchling 13 Mar '08

13 Mar '08

What's the status of the Mailman documentation, and where is the master copy now? The LaTeX source for the docs isn't in the Bazaar repository, beyond a copy in the Japanese translation (./messages/ja/doc/mailman-member.tex). The wiki page at http://wiki.list.org/display/DOC/Mailman+2.1+List+Administrators+Manual says "I (Terri) am currently in the process of importing the 2.1 documentation from latex," but there are many missing sections. Is the plan to migrate everything into the wiki? And where does the current LaTeX master live? --amk

7 24

Enhancing the bounce log
by A.M. Kuchling 13 Mar '08

13 Mar '08

I'd like to produce improved bounce statistics from Mailman's logs; for example, I'd like to track, per message, how many recipients there were and how many of them bounced. This means the logs need to include the message ID. Most of Mailman's logs (smtp, post, vette) include the ID, but the critical missing piece is the bounce log. To close the loop, I'l need to extract the ID of the message that was bounced. (The message ID of the bounce message itself isn't useful, and may not even exist; qmail's bounces apparently don't have IDs.) How should I write the code to extract the ID? Looking through the bounce test messages, there are various formats so we'll need several functions, similar to how there are several bounced-address parsers in Mailman.Bouncers. Should I: 1) add a extract_message_id() function to all of the modules in Mailman.Bouncers, which currently just have a process() function? 2) have a new package, Mailman.Bouncers.MessageId or whatever, that has several modules, analogous to the existing bounce analysis? 3) have a bunch of analysis functions in one module, and a single master function that tries all of them? I think 3) is the simplest course, but not too simple to be workable. Looking at the test bounces, finding the message ID is much simpler than finding the bounce address; searching for a small number of strings such as 'Original message follows' will often find the original headers. Can anyone see a reason that the more complicated 1) or 2) would be necessary? (I'll start a branch for this too, aimed at getting the change into 2.2.) --amk

2 4

Re: [Mailman-Developers] Fwd: Feedback for mailman developers
by Stephen J. Turnbull 13 Mar '08

13 Mar '08

Adrian Bye writes: > Is the code incomplete? Yes, as far as I can tell. As I wrote before: > > BTW, a look at the patch suggests it's incomplete; I couldn't find any > > templates for headers and footers, nor documentation for how to > > generate the 1-click unsubscribe button. > Please, stop looking for reasons why not to do this I'm not a Mailman developer yet, and I was looking for a reason for this to be where I start. I didn't find it in the patch itself, and in the meantime I found something I have a strong personal interest in doing. Sorry; I hope you have better luck with Barry (who's the assigned developer), Mark or Tokio. Steve

11 18

Referencing internal list names in TOC templates
by Lindsay Haisley 12 Mar '08

12 Mar '08

I mentioned this before, about a year and a half ago, but I don't know if it ever got any notice, since it's not in the 2.1.9 code. Please excuse me if this is already in the pipeline and scheduled for a future version. I just came on it again after a Gentoo Mailman upgrade which made me rebuild everything. If one is modifying Mailman TOC templates, as is necessary, for instance, when implementing the Namazu search engine or working with PHP code in templates, it can be extremely useful, and sometimes quite necessary to know the "internal" name of a list. This is easily done by adding one line to HyperArch.py: --- HyperArch.py.orig 2006-10-16 20:25:22.000000000 -0500 +++ HyperArch.py 2006-10-16 20:28:35.000000000 -0500 @@ -752,6 +752,7 @@ listname = mlist.internal_name() mbox = os.path.join(mlist.archive_dir()+'.mbox', listname+'.mbox') d = {"listname": mlist.real_name, + "internal": mlist.internal_name(), "listinfo": mlist.GetScriptURL('listinfo', absolute=1), "fullarch": '../%s.mbox/%s.mbox' % (listname, listname), "size": sizeof(mbox, mlist.preferred_language), This allows one to use "%(internal)s" as a replacement token in template code. -- Lindsay Haisley | "In an open world, | PGP public key FMP Computer Services | who needs Windows | available at 512-259-1190 | or Gates" | http://pubkeys.fmp.com http://www.fmp.com | |

1 0

Re: [Mailman-Developers] [Mailman-Users] Mailman topic duplication
by Mark Sapiro 12 Mar '08

12 Mar '08

Prashanth wrote: > > When i add same topic repeatedly it keeps adding (i >could see topic duplications), Is this a bug? If I type the same thing twice If I type the same thing twice and my MUA allows it, is it a bug? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

A couple of possible fixes to Mailman 2.1.9
by Lindsay Haisley 12 Mar '08

12 Mar '08

These are a few things I found while debugging my Mailman installation after the Gentoo mailman ebuild maintainer brought PREFIX and VAR_PREFIX in line with the Linux standard FSH. The changes are distribution-neutral but fix a couple of issues that crop up when PREFIX != VAR_PREFIX. check_perms_grsecurity.py is a contrib piece, but should be patched as follows: @@ -132,8 +132,8 @@ print file print "\nEnsuring that all config.db/pck files are owned by Mailman" - cdbs = glob.glob(paths.prefix + '/lists/*/config.db*') - cpcks = glob.glob(paths.prefix + '/lists/*/config.pck*') + cdbs = glob.glob(paths.var_prefix + '/lists/*/config.db*') + cpcks = glob.glob(paths.var_prefix + '/lists/*/config.pck*') for file in cdbs + cpcks: stat = os.stat(file) var_prefix isn't defined in paths.py, but probably should be. Adding: var_prefix = 'whatever ...' after line 31 in paths.py takes care of this, and var_prefix can be set by the autoconf/configure process in the install. ~mailman/bin/update may need to be patched as follows: @@ -344,7 +344,7 @@ # a new one there # tmpl_dir = os.path.join(mm_cfg.PREFIX, "templates") - list_dir = os.path.join(mm_cfg.PREFIX, "lists") + list_dir = os.path.join(mm_cfg.VAR_PREFIX, "lists") b4_tmpl_dir = os.path.join(tmpl_dir, mlist._internal_name) new_tmpl_dir = os.path.join(list_dir, mlist._internal_name) if os.path.exists(b4_tmpl_dir): I may be out to lunch on this one, but it got my attention. Does the use of PREFIX for the lists directory here apply to a legacy version of Mailman ("pre-b4")? If so, then perhaps this isn't an error. -- Lindsay Haisley | "Everything works | PGP public key FMP Computer Services | if you let it" | available at 512-259-1190 | (The Roadie) | http://pubkeys.fmp.com http://www.fmp.com | |

1 0

Recipients list in mailman
by Prashanth 10 Mar '08

10 Mar '08

Hi, I need to change the way mailman creates the list of mail ids to deliver the mail, I tried locating the code which creates the list of mail-id of a mailing list to send message but failed. Is there any function or a code which creates the list of mail-ids to deliver mail, it would be helpful if someone can tell me the exact location where mailman does that. -- regards, Prashanth http://munichlinux.blogspot.com

2 1

Re: [Mailman-Developers] [Mailman-Users] [Mailman-Announce] Updated message catalogs needed for Mailman 2.1.10
by Brad Knowles 10 Mar '08

10 Mar '08

On 3/10/08, liste yoneticisi wrote: > (An explanation to all: I just asked if there is anyone who > responsible for Turkish translation of Mailman, attended to these lists > from Turkiye.) This is a question that is better asked on the mailman-i18n mailing list. That's where all the Internationalization folks should be hanging out. -- Brad Knowles <brad(a)shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>

1 0

Updated message catalogs needed for Mailman 2.1.10
by Mark Sapiro 10 Mar '08

10 Mar '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If you are a language champion or otherwise responsible for a Mailman translation, please get the updated 2.1.10 message catalog for your language to me as soon as possible. Mailman 2.1.10 has been in beta for 3 months now, and I have received very few updated translations. I am planning to release what I hope will be the final beta release of 2.1.10 in a few days. This would be a release candidate rather than a beta if I had more updated translations. Thank you for your understanding. - -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFH0xyZVVuXXpU7hpMRAo1aAKDYiS/wpexcQJqNPi+d0GLK6o2x0gCfTo/Z 24bhI96yktpfx97nDC3XH48= =PH4r -----END PGP SIGNATURE-----

2 1

2008 Pizzigati Prize
by Barry Warsaw 06 Mar '08

06 Mar '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I realize that I've been remiss in announcing this. My apologies. I have been awarded the 2008 Pizzigati Prize for Public Interest Computing for GNU Mailman. http://www.pizzigatiprize.org/ I am deeply honored to win this prize because I believe very strongly in Mailman's role in helping people communicate and organize. I want to thank all of you who have supported me and Mailman over the years, and I want to let you know that I am as excited as ever about where Mailman is going. One of the most satisfying aspects of this project for me has been meeting you, the users, developers and contributors to Mailman, both online and face-to-face. I'm looking forward to meeting the Pizzigati family and having some time to spend with them learning about Anthony's remarkable life, sadly cut too short. So again, thank you all and I'm looking forward to the next 10 years of GNU Mailman! Cheers, - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkfPLpcACgkQ2YZpQepbvXGgwwCbB/PjbX7rSiI0xwKjJ7jPpjgJ kuMAoIfeC0j0+4f8l0GEOp2gYc7a+8MI =Y7nZ -----END PGP SIGNATURE-----

2 1