Mailman-Developers May 2009

mailman-developers@python.org

14 participants
11 discussions

Mailman 2.1x Authentication LDAP and OpenID - SQL Member Adaptor

by Jennifer Redman

Hello, One of the Systers' Google Summer of Code Projects is abstracting Mailman authentication for use with other application frameworks via LDAP and potentially OpenID, using a SQL Member Adaptor. If anyone has a good round-up of existing code or efforts to do this in MM 2x (using a SQL Member Adaptor) or would be interested in providing some mentoring support to our GSoC student leading the project (particularly with regards to doing things the "Mailman Way"), please let me know. If you are interested in contributing to the project, with either some mentoring or code contributions -- please join our development mailing list - http://www.systers.org/mailman/listinfo/systers-dev. Thanks, Jennifer

12 years, 2 months

Should Mailman provide periodic activity summaries to list owners?

by Stephen J. Turnbull

A quick search didn't find anything, so I'll do a more careful check and if there's nothing I'll add a tracker RFE and a short wiki page of the imagined feature, probably on Monday. Unfortunately, I can't volunteer to implement at this time. Details: I noticed that we've been getting a lot of posts from users who are being quite diligent about following up on their own issues, to the extent of their knowledge and accesses, but for one reason or another are not using the logs. Would it be desirable and feasible to send a periodic (options: daily, weekly, monthly, never) activity summary to list owners (similar to the tracker summaries that many trackers send to associated mailing lists)? If someone's list is having problems, then they could get access via the admin interface, which would simply wrap the text report which would be generated for mailing in an HTML PRE element, making for trivial implementation (once the report itself is implemented, of course). Something like Week of May 17-23, 2009 44 incoming messages processed (42 posts, 2 other) 1 message automatically discarded 2 messages held (1 non-member, 1 spam filter) of which 2 messages were approved 41 messages distributed to members 2 weekly digests produced (maximum size reached 1 time(s)) 20 SMTP errors occurred of which 18 posts handled normally by bounce processing 2 subscription requests (probable backscatter) Abstract of discarded messages From: hormel(a)163.com To: resident(a)whitehouse.gov Subject: We cannot transfer $1 million to you without account information Message-ID: <abc(a)fbi.cia.nsa> Abstract of held messages not configured. Abstract of SMTP errors not configured.

12 years, 2 months

Mailman-2.1.9: User Interface Customization

by Alain Reguera Delgado

Hello, As part of a web redesign I've customized mailman-2.1.9 user interface. I would like to know if these changes are useful for the project somehow. http://wiki.centos.org/WebsiteVer2/WebEnvironment/Mailman Thanks for this great software. Best Regards, -- Alain Reguera Delgado areguera(a)allmail.net -- http://www.fastmail.fm - Access your email from home and the web

12 years, 2 months

Re: [Mailman-Developers] Set cookies for global authentication

by Mark Sapiro

Hopkins, Justin wrote: > >I manage approx 50 discussion lists using the mailman system. The nature >of our organization is that one member is more than likely subscribed to >more than just 1 list. One issue that has come up among the membership >is the desire to authenticate only once and then be permitted to access >the private archives for all lists that they are subscribed to without >logging in again. > >I've noticed that using administrative credentials created a cookie >named 'site' whereas a normal login creates a cookie identifying the >users email address and the individual list. > >Has anyone worked on changing this functionality, or is it planned for >Mailman 3? I've scoured list archives and the internet in general and >haven't found even a hint that anyone is working on this or even feels >like it's worth complaining about. Did you look at <http://wiki.list.org/x/vgAM>? The very first paragraph says in part "Many things that people have been wanting for years will be addressed, most notably a unified user database ...". The unified user database will address this and several other issues involving user email addresses, roles, authentication, etc. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

12 years, 2 months

Re: [Mailman-Developers] Set cookies for global authentication

by Barry Warsaw

On May 15, 2009, at 9:10 PM, Hopkins, Justin wrote: > Has anyone worked on changing this functionality, or is it planned for > Mailman 3? I've scoured list archives and the internet in general and > haven't found even a hint that anyone is working on this or even feels > like it's worth complaining about. This will be the case in MM3, because you'll have just one 'account' under the unified user database. -Barry

12 years, 2 months

Re: [Mailman-Developers] Set cookies for global authentication

by Adam McGreggor

On Fri, May 15, 2009 at 08:10:54PM -0500, Hopkins, Justin wrote: > One issue that has come up among the membership > is the desire to authenticate only once and then be permitted to access > the private archives for all lists that they are subscribed to without > logging in again. > > Has anyone worked on changing this functionality, or is it planned for Hum, we're sort of doing something like that, at least for lists-admin. <https://secure.mysociety.org/cvstrac/rlog?f=mysociety/lists/web-admin/lists…> (<http://is.gd/AO16>) might be a starting point for you. (and also <https://secure.mysociety.org/cvstrac/dir?d=mysociety/lists/web-admin/lists/…> (<http://is.gd/AO1s>)) (In our case authentication works via Apache Basic Auth, unix groups, and password-generation scripts <https://secure.mysociety.org/cvstrac/rlog?f=mysociety/bin/htpasswd_import_u…> (<http://is.gd/AO1Z>) it should be quite trivial to implement using LDAP, too.) -- ``What lawyers call intellectual property is no more than theft from the public domain.'' (Andy Mueller-Maguhn)

12 years, 2 months

Set cookies for global authentication

by Hopkins, Justin

Hey all, I manage approx 50 discussion lists using the mailman system. The nature of our organization is that one member is more than likely subscribed to more than just 1 list. One issue that has come up among the membership is the desire to authenticate only once and then be permitted to access the private archives for all lists that they are subscribed to without logging in again. I've noticed that using administrative credentials created a cookie named 'site' whereas a normal login creates a cookie identifying the users email address and the individual list. Has anyone worked on changing this functionality, or is it planned for Mailman 3? I've scoured list archives and the internet in general and haven't found even a hint that anyone is working on this or even feels like it's worth complaining about. Thoughts? Cheers, Justin J. Hopkins MOBIUS, Internet Applications Specialist hopkinsju(a)umsystem.edu

12 years, 2 months

Re: [Mailman-Developers] [Mailman-Users] Deleting messages from archive....

by Barry Warsaw

On May 15, 2009, at 5:04 PM, Ralf Hildebrandt wrote: > * Mark Sapiro <mark(a)msapiro.net>: >> Charles Gregory wrote: >>> >>> Has anyone ever developed a point-n-click tool to delete >>> a message from an archive, preferably by just eliminating the >>> From/To/Subject and body, but leaving the links intact, with >>> a placeholder message that says "message content removed", etc? >> >> >> Not as far as I know. > > It would totally rule. Especially on python.org, where people regret > posting their full name because "employers tend to google them", and > then come running to us, asking "Please remove my name". > > Fucktards. > > But I like the idea of such a function. I've long thought that all archives should be vended dynamically rather than statically, of course with a cache to improve performance as necessary. This would allow you to do lots of interesting things, such as add links dynamically (e.g. "bug 12345" pointing to your bug tracker), or on-the-fly modification of archive style or anti-spam obfuscation, with the proper cache invalidation. This would also allow you to "delete" a message from the archive, by laying down a marker that causes the program to instead return a "not available" or cleansed message without affecting the underlying data. -Barry

12 years, 2 months

Proposal: option for UTF-8 emails without base64 encoding

by Petr Hroudný

Hi all, due to Python defaults, mailman exhibits strange behaviour when processing UTF-8 emails. When no header/footer is configured, mailman passes UTF-8 emails in original form, i.e. 8bit. However, when either header or footer is configured in mailman, it uses Python's libraries to add them and as a side effect it converts 8bit emails into 7bit base64 encoded ones. This is highly undesirable in some cases. For instance, mailinglist might be used to distribute trouble tickets or other content which is expected to be easily parsable by automated text-based utilities. With base64, emails grow in size by 33 % and such emails are getting much higher spam scores since base64 is typically used by spammers to obfuscate the payload. There are of course much more reasons for not using base64 as the primary encoding method for UTF-8 email. The fix is quite simple and is already widely used by other projects. All that needs to be done is to redefine Python's UTF-8 charset properties, i.e. in every place where you have from email.Charset import Charset you need to add: email.Charset.add_charset('utf-8',email.Charset.SHORTEST, None, None) With such setting, mailman will keep the 8bit encoding also when it's adding header/footer and won't downconvert to 7bit+base64. So I'd like to propose the above addition, at least as a configurable option if there's any fear that enabling it by default could cause some problems. Thanks, Petr

12 years, 2 months

mailman 3: webinterface: prototype (PDF)

by Patrick Ben Koetter

Greetings, following our discussions at the Pycon 2009 Mailman sprint I've come up with first draft of a/the future mailman 3 web interface. The interface has changed a lot. Changes follow these principles: * Simplify interface * Focus on tasks * Order and sort by task recurrance * Reduce information overflow e.g. by hiding help messages * Show help messages as bubbles when selected by user * Remove instructions on using a web from * Use default button texts e.g. "Save" instead of "Submit your changes" See also: <http://wiki.list.org/display/DEV/Rest+client> I've come up with a paper prototype, which you can download in an annotated PDF by clicking at "Mailman webinterface draft" at the following location: <http://wiki.list.org/display/DEV/Information+Architecture> Important The version you can download is _not a design_. It's a grid that creates a structure, puts elements we need on a (HTML) page, orders and groups them following the principles I've outlined above. Please feel free to comment on it and ask questions. I've spent the last 5 days clicking the old interface, thinking and sitting before my current proposal - I just might be blind to my own stupidity or brain dead by now. ;) My goal is to agree on an information architecture, so we can go on and create a design that combines functional requirements and aesthetics. Once we've agreed on a design, we will create HTML templates and then we will put them together with the upcoming REST client. p@rick -- state of mind Agentur für Kommunikation, Design und Softwareentwicklung http://www.state-of-mind.de Franziskanerstraße 15 Telefon +49 89 3090 4664 81669 München Telefax +49 89 3090 4666 Amtsgericht München Partnerschaftsregister PR 563

12 years, 2 months

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 May 2009