Hello all!


NEver had to stumble into this teritory before, as when I was a member of more than one network for awhile I was mail-only. THat net folded by the time I moved and started operating a bbs.

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


Been combing docs and so far as I can tell this appears to be the only option if I want everything to be copacetic with the other network if users post to these echoes.

Regards,
Richard
... Amazing how much tape is on a 10" reel when it's not.
--- timEd 1.10.y2k+
* Origin: Radio REscue net operations BBS (1:116/901)

NEver had to stumble into this teritory before, as when
I was a member of more than one network for awhile I
was mail-only. THat net folded by the time I moved and
started operating a bbs.

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

You will need to define some things in each of the areas that are part of the other ftn. The custom origin line, specifying which (alternate) address to use
in that area should do the trick for Max. Now, you may need to have a seperate
Squish control file for outbound, etc., depending on what you are trying to do.... It's been a while since I had an alternate FTN address configured in this BBS for actual usage....

Been combing docs and so far as I can tell this appears
to be the only option if I want everything to be
copacetic with the other network if users post to these
echoes.

Regards,

Good luck.....

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Richard Webb wrote in a message to all:

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

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

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

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

This has worked for me for years now.

Later,
Sean

--- timEd/2 1.10.y2k+
* Origin: Outpost BBS - Douglasville, GA - 770-489-1561 (1:18/200)

Sean Dennis wrote in a message to Richard Webb:

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

That's as I figured, easily enough done. Just a hnice simple solution with squish/timed for this, thought Max might have one too and I was overlooking it.
Regards,
Richard
... Braille: support true literacy for the blind.
--- timEd 1.10.y2k+
* Origin: Radio REscue net operations BBS (1:116/901)

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

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

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

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

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:

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

<path_to_messages_that_use_different_origin>\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
* Origin: Top Hat 2 BBS (1:343/41)

Mvan Le wrote in a message to Richard Webb:

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.

Yes, but Maximus puts an origin line on a message already, so squish doesn't. THe custom origin line works, just do it once, mark my block after the first time and paste. Just hoping somebody knew of a global solution. Three extra keystrokes after the first area is defined <g>. NO biggie.

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.

There ya go! THat would be cool. <NOte to coders <g>.
Just define it once for a given message division.
That's one reason I haven't bothered with divisions yet.
Btw, it's one feature I liked that was added since my days sysoping 2.01 wb. Just haven't seen the need for it yet. EVentually when we're telnet ready I'm going to implement some of the other features that are basically designed for tech support type boards etc. My objective: A user of the system who's handling an emergency situ IF he/she has to hand it off to somebody else it's easily enough done. That's for later on though <G>.



Regards,
Richard
... Preparation, knowledge, and discipline can deal with any form of danger. --- timEd 1.10.y2k+
* Origin: Radio REscue net operations BBS (1:116/901)