Mailman 3 September 1999 - Mailman-Developers

multilingual mailman
by Gerhard Gonter 12 Oct '99

12 Oct '99

Are there any plans to for non-english user interfaces which can be selected individually by the user or at least for a whole list? I would like to help start this effort or help otherwise. +gg -- Gerhard.Gonter(a)wu-wien.ac.at Fax: +43/1/31336/702 g.gonter(a)ieee.org Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria

5 5

Re: [Mailman-Developers] Mailman Customization Guide?
by J C Lawrence 29 Sep '99

29 Sep '99

On Wed, 29 Sep 1999 11:56:13 -0500 (CDT) Kendall Clark <kclark(a)ntlug.org> wrote: > By "document/url archive" I'd like to be able to define a > "library" for a list, a form for submission (even better: a little > xml language that could be cherry-picked from the text of list > messages themselves; but that's "version 2" feature :> ) of URLs > and plain text documents; the url > "http://foo.org/mailman/listinfo/<list-name>/archive would return > a page of the archived links and links to the plain text > documents. Yes, this is a bit duplicative of Pipermail, but it's > also very handy to have stuff organized in a non-archival way (not > thread or time or subject based). I imagine the best way to do > this is to store URLs and glob.glob(<the archive directory>) > pickled and then read them off the disk and build the page. Have a look at phpHoo. It doesn't do exactly what you want, but is workably close. -- J C Lawrence Life: http://www.kanga.nu/ Home: claw(a)kanga.nu ---------(*) Work (Linux/IA64): claw(a)varesearch.com ... Beware of cromagnons wearing chewing gum and palm pilots ...

1 0

Mailman Customization Guide?
by Kendall Clark 29 Sep '99

29 Sep '99

Hi all, First, Mailman is great. Thanks for the work. Next, I want to customize Mailman by adding a "poll" and a "document/url archive" option to mailing lists. "Poll", similar to what eGroups does with this (though they do some dumb stuff here) allows a list member or admin to define an issue and some "multiple-choice-style" options, and then list members register their vote, all of which are tracked. Interface would be something like: "http://foo.org/mailman/listinfo/<list-name>/poll/<polls-by-name or id>/vote" and "http://foo.org/mailman/listinfo/<list-name>/poll/<polls-by-name or id>/results" By "document/url archive" I'd like to be able to define a "library" for a list, a form for submission (even better: a little xml language that could be cherry-picked from the text of list messages themselves; but that's "version 2" feature :> ) of URLs and plain text documents; the url "http://foo.org/mailman/listinfo/<list-name>/archive would return a page of the archived links and links to the plain text documents. Yes, this is a bit duplicative of Pipermail, but it's also very handy to have stuff organized in a non-archival way (not thread or time or subject based). I imagine the best way to do this is to store URLs and glob.glob(<the archive directory>) pickled and then read them off the disk and build the page. I know how to write Python, but I'm not really sure where to dive into Mailman first; what is the preferred way of doing extension work like this is? In other words, I could probably hack at it long enough to get something working for me, but maybe, with a bit of guidance for what these features should look like to be consistent with Mailman's design, I can manage to do good enough work to submit some patches. Thanks. <Kendall/> -- I'll get a bunch of monkeys, dress 'em up, and make 'em reenact the Civil War! Heh, heh, heh! -- Homer Simpson Homer The Great

1 0

Documentation: Admin Guide Draft
by Christopher Kolar 29 Sep '99

29 Sep '99

I have placed the first rough draft of both a list manager's guide and a list manager's quick reference on the web. I would appreciate it if members of the development team took a look at it and commented. I have been preparing documentation for my institution as we roll MM out and we will eventually GPL them once we find out what we need to do. The following documents are currently available for review: 1. MailMan User Guide (for list subscribers) 2. MailMan Administrator's Guide (for list managers, non-technical list owners) 3. List Administrator's Quick Reference (covers 90% of what our help desk has heard from non-technical (faculty) list owners). AT this time all of the documents are ugly, I just need feedback/corrections related to the content. Documents are available at http://www.aurora.edu/~ckolar/mailman Cheers, --chris -- /////\\\\\/////\\\\\ Christopher G. Kolar Director of Instructional Technology Aurora University, Aurora, Illinois ckolar(a)admin.aurora.edu -- www.aurora.edu [PGP Public Key ID: 0xC6492C72]

1 0

Feature request
by J C Lawrence 28 Sep '99

28 Sep '99

I'd be awfully pleased if I could customise the default reject message on a per-list basis. I almost never use the "send administrative messages to..." message, using instead such things as: 1) Pleas trim your quotes 2) Please fix your attributions and/or attribute your quoted text 3) Please place new text below the quote it refers to and trim the quote 4) Please post from an address that does not append advertising to your message 5) Please wrap your lines at 80 columns or less 6) Please see the FAQ 7) Less noise, more signal please etc. Best of course would be the ability to pick from a list of canned customised reject messages. -- J C Lawrence Life: http://www.kanga.nu/ Home: claw(a)kanga.nu ---------(*) Work (Linux/IA64): claw(a)varesearch.com ... Beware of cromagnons wearing chewing gum and palm pilots ...

2 1

List config portability
by J C Lawrence 28 Sep '99

28 Sep '99

How portable are list configs between list names? Specifically: Can I rename a list by changing the name of the ~mailman/lists/XXX directory as long as I also change the MTA aliases and the name of the list in the admin interface? -- J C Lawrence Life: http://www.kanga.nu/ Home: claw(a)kanga.nu ---------(*) Work (Linux/IA64): claw(a)varesearch.com ... Beware of cromagnons wearing chewing gum and palm pilots ...

2 1

Another item for TODO: Accept list
by klm 27 Sep '99

27 Sep '99

> Date: Sat, 25 Sep 1999 02:14:35 -0600 > From: Sean Reifschneider <jafo(a)tummy.com> > To: mailman-developers(a)python.org > Subject: [Mailman-Developers] Another item for TODO: Accept list > > I didn't see anything in the main list admin page for doing this, > so I thought I'd write in to request it be put on the todo list. > There doesn't seem to be an ability to specify a specific "accept" > list. I'm thinking of a list which if non-empty, only posts from > addresses on the list would be accepted. The idea is to prevent > discussion on announce-only mailing lists. If i understand what you're seeking, there's an option on the privacy page for doing this. From the details page: posters (privacy): Addresses of members accepted for posting to this list without implicit approval requirement. (See "Restrict ... to list members" for whether or not this is in addition to allowing posting by list members. Adding entries here will have one of two effects, according to whether another option restricts posting to members. If member_posting_only is 'yes', then entries added here will have posting privilege in addition to list members. If member_posting_only is 'no', then only the posters listed here will be able to post without admin approval. I think the combination with members_posting_only == 'no' amounts to your accept list. > This is certainly something I'd be interested in implementing. > But, I've got to wonder what happened to the other patches I > submitted last week... :-) Ah, this is a problem. It looks like all the core mailman developers are currently tied up enough, so noone can cater to incorporating - or even following, at the moment - mailman developments. Sean, if you would do me the favor of pointing me to the patches - or resend them, just to me - i'll try to take a moment to look them over. (We're considering ways to increase the pool of people with privileges to touch the main development tree _without_ increasing the thrash factor - shepherding, itself, takes time which may be too scarce even for that at the moment, but we need to look at it.) > Or did I just overlook it? Probably the other way around - we did. (This is late vacation season - i was away week before last, eg, and i *know* from sparse discussions w/ other mailman developers time is real tight.) Ken Manheimer klm(a)digicool.com

2 1

Another item for TODO: Accept list
by Sean Reifschneider 25 Sep '99

25 Sep '99

I didn't see anything in the main list admin page for doing this, so I thought I'd write in to request it be put on the todo list. There doesn't seem to be an ability to specify a specific "accept" list. I'm thinking of a list which if non-empty, only posts from addresses on the list would be accepted. The idea is to prevent discussion on announce-only mailing lists. This is certainly something I'd be interested in implementing. But, I've got to wonder what happened to the other patches I submitted last week... :-) Or did I just overlook it? Sean -- It usually takes more than three weeks to prepare a good impromptu speech. -- Mark Twain Sean Reifschneider, Inimitably Superfluous <jafo(a)tummy.com> URL: <http://www.tummy.com/xvscan> HP-UX/Linux/FreeBSD/BSDOS scanning software.

1 0

Hostnames..
by Erik Parker 24 Sep '99

24 Sep '99

Where to the scripts ask to get their hostname from each time? mm_cfg.py ? I have DEFAULT_HOST_NAME = 'discuss.pentax.com' and in Defaults.py DEFAULT_HOST_NAME = 'discuss.pentax.com' Erik Parker eparker(a)mindsec.com

3 6

msg.headers.append('Reply-To: %s\n' % self.GetListEmail())
by Erik Parker 24 Sep '99

24 Sep '99

found this in Deliverer.py msg.headers.append('Reply-To: %s\n' % self.GetListEmail()) Could I re-write that line, and ALL messages leaving mailman would use that reply-to? I don't know how to write python.. how could i make that read something that would make all reply-to's goto pentax-discuss(a)discuss.pentax.com Thanks for your help. If this ever works right before 5pm, you will be life savers. heh. Erik Parker eparker(a)mindsec.com

1 1