Hi Francois,
FM> These flags seem to be authorized worldwide.
The Nodelist segment HEADER and TRAILER portions are unique for each ZONE,
that is why the trailer you quoted is valid for YOUR Zone, but those flags are
NOT valid in THIS Zone.
For comparison, here is the nodelist trailer taken from the Zone 3
Nodelist.337. I have edited out much of the comments otherwise it would go on
for many more pages, but ALL the acceptable (in Zone 3) flags are listed -
=========================================================================
;
;S
;S The following flags define special operating conditions:
;S
;S Flag Meaning
;S
;S CM Node accepts mail 24 hours a day
;S MO Node does not accept human callers
;S LO Node accepts calls only from valid listed node
;S numbers in the current FidoNet Nodelist
;S
;S The following flags define modem capabilities supported:
;S
;S Flag Meaning
;S
;S V21 ITU-T V21 300 bps full duplex
;S V22 ITU-T V22 1200 bps full duplex
;S V29 ITU-T V29 9600 bps half duplex
;S V32 ITU-T V32 9600 bps full duplex
;S V32b ITU-T V32bis 14400 bps full duplex
;S V33 ITU-T V33
;S V34 ITU-T V34 28800 bps full duplex
;S
;S H96 Hayes V9600
;S HST USR Courier HST up to 9600
;S H14 USR Courier HST up to 14400
;S H16 USR Courier HST up to 16800
;S MAX Microcom AX/96xx series
;S PEP Packet Ensemble Protocol
;S CSP Compucom Speedmodem
;S ZYX Zyxel series
;S VFC V.Fast Class
;S V32T V.32 Terbo
;S
;S NOTE: Many V22 modems also support Bell 212A.
;S
;S If no modem flag is given, Bell 212A is assumed for 1200 bps
;S systems, ITU-T V22bis is assumed for 2400 bps systems.
;S
;S V42 ITU-T LAP-M error correction w/fallback to MNP 1-4
;S V42b ITU-T V.42 LAP-M plus V.42bis BTLZ data compression
;S MNP Microcom Networking Protocol error correction
;S
;S MN No compression supported
;S
;S XA Frontdoor <1.99b, Frontdoor 2.02+, Dutchie 2.90c
;S Binkleyterm >2.1, D'Bridge <1.3, TIMS
;S XB Binkleyterm 2.0, Dutchie 2.90b
;S XC Opus >1.03
;S XP SEAdog
;S XR Opus 1.03
;S XW Fido >12m, Tabby, Trapdoor[1]
;S XX D'Bridge 1.30, Frontdoor 1.99b
;S
;S None QMM
;S
;S [1] With default file request processor enabled. If run with an update
;S request capable processor, the correct flag is XX.
;S
;S Gx..x Gateway to domain 'x..x', where 'x..x` is a string
;S of alphanumeric characters.
;S
;S #01 Zone 5 mail hour (01:00 - 02:00 UTC)
;S #02 Zone 2 mail hour (02:30 - 03:30 UTC)
;S #08 Zone 4 mail hour (08:00 - 09:00 UTC)
;S #09 Zone 1 mail hour (09:00 - 10:00 UTC)
;S #18 Zone 3 mail hour (18:00 - 19:00 UTC)
;S #20 Zone 6 mail hour (20:00 - 21:00 UTC)
;S
;S Currently authorised user flags in Zone 3:
;S
;S IP User-flags:
;S
;S The IP-user-flags consist of two parts:
;S
;S A basic transport and an optional non-standard port,
;S separated by a colon.
;S
;S IBN[:24554] BinkP protocol
;S
;S IFC[:60179] Raw protocol as used by ifcico
;S
;S ITN[:23] Telnet protocol.
;S
;S IVM[:3141] Vmodem protocol
;S
;S IP General flag for special protocol
;S specifications, if the other IP-flags
;S are not relevant.
;S
;S IMI Mime encoded
;S ISE SEAT encoded
;S ITX TransX compatible
;S IUC UUencoded
;S IEM Everything not defined by the aforementioned individual
;S flags
;S
;S T?? A flag used to described limited hours of operation of a
;S FidoNet mailer. See FSC-0062 (rev. 3) for specifics.
========================================================================
So you can see that the flags you have available there are different from what
we have available.
Cheers.............pk.
--- Maximus/2 3.01
2320/38
* Origin: Another Good Point About OS/2 (3:772/1.10)
|