| |
W7EES > SYSOP 28.06.26 18:23l 27 Lines 1103 Bytes #999 (0) @ USA
BID : 49186_W7EES
Read: GUEST
Subj: ALLUS? Really?
Path: IZ3LSV<I0OJJ<N2NOV<KC2NJV<K5DAT<WW6Q<W9GM<KA3BVJ<KA3VSP<N8FWD<N9LYA<
W7EES
Sent: 260628/1306Z 49186@W7EES.#NWOR.OR.USA.NOAM BPQ6.0.25
>From w7ees%w7ees.#nwor.or.usa.noam@i0ojj.ampr.org Sun Jun 28 18:19:37 2026
Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0q.1) with SMTP
id AA17063928 ; Sun, 28 Jun 2026 18:19:37 +0200
Message-Id: <49186_W7EES@n2nov.bbs>
>From: w7ees@w7ees.#nwor.or.usa.noam
X-JNOS-User-Port: Circuit (ARECS:N2NOV-7 N2NOV-7) -> Sending message
Can someone explain why some sysops are using the ALLUS, 'at BBS' token? My understanding is that ALLUS is the same routing as
USA. This was discussed in detail back in the 90's. (Read W0RLI's BBS Spec, page 34, Appendix C, Distribution Designators, Bull
etin Distribution Forwarding System.) If you haven't read the document, it's archived on my www.qsl.net/w7ees/Resources/bbs_spe
c.pdf page.
Yes, this is an old document, but it may help newcomers and authors of external forms and systems to understand the foundation
of the BBS network.
Is the token ALLUS formally documented? If so, pass the information on so all sysops can operate on the same page. A network sh
ould be unified, using the same standards, policies and procedures.
73 - W7EES
Read previous mail | Read next mail
| |
