[FADCA] H Fwding

[bud thompson]

Technically - in the case of SP and ST messages... you can have as many
target BBS on the list for those <CALL> and/or <@BBS> fields as needed, but
once a message is passed to any BBS on the target list,  the software should
not try to pass the message to another BBS on the list; else we end up with
duplicate messages.  In the case of SB messages, you can propose those to
any number of BBSs you want using the G list - which may take a lot of RF
time- but once a BBS has the MID#nnnnn for a message it will give you a -
(minus sign) for that message in the response to the bid and your BBS will
not try to send it to that forwarding partner again.  Also, each BBS can
build a reject file that will R(eject) any G <field> message that is not
wanted.  (R returned to the bid.)

Ultimately we need to develop telnet routing for the Trash Bulletins and use
RF routing as primary for SPs and STs. This is not to say all SBs are
TRASH - we just need to develop a list of G <fields> that are OKAY...

bud

PS - Okay... my feelings won't be hurt if someone wants to show this is not
the way it works! It's just the way I think it is suppose to work!

Let's make it right!


----- Original Message ----- 
From: "W4RP" <w4rp@spydercat.com>
To: <fadca@mailman.qth.net>
Sent: Friday, February 20, 2004 16:27
Subject: RE: [FADCA] H Fwding


> My question is how redundancy is achieved.
>
> I would think that to pass all #JAX messages, for example, I should pass
> them to N0IA as well as W4ZAX and perhaps XKF as well to ensure that it
will
> get through -- ONE of them will get there and be their first.
>
> I can see bud passing w4rp messages to w4rp bbs only,  but should only
pass
> #MLB messages to me  (W4RP BBS) --- could be that the telnet link is
down --
> and if passed all #MLB messages to N4XEO -- I would get them on the RF
side.
>
>
>