Mailman-Developers June 2007

mailman-developers@python.org

7 participants
11 discussions

Re: [Mailman-Developers] [Mailman-checkins] [Branch ~mailman-coders/mailman/3.0] (no title)
by Barry Warsaw 28 Jun '07

28 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Mark, thanks for fixing this. Just a couple of quick comments... On Jun 28, 2007, at 1:27 PM, noreply(a)launchpad.net wrote: > @@ -100,20 +101,25 @@ > os.chown(path, -1, MAILMAN_GID) > else: > print > - # All directories must be at least rwxrwsr-x. Don't check > the private > - # archive directory or database directory themselves since > these are > - # checked in checkarchives() and checkarchivedbs() below. > + # Most directories must be at least rwxrwsr-x. > + # The private archive directory and database directory > must be at > + # least rwxrws---. Their 'other' permissions are checked in > + # checkarchives() and checkarchivedbs() below. Their > 'user' and > + # 'group' permissions are checked here. > + # The directories under qfiles should be rwxrws---. Their > 'user' and > + # 'group' permissions are checked here. Their 'other' > permissions > + # aren't checked. > private = config.PRIVATE_ARCHIVE_FILE_DIR > - if path == private or (os.path.commonprefix((path, > private)) == private > - and os.path.split(path)[1] == > 'database'): > - continue > - # The directories under qfiles should have a more limited > permission > - if os.path.commonprefix((path, config.QUEUE_DIR)) == > config.QUEUE_DIR: > + if path == private or \ > + (os.path.commonprefix((path, private)) == private > + and os.path.split(path)[1] == 'database'): This is probably better style: if path == private or ( os.path.commonprefix((path, private)) == private and os.path.split(path)[1] == 'database'): # then... targetperms = PRIVATEPERMS It eliminates a backslash (always ugly ;) though it kind of begs for the 'then...' comment because of the way the columns line up. > + targetperms = PRIVATEPERMS > + elif os.path.commonprefix((path, config.QUEUE_DIR)) \ > + == config.QUEUE_DIR: > targetperms = QFILEPERMS Similarly, this removes the need for a backslash: elif (os.path.commonprefix((path, config.QUEUE_DIR)) == config.QUEUE_DIR): targetperms = QFILEPERMS You probably can't do much better without storing config.QUEUE_DIR in a local variable. Cheers, - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRoP6mHEjvBPtnXfVAQL8qQP9GZzd1T5xdGGmcWvGR+lpZPUpZPGWJhCq 7yH54o8E45pBisH6LVVJR3KoS7/xfJGevj3t/tQ6gLgiOsdeiLaTWQJ05UBBiHAr r8+7FWWgUrc84o7EvkhgXXsqCVT/iFTW1yVWmlsVGLm0ezdl6oOPTcrpJ2biA63S 3Hn//tQKi2o= =rA0r -----END PGP SIGNATURE-----

2 2

News -> mail should remove the mailing list tag
by Frederik Vanderstraeten 23 Jun '07

23 Jun '07

Hi When synchronizing a mailing list and a newsgroup, if a tag is enabled for the mailing list, but disabled for the newsgroup, the tag gets added properly when copying the message to the mailing list. But it doesn't get removed when copying responses back to the newsgroup. For an example of the problem, see this screenshot: http://img.photobucket.com/albums/v35/Benoit/projectowners_snap.png I'd be willing to fix this myself, but I never looked at Mailman's code before, so could someone help me with the whole development process. I don't even know what branch I should make my patch on. Thanks Frederik Vanderstraeten

3 3

Re: [Mailman-Developers] [Mailman-checkins] [Branch ~mailman-coders/mailman/2.1] (no title)
by Mark Sapiro 22 Jun '07

22 Jun '07

noreply(a)launchpad.net wrote: >-- >(no title) >https://code.launchpad.net/~mailman-coders/mailman/2.1 > >You are receiving this branch notification because you are subscribed to it. >To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman/2.1/+subscription/mailma…. Hmmm... If I go to <https://code.launchpad.net/~mailman-coders/mailman/2.1/+subscription/mailma…> and log in, I am told Sorry, you don't have permission to access this page. You are logged in as Mark Sapiro. It occurs to me that this message/URL is for mailman-checkins(a)python.org to unsubscribe from branch notifications, so the lack of permission for msapiro makes sense, but the original message leads to this confusion. Can these notices be sent out without this message? -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Reminder about bzr flag day
by Barry Warsaw 22 Jun '07

22 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a reminder that I plan to switch the official Mailman branches to Bazaar hosted on Launchpad sometime tomorrow. I may start doing this as early as midnight my time (UTC-4). I'll send out a message when the deed is done. If you have commit privileges on the Subversion repository, you will need to apply for membership in the Mailman Coders team on Launchpad: https://launchpad.net/~mailman-coders These Mailman wiki pages contain more information: http://wiki.list.org/display/DEV/MailmanOnLaunchpad http://wiki.list.org/display/DEV/MailmanBranches The branch names will change once the conversion is complete. Notifications of diffs pushed to the official branches will continue to be sent to mailman-checkins. Expect to see a big merge on the trunk branch after the conversion is complete. :) Cheers, - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRnqZW3EjvBPtnXfVAQJs9gQAn/aRSJ9lVWo4f9H/NtJ4+YJL4ubCNz63 5Pgr5FZpzRYZarTwLRtOm2hwUZgu8JAp0plq6Xc+jzLBWn8csc1l2B/pPbREocs7 a04YG/nhDe7E7XJvE7a01KoXfiUFRxpi6nkdYs3sGSz56kXE7F/SK0fhifSAu9u8 wRBH2IwXw1A= =LtQ8 -----END PGP SIGNATURE-----

1 1

Scrubber changes for Trunk
by Mark Sapiro 16 Jun '07

16 Jun '07

I have found a couple of Scrubber issues in 2.1.9 which I have patched on the Release_2_1-maint branch. These issues involved a message with a message/delivery-status part which parses into text/plain sub-parts with None payloads, and a message with an improperly RFC 2047 encoded filename which had a trailing null byte. In looking at how the Release_2_1-maint patches port to the Trunk, I've seen some other problems. I have developed the attached Scrubber.patch.txt patch for the Trunk which I think fixes the problems I saw in 2.1.9 and fixes the other problems I see. I would appreciate others, particularly Tokio, looking at this to see if it seems correct. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Bazaar branches
by Barry Warsaw 15 Jun '07

15 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks, I've started a page that we should use to collect 'interesting' bazaar branches of the Mailman source code. There will be two sections, one for the official branches and one for unofficial branches: http://wiki.list.org/display/DEV/MailmanBranches Right now it lists the branches being sync'd automatically to upstream svn, and a branch I've been working on to improve the Elixir data model. This latter will get merged to the 3.0 branch on Flag Day, when the official branches will move to being owned by the mailman-coders team. Still, what's described should be enough for you to start getting a feel for what it will be like to work with the Bazaar branches. I'm pretty sure that any branches you make now will be easily merged with the official branches after Flag Day. Enjoy, and feel free to ask questions! - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRnL2HnEjvBPtnXfVAQL0jQP/Ux7pa0vzm2BzfftOK23k7aOdp1qpoSDe 77SiLyS9QI07cZQwwKd7H7VQR9xmS/GdBAZIoo5Vq6sOD7dvsdBJQCjb1RXwkZrG rZ738R4M0wLRxgw0gL/+KpC9C1tCU1+HWwItGF7hV8gV/ufJ8v0Mdyu3g+wF2trB IXuzUaxTrWQ= =NoiY -----END PGP SIGNATURE-----

1 0

Re: [Mailman-Developers] [Mailman-i18n] Mistake in Brazilian Portuguese Translation
by Barry Warsaw 07 Jun '07

07 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jun 7, 2007, at 9:59 AM, Clytie Siddall wrote: > (Barry, is the Jira tracker ready for use yet?) Sadly, I haven't had time to do the migration, and I haven't been able to rustle up any volunteers to help. Maybe I should just give up and start fresh in Jira. We'll have to live with two trackers for a while, but maybe it will be easier to ask folks to migrate individual relevant bugs rather than do the entire tracker in one shot. I'm open to thoughts on how we can move to Jira sooner. This may make even more sense when I announce my roadmap plans (hopefully this week). Cheers, - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRmgZYXEjvBPtnXfVAQLzzAQAhgt/dV22QQ+DTkC6RvjrawN3XDBG7Pk9 z+9nB5rNWD4u8h+FhrDQRhZsQ82W5aw5Oneguqig/N0HC4PzQRYs5MAAoBwZSrCS RZhR5rDXEgBpVlPN2wVAisIjG40yQNhCXC+1+YmWgnWhqigmY+S9Ui6Qqnf2w8cZ Evpp6xsnhc8= =xyrD -----END PGP SIGNATURE-----

1 0

Where to insert additional Attachment-filters in the code?
by Andreas Kahl 07 Jun '07

07 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I have installed Mailman on a Debian for my club for organisational discussions. Some Members don't like attachments, some do. One solution could be a filter copying attachments to a location on my Webserver and sending a link + password over the list. Another could be a filter for several members where they can adjust personally to receive attachments or not. I am not familiar with your code, could you tell me in which .py-File the size of attachments is checked. Do you have any further recommendations to me when trying to implement such a module? Are there already similar modules? Thanks for your help. Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGZrdEq60kmgwCDSARAm6TAKDp3BjuAHnF4Z6yraeR7D9rsVCzlwCg9ln+ 9/sYoOlQNsLwwAtxPLJg4B4= =d4db -----END PGP SIGNATURE-----

2 1

missing the file ACEXML
by tufail muhammad 06 Jun '07

06 Jun '07

dear while isntallation of opendiameter 1.0.7-i the one error come i.e /usr/bin/ld: cannot find -lACEXML this error is not /usr/bin/ld: cannot find -lACE_SSL different error what i should do for installation. thanks _________________________________________________________________ Dont miss your chance to WIN $10,000 and other great prizes from Microsoft Office Live http://clk.atdmt.com/MRT/go/aub0540003042mrt/direct/01/

1 0

More help on the WebUI templating issue
by Alvaro Uría 04 Jun '07

04 Jun '07

Hi all! This is my first mail to the list so, let me greet all of you and just say that I've been reading over here for quite a while now. BTW, with pretty interesting threads. I've been administering GNU Mailman since 2003 and a few months ago started to dig into its design, in the aim of helping you, first with the WebUI templating, and with the idea of continuing in a future with other parts of Mailman. As a way of helping me to understand Mailman, I've created a few UML class diagrams based on MM2.1 (which I hope to improve), http://csl-mmwebui.forja.rediris.es/uml/uml.html ...and I've generated the API with epydoc, http://csl-mmwebui.forja.rediris.es/mailman-api/ In reference to the templating engine, I know you're thinking to use Kid or Genshi... but I've started another approach with Cheetah (http://www.cheetahtemplate.org/), which uses text-based templates. Here you have a very simple test of how Cgi scripts could be rewritten for the creation of web content, http://csl-mmwebui.forja.rediris.es/auria-test.tgz In this .tgz you have: 2 scripts: * Test.py (the one to be run) * TemplateController.py (the one that deals with Cheetah and the templating files, and called by the Cgi scripts) 2 templates: * if 'example.tpl' does not exist, 'error.tpl' is read (if not, a string is returned). BTW, I just wanted to clarify that I understand that only a templating engine will be used for the whole project, but I wanted to give a try to Cheetah and see if it matches in a better way all Mailman needs (including email templates and archives, and making easier to integrate the pages on "corporated sites", allowing to change pageheaders and pagefoots). I didn't say anything before on the list because I haven't been working constantly on this, and because I don't like very much to talk with no other purpose than talking (you know, "talk is cheap...", etc. :-)). Comming back to the WebUI, maybe the most important thing is that most of the i18n that is currently working should also work on any new design. In that sense, I've thought to migrate all to Unicode format (UTF-8) and to join all HTML templates per language in a common one, and instead of having contents like: """ <tr> <td>Username:</td><td><input name="foo" ..../></td> <td>Password:</td><td><input name="bar" ..../></td> </tr> """ ...we could have, """ <tr> <td>$label_foo</td><td><input name="foo" ..../></td> <td>$label_bar</td><td><input name="bar" ..../></td> </tr> """ So, the thing would be to include all this i18n (labels, etc.) to the .po files. For ".txt" files, nothing would change. In summary, only would change "templates/<lang>/*.html", joining them in a common dir like "templates/common/<themeName>/*.html". (Between those "themes", or styles, there could be ones using "<table>" tags and others with "<div>" and using only CSS for the draw...) So, as you can see, all CSS issues would be similar (if not the same) with what you're working right now, what it reduces (or joins) efforts :-) And last (sorry to bother you O:-)), I've started to use bazaar a week ago and I hope to push my work on this on launchpad. What I don't know is if I should create a branch and create subdirectories for different parts in there, or create those subdirectories as branches... :? Thank you very much for reading till here, and hope to help you :-)) Best regards, -- ,____________, .' '. /~~~~^~~~^~^~~~\ / _ /|| \ Alvaro Uría (0x3AD91E72) ; ( } \||D ; <fermat at rigel.deusto.es> | | /\__,=[_] | ; ( |_\_ |---| ; It might look like I'm doing nothing, but \ )| |/ | | / at the cellular level I'm really quite busy. '. | /_ | |.' '------------'

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

Mailman-Developers June 2007