[FADCA] Re: Packet & NTS Traffic/BBS & NTS data

Thu, 19 Feb 2004 17:46:13 -0500

Deltona

Yes, we will have to re-learn some old stuff and then we'll remember it
worked screwy 15 years ago, and find some work-arounds for sure.  - It is
still going to work screwy as the software hasn't changed!   If we are going
to cover the state with LAN BBS - we'll have to get along with the software
we have - and once we get it working it will serve our purposes.  The hope
is that eventually someone will write new software ('Jeff', where are you?)

                               NTS MESSAGING SCREW UP #1

ON FBB BBS, IF AN ST MESSAGE IS READ BY ANY USER THE STATUS FLAG IS RESET TO
"Y" MEANING IT HAS BEEN READ.

WORK AROUND circa 1990

1.  Packet BBS users will need to learn not to R(ead) an NTS messages on a
BBS unless they intend to process it.
2.  NTS BBS users will need to learn to R(read) an NTS message even if the
flag is Y and determine if the message should be processed no matter.
3.  Anyone who R(eads) an NTS message and processes it must come back and
K(ill) the NTS message so it won't be processed/delivered a 2nd time.
4.  BBS sysops can summarily edit the message and change the status back to
N, but that will certainly insure a duplicate processing/delivery in many
cases.

We can't blame the software - it won't be changed, so we have to work with
it.  The NTS packet gurus can be responsible for this one.

                     MESSAGE ROUTING SCREWED AROUND THE BARN

An example is that last week I REPLIED to a message on my BBS sent to me by
WB4KGY@WB4MOZ.#WPBFL.FL.USA.NOAM.  Today I received a note regarding unread
mail from KP4IG in Puerto Rico - the message for
WB4KGY@WB4MOZ.#WPBFL.FL.USA.NOAM got to him, but he can't forward it! Yes,
probably some BBS in Louisiana still forwards messages for #WPBFL to Puerto
Rico because it worked okay 15 years ago... BUT NOT NOW!  It is likely my
FBB sent it to N4ZKF or W4JAX and then it went to WB4TAX in Louisiana (or
something like that)... my BBS should not have sent it anywhere but to N4XEO
BBS.. so I need to work on that!

WORK AROUND

We must establish in-state BBS message routing to stay within the state.  It
is too early right now to have all that worked out.. but each BBS sysop must
start working on it, especially those who have telnet forwarding partners
outside of the state. DO NOT SEND MESSAGES WITH H-ROUTING INSIDE FLORIDA
OUTSIDE THE STATE.

At least that is a beginning.

We need someone who has a lot of BBS forward file configuration experience
to jump in and take command and show us what to do and be available in
sidebar to help out.

Who will that be?

Solve the first problem:

Q: How do I insure that a message SP W4RP@w4rp.#melb.fl.usa.noam only goes
to W4RP BBS when I forward to him via telnet rather than N4ZKF or W4JAX?

Solve that one and you have a job!

73,
bud N0IA

bud

----- Original Message ----- 
From: "David Calder" <[email protected]>
To: <[email protected]>
Sent: Thursday, February 19, 2004 08:24
Subject: RE: [FADCA] Packet & NTS Traffic

>
> Once read it appears to be read (not forwarded). Why read it if
> your not going do
> anything with it. Leave it to someone who can and will take care
> of it.
>
> Also, a good bbs sysop watches his bbs and makes sure the
> messages get where they
> are supposed to be. Don't blame the software.
>
> Dave

----- Original Message ----- 
From: "Charles S Schuman" <[email protected]>
To: "Bud Thompson" <[email protected]>
Sent: Thursday, February 19, 2004 12:24
Subject: BBS & NTS data

> I dragged out an old bulletin and updated it for my station.
> Some ZIPS added some changed.
> I hesitate to add those previously covered by OZS... even though I now
> serve his area.
> There are no NTS packet operators in Marion Co and only one in Citrus.
> The problem is... NTS operators deliver by phone & sometimes do not have
> toll free access to those station codes.
> I remember getting a list from someone regarding the phone # he/she
> could deliver to.
>
> Do we factor that into the equation? If so that means we need input from
> the NTS community AND the BBS SysOp.
>
> In another vain... I'm not too thrilled about the Swap file idea. It
> sort-ah defeats the original  ZIP@NTSxx format. However is does take the
> loop-the-loop process out of forwarding.
> Dang!   All this feels familer! I Guess after almost 20 years we are
> comming back to where we were or use-to be.
> Is this Good? :-\
>
> <<Charlie>>
>
>