Mailman 3 November 2004 - Mailman-Developers

Translation not working?
by Brian Greenberg 16 Nov '04

16 Nov '04

On Mon, 15 Nov 2004 14:00:11 +0100, Christiaan den Besten <chris(a)scorpion.nl> wrote: > Well, > > I have already send him some emails asking the same thing, but no reply :( > > Actually, the translation is there ... it just doesn't show up in the > "confirm subscription" page. Is there anyway I can check if the .po/.mo file > is ok? I've found that the install does not seem to copy over all of the *.mo files. After the make install completes, I do: cd $BUILD_TREE for MAILMAN_MO in $( ls messages/*/LC_MESSAGES/mailman.mo ) do cp $BUILD_TREE/$MAILMAN_MO /usr/local/mailman/$MAILMAN_MO done This seems to fix the problem. Brian. -- Brian Greenberg grnbrg(a)gmail.com

3 2

Offer of help
by Russ Pagenkopf 15 Nov '04

15 Nov '04

Not quite sure where to post this, so I thought I'd send it here. I've just started working with Mailman and when I started to print out the administrator commands with --help I noticed, ummm, a bit of, well, shall we say, inconsistency. :) Now I'm not a python programmer (sigh, another to learn?), but in looking through the files it looks like it would be fairly simple to edit them to a consistent standard. I want to contribute back and this is something I can do. Who and how should I submit these changes? I think a lot of the text descriptions could also be cleaned up and used on the web page, so I'd be happy to do that as well. Russ Pagenkopf

4 4

Mailman with SXIP support, preliminary demo
by Andy Smith 15 Nov '04

15 Nov '04

I posted earlier about my mission to add SXIP support to Mailman, so this is a follow-up on that now that some code is complete. I think I have hit all the areas that needed authentication, although the options area is notably weak as far as integration goes. To use the demo you will need a sxip account on https://demohomesite.com, it is a pretty painless sign up (and it ideally will prevent having to do these kinds of sign ups again). Demo at: http://listserva.beta.sxip.org/mailman/sxip/listinfo (Anybody who would like an admin account to test out that interface is welcome to email me so that I can add their email address as an admin or moderator) Everything should be contained under the /mailman/sxip/ path, if it should fall into /mailman/ I'd appreciate a bug report ;) Current code available at: http://an9.org/data/mm_sxip.tar.gz or in svn at http://an9.org/p/browser/mm_sxip Any comments, suggestions (especially those that include code) are eagerly awaited. - Andy Smith

3 6

New much improved danish translation available
by Tom G. Christensen 13 Nov '04

13 Nov '04

Hi, Over the summer myself and a colleague completely redid the danish translation and it is now *much* improved. All the templates are now translated and so is all of the messagecatalog. I've talked to the Danish i18n champion and he agrees that this new translation should be committed to CVS and replace what is there now. Unfortunately he's not able to do it (no CVS access). Is there anyone here who can help me? -tgc -- Tom G. Christensen - State and University Library - Aarhus - Denmark Email: tgc(a)statsbiblioteket.dk - Tel: +45 8946 2027 - Fax: +45 8946 2029

3 3

scrubber crash due to insanely long filename
by Tomas Lindroos DC 10 Nov '04

10 Nov '04

Hello everybody, I am running Mailman 2.1.5 and noticed this problem with the "senddigests" cron-job. If a message has an attachment with a really long filename, Scrubber.py crashes: --- Traceback (most recent call last): File "/export/mailman/cron/senddigests", line 94, in ? main() File "/export/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/export/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/export/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/export/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/export/mailman/Mailman/Handlers/Scrubber.py", line 240, in process url = save_attachment(mlist, part, dir) File "/export/mailman/Mailman/Handlers/Scrubber.py", line 445, in save_attachment fp = open(path, 'w') IOError: [Errno 36] File name too long: '/var/mailman/archives/private/LISTNAME/attachments/20041007/16a8914c/INSANELY_LONG_FILENAME_WITH_320_CHARS_TOTAL.eml' --- The problem didn't go away without admin intervention, and I suspect that no digest-mail was sent out while the problem persisted. The actual bug seems to be that there is not a try-except-block around the open() call, if the call fails, the Scrubber fails. Perhaps it could be added? To get around this particular problem, I made this small patch to Scrubber.py: --- Scrubber.py~ Thu Sep 30 14:15:19 2004 +++ Scrubber.py Wed Nov 10 11:51:21 2004 @@ -396,6 +396,10 @@ # after filebase, e.g. msgdir/filebase-cnt.ext counter = 0 extra = '' + # check for insanely long filenames + if len(filebase + extra + ext)>=256: + filebase=filebase[:255-5-len(ext)] # 5 chars for extra + while True: path = os.path.join(fsdir, filebase + extra + ext) # Generally it is not a good idea to test for file existance Now, this is not a perfect solution, since the same problem will occur if the string "extra" becomes longer than 5 chars in the while-loop below. Perhaps the 5 should be substituted by min(5,len(extra)) or something... This is not thouroghly tested, I just wanted to get the digests working again, so there may be pitfalls I didn't think of. Someone else with more insight into Mailman could probably implement this better. (How to get 320 chars into a filename? Send an attachment with a 245 char long filename containing a lot of scandinavian or other 8-bit characters in it. Watch the åäö's get mangeled into a strings like 'sE4ISO-8859-1QE4ntF6muutokset2C', and you'll have a lot more than 255 chars in a while...) /skitta -- Tomas 'Skitta' Lindroos. Planerare vid Datacentralen, UNIX-sektionen <skitta(a)abo.fi>, tel.nr. (215)4469

2 1

hooking mailman into bbs forum
by Steel City Phantom 04 Nov '04

04 Nov '04

i am in the planning stages of building a knowledge storage system. i have decided to organize the data and the discussions in a forum type layout and i want an email interaction with the PHP pages on the forum. so my question is this, does anyone know of any effort to port the message archive systems in mailman to MySQL? the reason i want to use mailman is i have used it in the past for various lists and really like its speed and stability. when it comes to a distribution list, i really don't want to reinvent the wheel. i don't want my web server or my JBoss server to have to deal with emailing people every day. i want that to be a third server sitting in the network handling that task. the plan i have been kicking around is my PHP and JBoss systems would automatically create a mailman list for every forum subject. for the users, i will create another interface where they can opt to be emailed all the discussions that happen in the forum. when they opt in, the scripts will create a user for that person in the list. The PHP interface will be set up so when someone goes into the interface to post a topic or reply, it will save it to the database and send a copy to the mailman list. that email that is sent to mailman will have hidden fields in the HTML that will be used if the person replys to the email in order to track the threading and such in the database. up to this point, its easy enough, now the hard part. if someone replys to the email they receive from mailman, how to i get mailman to either post the reply into the mysql database, or another option will be send my JBoss servlet the email formatted into some kind of xml that the JBoss can use to post into the forum. if anyone can point me into a direction to do this, it would help me a lot. i just downloaded 2.1.5 and am starting to find my way around the code, but that will take a while. thanks willie

2 2

Sxip and Mailman
by Andy Smith 02 Nov '04

02 Nov '04

Hey, My name is Andy Smith, I'm one of the open source developers over at Sxip Networks (https://sxip.org), and I've been charged with adding SXIP support to Mailman, initially for our own internal uses but to be released open source and as an add-on to Mailman. SXIP is a protocol for digital identity (Simple eXstensible Identity Protocol) that allows, among other things, single-sign on and secure attribute verification (ssl signing of xml data and whatnot). It's all open source and non-evil, too. It's fairly interesting and if you're interested hit up the site for more info (or just ask). I am mailing this to you folks here on the developers list for two reasons, one, because I'd like to be giving this work over to you (the community) once I am finished, and two, because you all know much more about Mailman than I do in the short time I have been examining the code and any pointers or suggestions you can give me will surely be very helpful. So, the goal of my work is to enable single-sign on for Mailman along the lines of the following scenario: ( "sxip in" = sign on, just using our branding ) - User arrives at a mailman site for the first time, and is presented with an overview of public lists. On the page will be a sxip in button and a paragraph informing the user that he/she will have to sxip in to subscribe to a list or see any non-public lists that he/she might have permission to. - If a user sxips in right there the overview will be updated to to contain checkboxes and other relevant links so that a user can subscribe to any number of lists at the same time, or if they have mod or admin access they would see a couple other options. I'm not totally sure at this point what these options should be. - If a user does not sxip in on this first page and instead clicks on a list to see the list info, he/she will be taken to the list info page, with a similar sxip in button and paragraph. In order to subscribe to a list or get any further, the user will have to sxip in. A "subscribe to this list" link will be provided but it will just force the user to sxip in and then present them with a prompt to confirm that they'd like to subscribe. - Once the user sxips in here, they will be taken back to the list info page but with more options available, including mod or admin links if appropriate to their authentication level. - A user will not need to confirm subscription via an email when subscribing this way, because during sxip in a verified email address (as well as first and last name) will be provided through the sxip in process (this is one of the features of the protocol). How I plan to do this, and please let me know if some of these things seem totally off, I've looked through the code but I may have misunderstood something: - Data will be stored in the same way as the other mailman data, using pickled flat files. * There will be a new file that represents all the admins and moderators on the system keyed on listname, with values consisting of a dictionary of keyed on user email addresses with values containing their authorization level * Note: How to handle list creator privilege? specific "site" key in the root of the structure? * It should be possible to make use of the current password scheme involved with the cookies to associate privileges with a user based on list in this data structure, this has the benefit of allowing the simple overloading of the function that checks the cookie data. See Mailman.SecurityManager for the functions used to handle passwords and check cookies. - User properties will remain in the current format, as will list info, nothing new is required there. - To enable sxipping out, true sessions will have to be implemented, which could be done using code as described at http://starship.python.net/crew/davem/cgifaq/faqw.cgi?req=show&file=faq02.0…, however the code there is not fully secure and sxip out support may not be a priority at the beginning (just let the cookie expire?). - There will be a new set of UI pages once the initial work is done to allow a user to sxip in to a session * A page requesting a sxip in, to be called by the various CGI scripts when a user attempts to go somewhere that requires auth. Overload Mailman.Cgi.Auth.loginpage * List Overview will have to be overloaded to show subscription options once sxipped in * List Info will give admin and mod options when sxipped in * All cgi scripts will have to be checked to be sure they authenticate first - To add a new member during sxipped in subscription will overload ApprovedAddMember in Mailman.MailList to be used automatically by sxipping in - To get the lists that a user belongs to and their privileges, a sweep of the list data will have to be performed, which is a little bit of a performance hit, ideally this could be cached in the future but for now I will just hope the performance isn't too drastically poor. Hopefully this model makes sense, I look forward to any comments or suggestions you may have. - Andy Smith Army of Coding Monkeys MSN: msn(a)anarkystic.com Jabber: termie(a)jabber.org http://anarkystic.com/blog

1 0