RW> So I've joined another network and wish to make some of those
 RW> echoes available to bbs users.  IS my only option to create a
 RW> custom origin line in each of those areas in msgarea.ctl?
 RW> OTherwise, it appears that my fido address would be used even
 RW> though the other address is declared in max.ctl.

 SD> As the ZC of the "other network" you're in... 

 SD> Yeah, you'll have to make a custom origin line in 
 SD> MSGAREA.CTL for each echo.  Here's an example:

 SD> MsgArea MBBS
 SD>     ACS Normal
 SD>    Desc General BBS Chat
 SD>   Style Squish Echo Pub Alias
 SD>    Path d:\msgs\minbbs
 SD>  Origin 618:618/1 618:618/1 Micronet WHQ - Douglasville, GA
 SD> End MsgArea

 SD> This has worked for me for years now.

Squish has this feature:

          areaname.SQO   This file is used by the Squish tosser to provide
                         a custom origin line for the given area.  If an
                         .SQO file is present for a given message area, the
                         first line in the file will be used as the origin
                         line for messages in that area, overriding the
                         "Origin" setting in SQUISH.CFG.  Squish will
                         automatically add the "* Origin" prefix and the
                         trailing "(zone:net/node)" text.

But you'd have to modify the primary address (-p) for each echoarea
definition which is pointless to your objectives.

If *only* Squish did not append the (zone:net/node) you could do something
like group all your areas under a separate directory in Maximus, and modify
origin lines like this:

\origin.txt:
===================================
This msg is gated from 85:123/456 
===================================

\distribute_origin.bat:
===================================
for i in (*.sqd) do
  copy origin.txt `basename $i`.sqo
done
===================================

Maybe ONE DAY the Origin keyword could be used with a MsgDivisionBegin
declaration to solve all such gating/multizone origin line inconveniences.
I reckon this feature could be implemented in Maximus by 2030. 

Anyway, more pipe dreams for me. 

--- Maximus/2 3.01