Mailman 3 September 2003 - Mailman-Developers

loginpage
by Marius Herea / Gazduire.ro 28 Sep '03

28 Sep '03

Hi, I have mailman v 2.1.2 and I have no idea how to edit the loginpage for a website. Is there a way to put a condition somewhere in order to show a page defined by me for every list under a domain.tld? Regards, Marius

1 0

Cutting Mailman 2.1.3
by Barry Warsaw 28 Sep '03

28 Sep '03

Okay, I'm going to be cutting Mailman 2.1.3 over the next hour or so. avalon and duke9 are getting their 11th hour updates in, but those will probably be the last. :) -Barry

1 0

bugs in 2.1.2
by ned 28 Sep '03

28 Sep '03

Hello list, i've been poking and prodding mailman for about an hour now...found a few things which could be not seen as secure (although they dont have any real impact...): first there is a XSS (cross site scripting) bug in create.py in Cgi/. just enter "><script>alert("hi")</script>. putting a Utils.Websafe (is that right) shoudl fix it... second small bug in Mailist.Mailist, here's a quick demo: http://mail.python.org/mailman/listinfo/(X * 500). nice little info disclosure hole...easily fixed by restricting lengths on filenames that open() uses. but you already knew that! anyway, nothing a few length checks and some url-fixups wont fix! aapologies too if this should have gone throuhg bugzilla or something...it's late right now and im excited by the grand final tomorrow. regards, Ned Dawes -- http://felinemenace.org/~nd

2 1

Planning for the next release
by Barry Warsaw 27 Sep '03

27 Sep '03

Not that I have any more free time than I used to, but I'd like to start planning for the next major release of Mailman. Over the summer I made some good progress on Mailman 3, but I'm beginning to think that we'll need a MM2.2 release sooner than that. There's a ton of stuff backed up that can't really go into 2.1.x. MM2.2 would be more modest, with no fundamental architectural changes, but hopefully some useful new features nonetheless. So I've started a wiki page to start collecting ideas. I'm not committing to any of them, but we need a place to document and discuss things that might go into Mailman 2.2. Here's the url: http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/MailmanTwoDotTwo Feel free to comment, or add other wish list items. I'll garden the wiki as necessary. -Barry

2 3

Re: [Mailman-Developers] Re: Bounce removal parameters default values
by J C Lawrence 26 Sep '03

26 Sep '03

On Fri, 26 Sep 2003 17:10:35 -0400 Barry Warsaw <barry(a)python.org> wrote: > On Fri, 2003-09-26 at 12:36, J C Lawrence wrote: >> At its core this is an argument between pragmatism and principle. >> >> My principled side says that an alarming number of sites actually do >> use content filters and that they are a reality of email life and we >> should properly handle reality. > I would have thought this was the pragmatic side... >> My pragmatic side says that content filters are inherently and >> necessarily broken and like any other technical brain-damage, >> shouldn't be accommodated. > ...and this was the principled side. ;) Yeah. Damn. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

Re: [Mailman-Developers] Re: Bounce removal parameters default values
by J C Lawrence 26 Sep '03

26 Sep '03

On 26 Sep 2003 11:41:08 -0400 Greg Stark <gsstark(a)mit.edu> wrote: > Deciding an address is invalid on the basis of messages posted to the > list is bogus. Mailman can't know whether the message posted to the > list bounced because the address was invalid, or merely because the > content of that particular message triggered a content-based filter. At its core this is an argument between pragmatism and principle. My principled side says that an alarming number of sites actually do use content filters and that they are a reality of email life and we should properly handle reality. My pragmatic side says that content filters are inherently and necessarily broken and like any other technical brain-damage, shouldn't be accommodated. As always, you get to choose. Currently I'm very happy with the principled side. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

3 2

Trivial mm wording nit
by Skip Montanaro 25 Sep '03

25 Sep '03

I know this is anal, but it bugs me every time Mailman discards a message then sends me a note with this text: The attached message has been automatically discarded. It should be The attached message was automatically discarded. FYI. -- Skip Montanaro Got gigs? http://www.musi-cal.com/ http://www.mojam.com/ Got spam? http://spambayes.sf.net/

4 5

Topic feature request
by J C Lawrence 25 Sep '03

25 Sep '03

I would like to be able to flag specific topics as mandatory. For example "ADMIN:", as a topic, would also go to every user no matter their topic selection. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

unremovable/broken member addresses
by Andrew D. Clark 25 Sep '03

25 Sep '03

Hello all, I've encountered some list member addresses like so (I've substituted the domain name here to protect the guilty): %./list_members some-list bbest(a)goaway.spammer * ben I can't remove a member address like this: %./remove_members -n -N some-list "bbest(a)goaway.spammer * ben" Traceback (most recent call last): File "./remove_members", line 186, in ? main() File "./remove_members", line 176, in main admin_notif, userack) File "/home/services/mailman/Mailman/MailList.py", line 941, in ApprovedDeleteMember self.removeMember(emailaddr) File "/home/services/mailman/Mailman/OldStyleMemberships.py", line 220, in removeMember self.__assertIsMember(member) File "/home/services/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: bbest(a)goaway.spammer*ben Nor does it work by escaping the spaces and/or the *. Doesn't work via the web front end either. Any ideas? -- Andrew Clark Campus Network Programmer Office of Information Technology University of California, Santa Barbara andrew.clark(a)ucsb.edu (805) 893-5311

4 4

lost data files for filebase
by Kory Wheatley 22 Sep '03

22 Sep '03

I'm going these errors in the error log for mailman 2.1 on RED HAT 9 , Python 2.2 Here's the errors Sep 22 23:02:47 2003 (26500) lost data files for filebase: 1064243291.09331+d473693c98d3d8d8b251c45f7b36ef47009afbc1 Sep 22 23:02:47 2003 (26500) lost data files for filebase: 1064243292.06778+eb8df709a22017653552825e42ddaadebc2ed27f Sep 22 23:02:47 2003 (26500) lost data files for filebase: 1064243296.583845+a33368a7b5929d3651a9857237d3b0bf73e47599 Sep 22 23:02:47 2003 (26500) lost data files for filebase: 1064243345.690969+cba1a653bc7c104a639147d8f5d68156d603db0f Sep 22 23:02:47 2003 (26500) lost data files for filebase: 1064243382.699338+ee1a8616c1dd74b2b38d6a5a00cbd900611aa4b6 Sep 22 23:02:47 2003 (26500) lost data files for filebase: 1064243559.031534+d70b87da87bd35dc7a8ed376b0914a447ed50284 Sep 22 23:02:47 2003 (26500) lost data files for filebase: 1064244308.556132+47da5be929c7e4895caa21e917fa4233352ee932 Sep 22 23:02:47 2003 (26500) lost data files for filebase: 1064244559.5556411+dc264fc752653b09650609afc700738a1b6ca57 Sep 22 23:02:47 2003 (26500) lost data files for filebase: 1064257065.58655+b5f6b7eb3a0808f81e3776ffa2dbcfed58318cad Sep 22 23:02:47 2003 (26500) lost data files for filebase: 1064288683.7312551+3d3abeb8c3649419b571a98a87f524e1d2ff667

1 0