Mailman 3 June 2001 - Mailman-Developers

forwarded message from Guido van Rossum
by barry＠digicool.com June 14, 2001

June 14, 2001

For those of you concerned in these sorts of issues, this is great news. I've done some limited testing of MM2.0.5 and MM2.1alpha against Python 2.0.1 and it all seems to work. I think we can finally put the GPL-compatibility issue to bed. -Barry

1 0

why no user disable of the monthly reminder?
by J.D. Laub June 13, 2001

June 13, 2001

Please CC me on replies as I'm not a mailman-developer subscriber... In my inbox this morning I found several monthly reminders for various lists to which I'm subscribed. I'm responsible enough to save off a list's "Welcome" message, and I need no monthly reminder. Why does Mailman penalize me with setting up & maintaining filter rules to clobber the unnecessary reminders? Is adding a user level configuration of this option in the works? If not, here's a request for one.

9 18

adding anonymity features?
by Yanuar Nugroho June 12, 2001

June 12, 2001

Hi there! A short introduction: I am a MSc student in Information Systems Engineering at UMIST, Manchester, UK, who is now doing my dissertation on applying anonymity in mailing list communication to examine the communication behaviour among participants. The idea is basically hiding the identity of the sender so that the communication will be based on what is being communicated and not who is communicating in the group. The possible usage in the future might range from decision making within organisation (or network/group) to conflict resolution. I am interested in Mailman (GNU milist mgt system) to be developed or equipped with anonymity features. Is it possible to add "anonym feature" in Mailman? Can you give me a clue from where should I start? I have with me now the source-code of Mailman (written in Python) together with its documentation. Cheers, Yanuar ps. I am an NGO activist in Indonesia, where the possible advantageous usage of this feature might be huge among many NGO/non-governmental/non-commercial group that exist. Yanuar Nugroho http://yanuar-nugroho.mainpage.net http://www.yanuar-n.net ---------------------------------------- PG. Stud. MSc. Information Systems Engineering, Dept. of Computation, UMIST, Manchester - UK

1 0

site-wide list configuration...
by Chuq Von Rospach June 11, 2001

June 11, 2001

Just as a bit of an FYI -- I've mentioned in the past that I'd like the ability to "lock down" certain list configuration options based on site-wide standard. Having this feature has become more interesting to me, since I just has a 'situation' where it would have been really useful. I had a list admin decide he wanted to change reply-to to the list. This, despite being told not to change things. So he did. And it got involved in a situation where stuff was posted to the list (by me, in fact) that shouldn't have been because the list was configured different than everything else on the system. And that led to the "why can't we have this?" fight, and it led to a private argument with the list admin (who actually changed it twice), and all sorts of unhappiness. And one of his arguments, of course, was "if you don't want this changed, why do the pages let me"? Don't worry, my hair will grow back. Well, maybe. But take this as a real-world case where splitting out content admin from list admin from site admin and allowing the folks higher up in the hierarchy to delegate or freeze what sub-admins can do. Because while it's nice to think everyone will play nice and follow instructions, in the real world, it doesn't always happen. -- Chuq Von Rospach, Internet Gnome <http://www.chuqui.com> [<chuqui(a)plaidworks.com> = <me(a)chuqui.com> = <chuq(a)apple.com>] Yes, yes, I've finally finished my home page. Lucky you. It's a thankless job, but I've got a lot of Karma to burn off.

2 1

Mailman v2.0.5
by Murali Kumar June 11, 2001

June 11, 2001

Dear Sir, Congratulations for Your Excellent Software ( Mailman v2.0.5 ) Your software has been selected in the category "Email ------> Email List Management" by our editorial team. Come to http://www.softlandindia.com/Linux/ Onestop site for Softwares; See the Winners. Our Home Page: http://www.softlandindia.com/Linux/ Your Excellent Software Located at: http://www.softlandindia.com/Linux/EmailList.htm Editors Pick Logo at: http://www.softlandindia.com/editorspick.gif Please inform us of updates and trial versions. We would like to review them early for our readers. Thanking You, With Kind Regards, K.Murali Kumar Webmaster www.softlandindia.com Email Ids: info.softlandindia(a)hotpop.com and softlandindia(a)hotpop.com ---------------------------------------------------------------------------------------------------------------- To unsubscribe, send email to: softlandindia(a)hotpop.com SubJect: Unsubscribe

1 0

Re: [Mailman-Developers] Re: [Mailman-Users] Re: MIME messages
by J C Lawrence June 9, 2001

June 9, 2001

On Fri, 8 Jun 2001 10:49:01 -0700 Chuq Von Rospach <chuqui(a)plaidworks.com> wrote: > On Friday, June 8, 2001, at 10:21 AM, Darrell Fuhriman wrote: >> J C Lawrence <claw(a)kanga.nu> writes: >>> baggage than I consider justifiable for an MLM or for sites >>> which have no other reason (or wish) to run Zope. >> I couldn't agree more. Zope is a very complex piece of software >> that I have no use for on my site, and no wish to maintain. > There are very good reasons for doing someething like this, > especially for those crazy people like me trying to integrate > mailman into a larger, integrated environment. But the point is a > good one -- this stuff should be optional, so people running > "lake-witchita- friends(a)witchita.org" don't need to hire someone > like me to install mailman.. There's also the small fact that the environment one is integrating into may be (is in my case) Zope unfriendly. Requiring Zope would require me to move away from other designs I'd much rather not. > The default should be simple and straightforward -- and the key is > to build interfaces and APIs that allow users to plug in > replacement modules for functionality... Quite. -- J C Lawrence claw(a)kanga.nu ---------(*) http://www.kanga.nu/~claw/ The pressure to survive and rhetoric may make strange bedfellows

2 1

thank you guys for showing me the way.
by extacyhigh152＠webtv.net June 9, 2001

June 9, 2001

1 0

Re: [Mailman-Developers] Re: [Mailman-Users] Re: MIME messages
by J C Lawrence June 8, 2001

June 8, 2001

On Thu, 7 Jun 2001 23:32:03 +0200 Norbert Bollow <nb(a)thinkcoach.com> wrote: > Please explain... what is bad about Zope? Zope is not inherently bad. It is however a large and complex product that comes with significant baggage, and especially more baggage than I consider justifiable for an MLM or for sites which have no other reason (or wish) to run Zope. -- J C Lawrence claw(a)kanga.nu ---------(*) http://www.kanga.nu/~claw/ The pressure to survive and rhetoric may make strange bedfellows

4 3

admlogin.html missing in the current cvs (2.1a2) for i18n
by Fil June 8, 2001

June 8, 2001

Just to mention that the admlogin.html template is missing in the languages templates (I had to copy it from templates/en/admlogin.html to templates/fr/admlogin.html). -- Fil

1 0

Re: [Mailman-Users] Re: MIME messages
by barry＠digicool.com June 7, 2001

June 7, 2001

[I've moved this discussion over to mailman-developers. -BAW] >>>>> "JCL" == J C Lawrence <claw(a)2wire.com> writes: JCL> Ability to unroll quoted printable. JCL> Ability to unroll base64 encoded plain text. JCL> Ability to strip blocks from message parts that match JCL> stated patterns (eg Yahoo/MSN/Hotmail ads, corporate CYA JCL> statements, etc). JCL> Ability to filter on line length (eg hold for moderation or JCL> auto-discard/reject). Some of this will be added to mimelib when I get a chance. On the plus side, Python 2.1 and the future 2.2 has some nice support for all this via its unicode codecs. I.e. in the Python CVS there's now a codec for quoted printable so you can essentially say something like: subject = msg['subject'].decode('quopri') if your subject header is quoted as per RFC 2047. I've only played around with this stuff a little bit, to get a feel for what you can do, so I haven't thought about APIs or doing the actual coding yet. The downside is that I'm still targetting Mailman 2.1 at Python 2.0, so some of these features may not be available. Also, just some quick thoughts on de-mime-ing, which also address some things that Chuq has brought up, re: regexp filtering, auto-discarding, etc. I'm of the opinion that regular expression predicates alone aren't going to cut it, and that anything more complex is just way way too complicated to attempt to expose through an email or web interface. Complexity is already our enemy, IMHO. So what I'm envisioning is an extensible architecture, a la the message pipelines, where each filter is implemented in a separate Python module, conforming to a particular, yet-to-be-defined API. Mailman will provide a bunch of canned defaults, like "strip-mime-leaving-only-text/plain" or "match-vbs-attachments". There will probably be some kind of mix-in model for describing the action to take when a filter module matches. Then the admins can choose which filters they want, and what order they want to run them in. I'd actually envisioned something like this for the delivery pipeline, but that (giving admins control) has turned out to be not as necessary. Even this may turn out to be too complex, so there may be yet another level of abstraction that a site admin can glom together, so that a list admin would be presented with a limited set of `rhythms', `themes', or `styles' that they can pick and choose from. I've thought about a similar mechanism for list themes, like "announce-only list" or "read-only mirror list". The point is that there's a lot we can do very cleanly at the Python level, but that the more configurability we expose at the web/email interface, the less usable it becomes, IMHO. So, I'm thinking seriously about ways to preserve the power Mailman can provide to the Python hacker while employing abstractions to reduce the cognitive load on the list administrators and users. -Barry

5 7