BJ>> Thanks for the note.  The area is probably still marked 
 BJ>> for sysop only, because at one time it was a sysop 
 BJ>> support echo (years ago), with such restictions.  The 
 BJ>> archive is there.....  When I get the chance I'll have 
 BJ>> to re-read the current echo discriptionn and then open 
 BJ>> it up, if allowed....

 JD> I made very few changes to the rules.  For ease and simplicity.

This could be *several* years ago......  I switched to Maximus
1. from running OPUS....  It's been a long time.....  And
burried some place is the old source code to Maxumius 1.0.

 ac> I wasn't aware of such a rule, although it seems to have existed since
 ac> at least June 1998 according to my archives (and most likely before
 ac> then).  What's the rationale behind that, anyway?

As a sysop restricted echo, we could discuss the issues we had with running
Maximus, including security issues, without letting regular users know what
holes one might be trying to plug.  There haven't been many over the years,
but there has been one or two security issues that did come up......  

 ac> One wonders how a would-be Maximus user with problems setting up their
 ac> system could've possibly obtained support through this echo without
 ac> already being a sysop.  Catch 22?  Strange rule!

In some ways, catch 22.  In other ways, once someone was trying to get
Maximus setup, they usually already had a mailer setup, and so were a
"sysop" per the nodelist, and had access to this echo.

Take care.....

Bob Jones, 1:343/41

--- Maximus/2 3.01