Mailman 3 November 1998 - Mailman-Developers

feature request
by Darren Henderson 07 Nov '98

07 Nov '98

It would be nice if administrative users could see a log of list activity. A web page would surfice... even just a grep of the subscribe log in reverse chronological order for their list though it might be handy to see other activity as well, (statistical type stuff...how many posts this week, month, year etc might be interesting though perhaps not of great utility). Perhaps access attempts for both administrative and user accounts to see if any fishy seems to be happening. ______________________________________________________________________ Darren Henderson darren(a)jasper.somtel.com Help fight junk e-mail, visit http://www.cauce.org/

1 0

Another patch
by Greg Stein 07 Nov '98

07 Nov '98

This patch modifies the text in the subscription page. For list-admin-hidden lists, the text erroneously stated that list members could see the member list. -g -- Greg Stein, http://www.lyra.org/

2 1

patch for virtual host lists
by Greg Stein 07 Nov '98

07 Nov '98

Here is a small patch for virtual-hosted lists. The original listinfo.py would correctly filter the visible lists for a virtual host, but the hostnames in the title and page contents were wrong. -g p.s. the patch is against 1.0b6 -- Greg Stein, http://www.lyra.org/

1 0

Mailman 1.0b6
by John Viega 07 Nov '98

07 Nov '98

Ok, 1.0b6 is finally done. I needed some info from Barry, and he sent it this morning, then I wasn't around until a little while ago. I'm going to hold off about a day on a more widespread announcement, just to make sure you guys don't find any big show-stoppers that we missed. You can get it off the home page (http://www.list.org), or at: ftp://list.org/pub/mailman/mailman-1.0b6.tar.gz New in b6: - Archiving is (finally) back in. - Administrivia filter added. - Mail queue mechanism revamped with better concurrency control. - For recipients that have estmp MTAs, set delivery notification status so that only delivery failure notices are sent out, inhibiting 4 hour and N day warning notices. - Now expire old unconfirmed subscription requests, rather than keeping them forever. - Added proposed standard List-Id: header, and our own X-MailmanVersion header. - Prevent havoc from attempts to subscribe a list to itself. (!) - Refine mail command processing to prevent loops. - Pending subscription DB redone with better locking and cleaner interface. - posters functionality expanded. - Subcsription policy more flexible, sensible, and site-configurable. - Various and sundry bug fixes. John

1 0

Re: [Mailman-Developers] mailman's own archives
by Ken Manheimer 07 Nov '98

07 Nov '98

On Sat, 7 Nov 1998, Scott wrote: > Dont think those guys have upgraded their site yet. I doubt we'll see > them updated till the weekend's over, though. (Sorta in between - the bottom of the pages say 1.0b6, 'cause someone incremented the version number between releases, but it's before all the archiving stuff got worked out, so i have the internal pipermail archiving off.) (Ken)

1 0

Re: [Mailman-Developers] mailman's own archives
by Ken Manheimer 07 Nov '98

07 Nov '98

On Sat, 7 Nov 1998, Darren Henderson wrote: > Mailman's archives at python.org appear to have stopped on 11/2. Something > to do with the switch to the new version? Yes! I installed to a different location, and once i was satisfied it was working i decoupled the dynamic stuff (list dbs, archives, locks, etc) - neglecting to consider that the external pipermail archiver we're still using was still looking at the old place. For now i'm using a symlink to keep the external pipermail happy - if i'm right, the archives should catch up the next time the job is run. (When i return from the conference i'll use whatever mechanisms we have - or will have, i'm not sure myself - for processing accumulations in preexisting mbox files. Since scott and john will be around during the conference, one of them will probably speak to these issues...) Ken

1 0

looking for stats
by Ken Manheimer 02 Nov '98

02 Nov '98

Hi, all. I'm going to be presenting a paper on mailman at the python conference in a couple of weeks, and i'd like to be able to answer the inevitable questions along the lines of, "how big a list is being run with mailman?" So i'd like to hear from you if you think you have some really big lists, or an otherwise interesting situation where you're using mailman. (I just ran the mailpasswds script by hand, with some gratuitous printing to see how many distinct subscribers, and we have around 2000 valid, distinct recipients, distributed over 33 lists. The largest individual list is probably jpython-interest, with around 450 members. Hmm - on a sparc 5 running solaris, the passwords job took around 1 hour to run - with 15 seconds total for doing the consolidation of all subscriptions for each address, the rest for sending out the notices.) Ken

3 2