Re: It's back

[Jason L Tibbitts III <tibbs @ hpc . uh . edu>]

Yet another snapshot.  Grab it at
<URL:ftp://ftp.hpc.uh.edu/pub/majordomo/Majordomo-0.0199801210.tar.gz>.

This one has basic support for attachment_rules, so that when certain MIME
types are encountered, Majordomo can consult the list owner or reject the
message outright.  There is also support for sending rejection messages for
failed postings if the user is a subscriber with the appropriate flags set.

The full set of default access routines is in place, so if you don't set
anything in access_rules things basically happen as you expect them to.
There are still plenty of tweaks necessary, though.

Finally, I added this to the TASKS list.  Anyone interested?

Beautify the logfile code:
  The current logging code was written for simplicity; this results in
  a logfile which is neither pretty nor human-readable.  While the
  intention is for Majordomo to be able to make reports from its
  logfile, there is is still reason to make it browseable by those who
  want to look at the file itself.  Many recommendations for the
  common logfile format were made, but I know little of it and I am
  unsure that it can handle all of the specific data elements that
  Majordomo keeps.  This needs to be investigated and better code
  needs to be written.

 - J<