On Feb 20, 1997 at 16:32, andrew clarke of 3:635/728.4{at}fidonet sez to 
Mike Christian:


>> I have several "local areas" on my point setup. They are
meant to be 
>> read only.

ac> How are these areas configured, out of interest?
I declare them in SQUISH.CFG (my Msged.cfg file uses these declarations
rather than declaring them in Msged.cfg):

EchoArea  Railroad     f:\comms\bt\Msg\RR        -f       1:396/17
EchoArea  FrtCars      f:\comms\bt\Msg\FRTCARS   -f       1:396/17
EchoArea  CNet         f:\comms\bt\Msg\CNET      -f       1:396/17
EchoArea  CPRSOO       f:\comms\bt\Msg\CPRSOO    -f       1:396/17




>> But sometimes they get scanned when I exit MsgEd, I assume because
>> somehow they are included in my tosslog. Perhaps I move a message
>> into an area, I'm not sure what causes the local areas to be 
>> scanned, but they occassionally are.

ac> I can only assume you are writing mail to those areas.  If Msged 
ac> were to have an option to configure an area as read-only, then 
ac> obviously you wouldn't be able to write to it.  Do you want to 
ac> write to those areas, or not?  :-)
Hmm... good point! ;-) I found out what was happening. I was using macros
to move messages from my netmail area to the four mailing list areas. I
guess Msged sees this as entering new messages in those areas, and would
point to them in the tosslog. Now that I have NetManager working, I don;t
seem to have the problem any more. When NetMgr moves the messages they are
moved outside of Msged, so it can't point to them in the tosslog.



ac> Your mail processor shouldn't be exporting local areas.  This is 
ac> why I ask how you have configured these "local" areas, and if they 
ac> are really "local".
Yeah, I think you hit on it there. Instead of declaring them as echoareas
they need to LocalAreas in Squish.cfg.


Thanx,


              **Mike**


 mike.christian{at}nopc.org

--- Msged/386 4.10

SDŽ¯t