GH> I would like Seal to rad my netmail which it does send my downlinks a
 GH> copy of the reply, then send my uplink a request for the echo if I have
 GH> not already got it, if I have it add my downlinks to the echo.

This is exactly what it does here, and on our net's NEC machine, flawlessly.
(and for years.)

 GH> Seal *must* run on auto pilot, *I do not want to babysit it*.

It does.  You call it when you get new inbound mail, and it'll do it's thing.

 GH> Backup=No

Yes.  Just for a safety copy, if nothing else.

 GH> Tic=C:\BBS\TIC.CFG

If you don't want it doing files, you don't need anything here.

 GH> Alias=AREAFIX,AREAMGR,ECHOMGR,SQAEM

Add "Fastecho" and "GEcho" in there, just
"because".  Remove "SQAEM", since
it'll be pretty rare anyone will "accidentally" address an areafix to that
name.

 GH> Alias=RAID,TIC,TICK,FILEMGR,ALLFIX

Remove these if you don't want it dealing with files.

 GH> ; PROTECTED AREAS
 GH> ;
 GH> ; tag=type,level,locks

Look at what it tells you on the layout of protected areas above, now look
how you have them set up below:

 GH> [ProtectedAreas]
 GH> SHAREWARE_SUPPORT=Yes,  ;I moderate this echo
 GH> DIRTY_DOZEN=Yes,        ;I co-moderate this echo
 GH> ECHOLIST=Yes,           ;Successful Echo List updates
 GH> TERMINAT=Yes,           ;I am a beta-tester here.
 GH> VIRUS=Yes,              ;I am acting Moderator.
 GH> VIRUS_INFO=Yes,         ;I am acting Moderator.

You have it wrong, and besides, why would you protect echos that should be
open to the public?  Protection is mainly to "protect" echos from
being seen
or turned on by people that shouldn't be doing so.


--gary

--- Maximus v3.01