| |
I0OJJ > PACKET 25.02.25 23:33l 93 Lines 3899 Bytes #999 (0) @ WW
BID : 194_IR0AAB
Read: DJ6UX GUEST
Subj: Re; RE: Hierarchical (P, T) vs Flood Area (B) Messages
Path: DB0FHN<DB0RKB<DK0WUE<DK0WUE<K7EK<GB7RJJ<VK5LEX<VE3KPG<VE3TOK<IR0AAB
Sent: 250225/2223Z 194@IR0AAB.ITA.EU LinBPQ6.0.24
Hi,
> The problem is that not all BBS software works the same. Should it? Maybe.
Since the mid 1980s the F6FBB software obtained a reasonable
synthesis of the WA7MBL and W0RLI ideas on forwarding rules
and the pertinent setup on its DOSFBB; those rules remain
perfectly applicable to nowadays PBBS software.
But nothing, they need to reinvent the Babel tower and so
vanishing all the previous efforts.
> A lot of things have changed since 2012 and as is admitted in the document routing to the state level has some ambiguity and so certain accommodations must be made. It specifically says in that same document:
That document is the one of 1994 only with the date changed.
> "A simplified method would be to add the whole Hierarchical string to every message. This would remove any confusion."
No, it should be clear that the Hierarchical address is ONLY
for SP (personal) messages and not for SB (bulletins)
Essentially, for bulletins the rules are ONLY the following (from
my personal notes):
-------------------------
In example 2 the message being sent is a Bulletin. In
Bulletins the hierarchy of the address is expressed in both
the TO (expressing an AREA OF INTEREST) and the @ (expressing
the GEOGRAPHICAL ADDRESS) namely, the portion of the address
wich identifies the DISTRIBUTION AREA.
This will forward using the address found after the @ PBBS
field.
Send Bulletin -- -------------- TO portion of address
| | wich identifies the
| | AREA OF INTEREST
| |
| | ----- @ portion of address which
| | | identifies and limits the
- --- -- --- -- GEOGRAPHIC DISTRIBUTION
SB AAAAAA @ DDDDDD
The TO portion identifies the AREA OF INTEREST, which
usually is a topic such as DX, HELP, FBB, SAT, etc. It helps
identify the population of persons who have an interest in
reading the Bulletin.
The @ portion of the message narrows the distribution of the
Bulletin to specific GEOGRAPHIC AREAS (e.g. ITA, ILAZ, IPIE
etc.) and, in a few rare cases to a broad *topical area* (e.g.
SYSOP, AMSAT).
Some examples:
-------------
SB HAMFST @ ILAZ advertise ham for a HamFest in Lazio
SB DX @ ITA a DX bulletin for distribution (whole ITA)
SB USERS @ I0OJJ Information for users of I0OJJ PBBS
SB JNOS @ WW for Hams concerned in JNOS (whole world)
----------------------------------
> And this is what my BPQ installaton appears to require. I believe that BPQ recognizes down to the
> country element, but not the state due to the possibility of conflicts.
The BPQ is one of the modern Babel towers :)
> Specifically, TOPIC@TX goes nowhere in a BPQ system without special forwarding entries. And TOPIC@TX.TX and TOPIC@STX.TX is recognized as an email address and sent to the RMS forwarding, if one exists. Unfotunately, things like @AMSAT, @ARRL, etc. don't get routed automatically in BPQ either and special routes must be entered if the sysop wants to forward those.
Ditto. Internal distribution of messages into a complex
situation as of that of USA and others must be coordinated
inside each Country ... the States/Provinces are apart.
> Regretfully, SYSOP@NY.USA.NOAM or any type B with a full hierarchical address is not handled in all software and it is your choice to accomodate the address or not. BBS systems are evolving and a sysop can choose to change with it or not.
>
>
> In my opinion sysops just have to adapt for their own software. One size does not fit all in this world.
How many have the necessary instruction for manage their
proper situation?
> 73,
> Mark
--
73 and ciao, gustavo i0ojj/ir0aab/ir0eq
non multa, sed multum
Read previous mail | Read next mail
| |
