On Mon, 01 Oct 2001 10:31:07 +1000
AE Somerville <[EMAIL PROTECTED]> wrote:
> I was particulalry interested in: 1. How your software stores and
> accesses the mailing list information (List Members,
> Administrators, Moderators, Members).
Currently they are stored as a Python streamed object.
On Mon, 1 Oct 2001 14:55:13 -0400
Greg Ward <[EMAIL PROTECTED]> wrote:
> BTW, this holds for Mailman 2.0 and earlier. I believe Mailman
> 2.1 uses "pickle" (another, more powerful persistence mechanism
> for Python) for list config information.
2.1 implements a plugin and abstraction layer suc
On 01 October 2001, Jon Carnes said:
> > I was particulalry interested in:
> > 1. How your software stores and accesses the mailing list information
> > (List Members, Administrators, Moderators, Members).
>
> The information for each list is stored in a large database file called
> "config.db" w
> I'm currently compiling a list of prospective MLM software for the QUT
> Messaging Project (redesigning the Queensland University of Technologies
> email systems).
>
> We are running a mail system for approx 53,000 users supporting approx
> 1,500 lists. The lists are generated by the Universitie
G'Day,
I'm currently compiling a list of prospective MLM software for the QUT
Messaging Project (redesigning the Queensland University of Technologies
email systems).
We are running a mail system for approx 53,000 users supporting approx
1,500 lists. The lists are generated by the Universities s
