I fully support any development in this area. We developed quite
sophisticated statistics module for our Mail Service and I consider that
there are several aspects in this problem:
- listowners may want to have a feeling of how their lists are used
- the majordomo keepers are willing to understand the overall situation:
How many mail messages are sent via the majordomo server
Which are the "heavy" lists compared to the "light" ones
- this is very important although the measure must be defined:
- number of mail messages
- number of commands issued on the list
- size of archives
- mailing lists which are used on a very seldom based may be
removed (a project finished, etc.)
Which are the commands which are mostly used (subscribe, etc.)
Which is the number of mailing lists
Which is the spectra in the size of mailing lists
(at CERN we have 600 mailing lists from 1 to 2000 entries)
Which are the big mistakes, bounces, etc.
How many times users try to access lists but are rejected due to
How many users are entering majordomo commands
How many users are posting mail messages
Can we group the statistics for sets of mailing lists (which are
naturally linked managed)
How are the trends in the creation of new mailing lists
How are the figures evolving on a
- longer term
I already did such analysis for an IMAP Mail Server by simply processing
the system log files. For majordomo I was planning to do the same thing
here but looking at the initial majordomo log files. I am quite strong in
the multicriteria choice aggregation to compare the usage of some items.
to have a feeling of what we are doing at CERN. With my colleagues we are
scheduling some work here but I would support any initiative if this could
be done in the sources of majordomo itself.
On Thu, 31 Oct 1996, Dave Wolfe wrote:
> [ chris writes: ]
> > Is there a way to gather statistics for list usage. I am aware of the
> > logs and I also know that I can archive every message from every list. I
> > maintain about 25 lists and I would like to be able to monitor the usage
> > of each of the lists.
> Currently there's nothing to capture usage stats, but when Mj gets
> modularized to make it easier to add customization modules, I'd thought
> about an add-in to do that. The problem is that it's no insignificant
> amount of overhead to do the stats file locking, etc. for each posting.
> It would be pretty useless unless a list owner were able to retrieve
> the stats via e-mail (using a password, of course) and maybe a retrieve
> and reset. Then there's the details of exactly what stats need to
> be captured: number of messages, of course, but what else? Some
> possibilities off the top of my head:
> Counts of:
> - messages
> - message (body) sizes, i.e. bytes distributed
> - administrivia bounces
> - taboo header, etc. rejects
> - max size bounces
> - errors returned by MTA
> Also a time stamp when last retrieved and when last reset. Probably also
> when last updated. Another question is how configurable this should be?
> I'd say just enable/disable per list. I see no reason to configure each
> stat type, that's more appropriate for the report generator program that
> uses the stats.
> Comments? Please direct followups to Majordomo-workers.
> Dave Wolfe
Arnaud Taddei tel : +41 22 767 9349
CN Division 513 1-019 fax : +41 22 767 7155
CERN mail: Arnaud.Taddei@cern.ch
CH-1211 Geneve 23 URL: http://wwwcn.cern.ch/~taddei