FidoNews · Vol 30, No 10 · 11 Mar 2013
The F I D O N E W S Volume 30, Number 10 11 Mar 2013
+--------------------------+-----------------------------------------+
| |The newsletter of the | | |
| | FidoNet community. | | Netmail attach to (POTS): |
| | | | Editor @ 2:2/2 (+46-31-960447) |
| | ____________| | |
| | / __ | Netmail attach to (BinkP): |
| | / / \ | Editor @ 2:203/0 |
| | WOOF! ( /|oo \ | |
| \_______\(_| /_) | Email attach to: |
| _ @/_ \ _ | bfelten @ telia dot com |
| | | \ \\ | |
| | (*) | \ ))| |
| |__U__| / \// | Editor: Björn Felten |
| ______ _//|| _\ / | |
| / Fido \ (_/(_|(____/ | Newspapers should have no friends. |
| (________) (jm) | -- JOSEPH PULITZER |
+--------------------------+-----------------------------------------+
Table of Contents
1. FOOD FOR THOUGHT ......................................... 1
2. FTSC INFORMATION ......................................... 2
Publication: FTS-5001 ................................... 2
3. JAMNNTPD SERVERS LIST .................................... 17
The Johan Billing JamNNTPd project ....................... 17
4. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 18
FidoNet Software References .............................. 18
5. SPECIAL INTEREST ......................................... 23
Nodelist Stats ........................................... 23
6. FIDONEWS INFORMATION ..................................... 25
How to Submit an Article ................................. 25
Credits, Legal Infomation, Availability .................. 27
FIDONEWS 30-10 Page 1 11 Mar 2013
=================================================================
FOOD FOR THOUGHT
=================================================================
Marriage -- book in which the first chapter is written in poetry
and the remaining chapters in prose.
-- Beverley Nichols
-----------------------------------------------------------------
FIDONEWS 30-10 Page 2 11 Mar 2013
=================================================================
FTSC INFORMATION
=================================================================
Publication: FTS-5001
Revision: 4
Title: Nodelist flags and userflags
Author(s): FTSC Members, Administrator and Honoured Guests
Issue Date: 10 March 2013
======================================================================
Status of this document
-----------------------
This document is a Fidonet Technical Standard (FTS) - it specifies
the current technical requirements and recommendations for FTN
software developers, coordinators and sysops of the Fidonet network
and other networks using FTN technology.
This document is released to the public domain, and may be used,
copied or modified for any purpose whatever.
Abstract
--------
Nodelist flags extend the basic nodelist format described in
FTS-5000, allowing a node to provide detailed information of its
operation and capabilities.
Contents
--------
1. Introduction
2. Supersessions
3. Purpose
4. Syntax
5. Normal flags
5.1 Operating Condition Flags
5.2 Modem Connection Protocol Flags
5.3 Session Level Error-correction and Compression Flags
5.4 File/Update Request Flags
5.5 Gateway Flag
5.6 Mail Period Flags
5.7 System Online Flags
5.8 ISDN Capability Flags
5.9 Internet Capabilities
5.10 Robot flags
5.11 Flag Redundancies
6. User Flags
6.1 Format Of User Flags
6.2 Mail Oriented User Flags
FIDONEWS 30-10 Page 3 11 Mar 2013
A. References
B. History
======================================================================
1. Introduction
---------------
The Fidonet Distribution Nodelist (FTS-5000) is a comma-delimited
database, i.e. each node's entry is made up of fields, each of which
has a specific purpose.
While this is a fine system for holding information that all nodes
must have (e.g. node number, sysop name, etc.) it is not well suited
for data that varies wildly from system to system. To accommodate
such data, the flag fields are defined as self-describing and
non-position dependent fields.
This document is a registry of all commonly used flags in Fidonet,
and companion to FTS-5000 in describing the Distribution Nodelist.
2. Supersessions
----------------
This document supersedes and replaces FTS-0005, FSC-0009, FSC-0040,
FSC-0062, FSC-0075 and FSC-0091.
3. Purpose
----------
As with FTS-5000, this document is intended for both developers and
nodelist maintainers to avoid duplication and conflicts. Normal
sysops would also do well to have at least cursory knowledge of the
nodelist's capabilities so they may provide their Coordinators with
all the pertinent detail of their systems.
This document should be considered a guide, and not the final word
on what are and aren't valid flags. There will obviously be an
unavoidable lag between the introduction of new flags and their
inclusion in this document, as well as experimental flags that will
come and go with no official documentation at all.
4. Syntax
---------
Most flags are simple tokens that each occupy a single field and by
their presence or absence in the nodelist, indicate the presence or
absence of a certain feature in the node.
A more recent style is to subdivide the flag field, usually with a
colon (3Ah) to allow for variable data under a common flag. These
are essentially named fields, consisting of the flag itself and its
FIDONEWS 30-10 Page 4 11 Mar 2013
payload as one or more subfields.
Unless otherwise stated, flags are not position or order dependent,
with the exception that User Flags must follow Normal Flags.
5. Normal flags
---------------
5.1. Operating Condition Flags
------------------------------
Flag Meaning
CM Node accepts mail 24 hours a day using all listed methods
ICM Node accepts mail 24 hours a day using all listed TCP/IP
methods, but not all of the other listed methods (such as
PSTN/ISDN) and therefore cannot be CM. See FRL-1017.
MO Node does not accept human callers
LO Node accepts calls Only from Listed FidoNet addresses
MN Compressed mail packets will not be processed automatically
5.2. Modem Connection Protocol Flags
------------------------------------
The following flags define modem connection protocols supported.
Please also read section 5.11 on flag redundancies.
ITU-T (formerly CCITT) Protocols:
Flag Meaning
V22 ITU-T V.22 1.200 bps full duplex
V29 ITU-T V.29 9.600 bps half duplex
V32 ITU-T V.32 9.600 bps full duplex
V32b ITU-T V.32bis 14.400 bps full duplex
V34 ITU-T V.34 33.600 bps full duplex *
V90C ITU-T V.90 Client 56.000 bps asymmetric
V90S ITU-T V.90 Server 56.000 bps asymmetric
Industry standard protocols:
Flag Meaning
V32T V.32 Terbo 21.600 bps full duplex *
VFC V.Fast Class 28.800 bps full duplex
Proprietary Protocols:
Flag Meaning
HST USR Courier HST 9.600 bps asymmetric
FIDONEWS 30-10 Page 5 11 Mar 2013
H14 USR Courier HST 14.400 bps asymmetric
H16 USR Courier HST 16.800 bps asymmetric
X2C US Robotics x2 client 56.000 bps asymmetric
X2S US Robotics x2 server 56.000 bps asymmetric
ZYX Zyxel 16.800 bps
Z19 Zyxel 19,200 bps
H96 Hayes V9600 9.600 bps
PEP Packet Ensemble Protocol
CSP Compucom Speedmodem
* NOTE: maximum possible speed; actual maximum will vary
depending on implementation.
5.3. Session Level Error-correction and Compression Flags
---------------------------------------------------------
The following flags define type of error correction and/or data
compression available. A separate error correction flag should not
be used when the error correction type can be determined by the
modem flag. See section I for details.
Flag Meaning
MNP Microcom Networking Protocol error correction
of type MNP1 to MNP4
V42 ITU-T V.42: LAP-M error correction with fallback
to MNP 1-4
V42b ITU-T V.42bis: LAP-M error correction and
compression with fallback to MNP 1-5
5.4. File/Update Request Flags
------------------------------
The following table shows the flags indicating various types of
file/update requests supported:
+--------------------------------------------------+
| | Bark | WaZOO |
| |---------------------|---------------------|
| | File | Update | File | Update |
| Flag | Requests | Requests | Requests | Requests |
|------|----------|----------|----------|----------|
| XA | Yes | Yes | Yes | Yes |
| XB | Yes | Yes | Yes | No |
| XC | Yes | No | Yes | Yes |
| XP | Yes | Yes | No | No |
| XR | Yes | No | Yes | No |
| XW | No | No | Yes | No |
| XX | No | No | Yes | Yes |
| none | No | No | No | No |
+--------------------------------------------------+
FIDONEWS 30-10 Page 6 11 Mar 2013
The following software is qualified to use the appropriate file
request flag according to information provided by developers:
+-----------------------------------+
| Flag Software Package |
|-----------------------------------|
| XA Frontdoor 1.99b and lower |
| Frontdoor 2.01 and higher |
| Dutchie 2.90c |
| Binkleyterm 2.1 and higher |
| D'Bridge 1.2 and lower |
| Melmail |
| TIMS |
| ifcico |
| mbcico 0.60.0 and higher|
| (via modem) |
|-----------------------------------|
| XB Binkleyterm 2.0 |
| Dutchie 2.90b |
|-----------------------------------|
| XC Opus 1.1 |
|-----------------------------------|
| XP Seadog |
|-----------------------------------|
| XR Opus 1.03 |
| Platinum Xpress |
|-----------------------------------|
| XW Fido 12N and higher |
| Tabby |
| TrapDoor No update processor|
| binkd w/SRIF FREQ processor |
|-----------------------------------|
| XX Argus 2.00 and higher |
| D'Bridge 1.30 and higher |
| Frontdoor 1.99c/2.00 |
| InterMail 2.01 |
| McMail 1.00 |
| T-Mail |
| TrapDoor - Update Processor |
| mbcico 0.60.0 and higher|
| (via IP) |
|-----------------------------------|
| None QMM |
+-----------------------------------+
5.5. Gateway Flag
-----------------
The following flag defines gateways to other domains (networks).
Flag Meaning
Gx..x Gateway to domain 'x..x', where 'x..x` is a string
of alphanumeric characters. Valid values for
'x..x' are assigned by the FidoNet International
FIDONEWS 30-10 Page 7 11 Mar 2013
Coordinator or the Zone Coordinators Council. They
will also adequately distribute a list of valid
values.
5.6. Mail Period Flags
----------------------
The Mail Period Flags indicate compliance with another zone's ZMH.
Since ZMH is mandatory within one's own zone, it is not indicated.
These flags have the form "#nn" or !nn where nn is the UTC hour the
mail period begins, # indicates Bell 212A compatibility, and !
indicates incompatibility with Bell 212A. For example:
Flag Meaning
#02 Zone 2 mail hour (02:30 - 03:30 UTC)
#08 Zone 4 mail hour (08:00 - 09:00 UTC)
#09 Zone 1 mail hour (09:00 - 10:00 UTC)
#17 Zone 3 mail hour (17:00 - 18:00 UTC)
The above listing of the ZMH for each individual zone is only given
for your convenience. It was correct at the time of this writing,
but could be changed at any time by following the procedures
established in Fidonet policy. The FTSC has no role in determining
the Mail Hour of any Zone. You'll find an up-to-date list in the
comments at the end of the Fidonet Nodelist.
NOTE: When applicable, the mail period flags may be strung together
with no intervening commas, e.g. "#02#09".
5.7. System Online Flags
------------------------
The flag Tyz is used by non-CM nodes online not only during ZMH, y
is a letter indicating the start and z a letter indicating the end
of the online period as defined below (times in UTC):
A 0:00, a 0:30, B 1:00, b 1:30, C 2:00, c 2:30,
D 3:00, d 3:30, E 4:00, e 4:30, F 5:00, f 5:30,
G 6:00, g 6:30, H 7:00, h 7:30, I 8:00, i 8:30,
J 9:00, j 9:30, K 10:00, k 10:30, L 11:00, l 11:30,
M 12:00, m 12:30, N 13:00, n 13:30, O 14:00, o 14:30,
P 15:00, p 15:30, Q 16:00, q 16:30, R 17:00, r 17:30,
S 18:00, s 18:30, T 19:00, t 19:30, U 20:00, u 20:30,
V 21:00, v 21:30, W 22:00, w 22:30, X 23:00, x 23:30.
For example TuB shows an online period from 20:30 until 1:00 UTC.
Daylight saving time
--------------------
If a node changes online times with respect to UTC when daylight
FIDONEWS 30-10 Page 8 11 Mar 2013
saving time becomes effective (which would be the case with most
part time nodes), then this is to be taken into account when
assigning this flag. An online times flag assigned to a node should
not be altered for the specific purpose of adjusting due to daylight
saving time, since large difference files (NODEDIFF's) would result
if every node was allowed to do this, e.g. a node used to be online
from 2300 to 0800 in local time, which in winter is UTC, but in the
summer it becomes BST (British Summer Time). This is one hour ahead
of UTC, and the corresponding availability times of a node during
the summer period were 2200 to 0700 UTC. Therefore its online times
flag would have indicated availability between the hours of 2300 and
0700 UTC, the daily time period encompassing both times, so the flag
would be TXH.
5.8. ISDN Capability Flags
--------------------------
Nodelist Specification of minimal support required for this flag;
flag any additional support to be arranged via agreement
between users
V110L ITU-T V.110 19k2 async ('low').
NOTE: some implementations are limited to 9600bps.
V110H ITU-T V.110 38k4 async ('high').
V120L ITU-T V.120 56k async, layer 2 framesize 259, window 7,
modulo 8.
V120H ITU-T V.120 64k async, layer 2 framesize 259, window 7,
modulo 8.
X75 ITU-T X.75 SLP (single link procedure) with 64kbit/s B
channel; layer 2 max. framesize 2048, window 2, non-ext.
mode (modulo 8); layer 3 transparent (no packet layer).
ISDN Other configurations. Use only if none of the above
fits.
NOTE: No flag implies another. Each capability MUST be specifically
listed.
5.9. Internet Capabilities
--------------------------
Basic Syntax
------------
Internet capability flags use the format:
<flag>[:<internet address>][:<port>]
Where <internet address> is:
* a fully qualified domain name (FQDN), or
* an IPv6 address encased in square brackets, or
* an IPv4 address in dotted-quad format, or
* an email address,
depending on the protocol, and <port> is the service port number.
FIDONEWS 30-10 Page 9 11 Mar 2013
<internet address> may be omitted if the address is available in
another field (see below). <port> should be omitted if it is the
default port for that particular service, and is not permitted for
email addresses.
The mailer software is expected to be able to determine whether
<internet address> is an IPv4 quad, an IPv6 encased address, a
host name or email address by itself.
Advanced usage
--------------
Several methods of listing Internet capability flags are widely
used and subject to change at any time. Internet capable software
should provide a suitable manual override mechanism to compensate
for the volatility of the nodelist format, and be able to deal with
prolonged connection failures (e.g. by automatically putting waiting
mail on hold, and notifying the local sysop).
Shorthand flags
---------------
For brevity, a node that lists multiple Internet capability flags
that require the same address may list the address only once, and
specify only port numbers per flag if required.
Ideally, a node should use the flags specifically intended for this
purpose, but that is not always the case. Be prepared to look for
addresses under any flag of the same type.
Multihomed systems
------------------
Multihomed systems or systems that are otherwise reacheable by more
than one address, may - instead of adding another A or AAAA record
to the DNS zone of the host name - repeat the flag(s) carrying the
address with another address.
Example: INA:host1.example1.tld,INA:host2.example2.tld,IBN
This method is not to be used to signal that a system is IPV4 and
IPv6 capable. Additional IPv6 capability should be advertised by
adding an AAAA record to an already listed host name.
Alternate fields
----------------
If the address is not attached to any of the Internet capability
flags, it may be present in another field (see FTS-5000).
Because of this, systems using Internet capability flags should
avoid entering data in such fields that may be mistaken for Internet
related information. For example, a node with an email flag should
FIDONEWS 30-10 Page 10 11 Mar 2013
not use a system name that could be confused with an email address.
DNS Distributed Nodelist
------------------------
"Precompiled" IP connection information may also be obtained from
one of the local or publicly available DNS Distributed Nodelist
(DDN) services. This is documented in FTS-5004.
Indirect Delivery
-----------------
Not all Internet tunneling methods require the originating node and
the destination node to make a direct, realtime connection. Relays
though the FTP or email servers of an ISP may serve as an example.
To avoid unusual delays, nodes using such 3rd party relays should
check regularly for new mail -- daily for non-CM nodes, and hourly
for CM nodes is recommended.
Where multiple protocols are available, the originating node should
select the most direct method, and avoid protocols that may be using
relays.
Standard Flags
--------------
Default
Flag port Description
--------------------------
INA (none) This flag sets the default Internet address used
for any non-email based flag that does not specify
its own. This flag does not carry a port number.
IP (none) Mostly used during the introduction of IP capable
systems to the nodelist, is similar to the INA flag
but may or may not specify an Internet address.
Both usages are deprecated in favour of INA.
IBN 24554 Binkp (FTS-1026 - FTS-1029)
IFC 60179 RAW ifcico (FTS-1024)
IFT 21 FTP (RFC-0959); Note there is currently no widely
accepted authentication scheme for FTP transfers by
Fidonet mailers.
ITN 23 Telnet connection using FTS-1 or any other protocol
designed for classic POTS and modem.
IVM 3141 Vmodem connection using FTS-1 or any other protocol
designed for classic POTS and modem.
Email Flags
-----------
FIDONEWS 30-10 Page 11 11 Mar 2013
To use the flag for any Email method providing for return receipts
(currently ITX and ISE) a node *must* have them enabled and send
such receipts within 24 hours of receiving a file.
Flag Description
--------------------------
IEM Indicates an unspecified mail tunnelling method (old
usage, similar to IP), or sets the default email
address for other flags (similar to INA)
ITX TransX encoding for email tunnelling with receipts
enabled.
IUC uuencoding of mail bundles
IMI MIME encoding of mail bundles
ISE SEAT protocol for Email tunnelling with receipts.
enabled; should always be accompanied by IUC and/or IMI.
The e-mail flags do not carry a port number.
Reliability
-----------
It should be noted that only some of these Internet based methods
(currently IBN, IFC, ITN, IVM, ITX and ISE) can give the sender a
proof of receipt of a file by the addressee, like FTS-0001 does.
Other methods have no guarantee of reliability, so they shouldn't be
used to transmit critical data.
Also, nodelist segment maintainers should take into account the
presence of at least one of these reliable protocols when deciding
on application for Fidonet membership by nodes without a dial-up
connection.
5.10. Robot flags
-----------------
PING
----
Specified as exactly "PING" with no arguments. Nodes flying this
flag will adhere to the following functionality:
1) PING-function:
If a message destined to "PING" arrives at its final destination
and this final destination flies the "PING"-flag, then the
receiving node will bounce the message back to the original sender
clearly quoting all the original via-lines.
If a message destined to "PING" arrives at its final destination
but this final destination does _not_ fly the "PING"-flag then the
message may be deleted from the inbound-queue without further
follow-up.
FIDONEWS 30-10 Page 12 11 Mar 2013
2) TRACE-function:
If a message destined to "PING" arrives at a node which flies the
PING-flag but is merely passing-through to another destination
then the in-transit node will notify the sender of this occurrence
and will forward the original mail unaltered towards its final
destination.
WARNING: the sender's name (in either direction) must *NEVER* be
"PING".
5.11. Flag Redundancies
-----------------------
Only the smallest possible set of flags should be used in each
entry.
Since different people might have different perception of modem
flag redundancies, the FTSC decided to provide a standard table.
The relation "implies" means either that the first protocol
requires all the others as a fallback or that to all practical
purposes all modems which have been manufactured until today (and
conceivably even future ones) implemented the other protocols
anyway.
For example, the protocol V.32bis implies V.32 because it's
required as a fallback; on the other hand, V.32Terbo implies
V.32bis because practically all modems with V.32Terbo also had
V.32bis to connect to existing modems, even though it wasn't
required in the protocol specifications.
V32 implies V22
V32B implies V22 V32
V34 implies V22 V32 V32B
V90C implies V22 V32 V32B V34
V90S implies V22 V32 V32B V34
V42 implies MNP
V42B implies V42 MNP
V32T implies V22 V32 V32B
VFC implies V22 V32 V32B
HST implies MNP
H14 implies HST MNP
H16 implies HST H14 MNP V42 V42B
X2C implies V22 V32 V32B V34
X2S implies V22 V32 V32B V34
ZYX implies V22 V32 V32B V42 V42B MNP
Z19 implies V22 V32 V32B V42 V42B MNP ZYX
Please note also that:
FIDONEWS 30-10 Page 13 11 Mar 2013
. the V90C and V90S flags are mutually exclusive.
. the X2C and X2S flags are are mutually exclusive.
. no modem has at the same time the US Robotics proprietary
protocols and the ZyXEL ones; so, use of any flag in the group
HST, H14, H16, X2S and X2C is incompatible with any of the ZYX
and Z19 flags, and vice versa.
. all X? flags are mutually exclusive.
. the CM flag is incompatible with any of the #??, !?? or T??
flags.
. the CM implies ICM; ICM should not be used unless CM is
impossible.
6. User flags
-------------
It is impossible to document all user flags in use. The FTSC makes
no attempt at it. This document lists those flags which got at
least some kind of official sanction or were deemed of technical
interest by FTSC.
6.1 Format Of User Flags
------------------------
U,x..x
A user-specified string, which may contain any alphanumeric
character except blanks. This string may contain one to thirty-two
characters of information that may be used to add user-defined data
to a specific nodelist entry. The character "U" must not be
repeated, eg, ",U,XXX,YYY,ZZZ" not ",U,XXX,U,YYY,UZZZ". The 32
character limitation is per userflag, not for the total of all
userflags.
New implementations must place a comma after the initial "U" before
the user flags. Some implementations will not place a separating
comma between the "U" and the first user flag, but this practice is
deprecated. Implementations should be prepared to read flags in this
format, and must strip the "U" from the flag before analysis in this
case.
Entries following the "U" flag must be of a technical or
administrative nature. While experimentation of new software
functions using this flag is encouraged, advertisement is strictly
prohibited.
For applications other than those shown, or if you have questions
concerning the use of this field, please contact your Regional or
Zone Coordinator.
Developers should note that the distinction between "normal" flags
and user flags is a non-technical, purely political one. It often
happened that a user flag was "promoted" to regular status, and the
reverse could conceivably happen. It is recommended that, while
parsing nodelist entries, no distinction at all be done between the
FIDONEWS 30-10 Page 14 11 Mar 2013
two categories of flags.
6.2. Mail Oriented User Flags
-----------------------------
Flag Meaning
ZEC Zone EchoMail Coordinator. Not more than one entry in the
zone segment may carry this flag and that entry must be the
current Zone EchoMail Coordinator.
REC Regional EchoMail Coordinator. Not more than one entry in
any region may carry this flag and that entry must be the
current Regional EchoMail Coordinator.
NEC Network EchoMail coordinator. Not more than one entry in any
net may carry this flag and that entry must be the current
Network EchoMail Coordinator of that Net.
NC Network Coordinator. This flag is ONLY to be used by the
Network Coordinator of a net which has split the duties of NC
and Host and the NC does NOT occupy the Net/0 position in the
nodelist.
SDS Software Distribution System
SMH Secure Mail Hub
RPK Regional Pointlist Keeper. This user-flag identifies the
person who compiles the region-pointlist (only 1 entry per
region allowed)
NPK Net Pointlist Keeper. This user-flag identifies the person
who compiles the net-pointlist (only 1 entry per net allowed)
ENC This node accepts inbound encrypted mail and will route it
like other mail
CDP This node will accept points auto-created by the CD-point
software.
A. References
-------------
[FTS-0005] "The distribution nodelist", Ben Baker, Rick Moore.
February 1989.
[FSC-0009] "Nodelist Flag Changes Draft Document", Ray Gwinn,
David Dodell. November 1987.
[FSC-0040] "Extended Modem Handling", Michael Shiels.
February 1990.
FIDONEWS 30-10 Page 15 11 Mar 2013
[FSC-0062] "A Proposed Nodelist flag indicating Online Times of a
Node", David J. Thomas. April 1996.
[FSC-0075] "ISDN capability flags in the Nodelist", Jan Ceuleers.
October 1993
[FSC-0091] "ISDN nodelist flags", Arjen Lentz. October 1995.
[FRL-1036] "IPv6 numbers in the nodelist". March 2010
[Policy] "FidoNet Policy Document" v4.07 - June 9, 1989.
B. History
----------
Rev.1, 19990627: Initial Release.
Principal Author David Hallford
Rev.2, 20000422: new draft by Gino Lucrezi; major changes:
- reorganization of flags classification
- rewrite for clarification of internet connection
flags
- note on difference between "regular" and "user"
flags
- description of flag redundancies
new draft by Gino Lucrezi with input from others
- removed Andreas Klein from authors
- ENC flag
- distinction of direct and indirect IP
connectivity
- requirement for return receipts with ITX and ISE
- additional requirement for IP-nodes with CM flag
- clarification on some flag redundancies
new draft by Gino Lucrezi with input from others
- corrected Z3MH and added note on changing of
ZMHs
Rev.2, 20040904: re-re-draft by FTSC.
- Changed header style
- Added Introduction and Purpose sections
- Added Syntax section
- Rewrite of Internet connectivity section
- Removed IP flag conversions
- Merged IP flags and default ports tables
- Added ifcico to compatibility table
- Fixed Txy flag status (user flag -> normal flag)
- Removed ISDN conversions and redundant 300 bps
limit (specified in FTS-5000)
- Removed 32 character flag limitation
- Removed obsolete flag: V21
- Removed obsolete flag: V33
- Removed obsolete flag: MAX
- Removed obsolete flag: K12
- Updated V?? flags
- Added ICM flag
FIDONEWS 30-10 Page 16 11 Mar 2013
- Added PING flag
- Added flag redundancy table
Rev.3 20130104 - There is no version 3. The above version
20040904 should have been labelled version 3,
but due to a clerical error it was also labelled
version 2. So there are two version 2's. Rather
than attempting to correct the error, which
would probably not have succeeded as it is next
to impossible to recall a file that was hatched
many years ago, it was decided to leave things
as they are, skip version 3 and carry on with
version 4.
Rev.4, 20130310 - Updated the paragraph on DDN in section 5.9 to
reflect that the DDN project is now documented
in separate document FTS-5004.
- Upgraded the description of the MN flag
- Removed reference to port numbers for e-mail
flags.
- Added IPv6 where literal IP numbers are
referenced.
- Removed reference to Z5 and Z6. (#nn flags)
- Added "binkd w/SRIF FREQ processor" to list
of programmes qualifying for XW freq flag.
- Dropped NSMH, RSMH, ZSMH and ISMB. Obsolete.
- Clarified meaning of ITN and IVM flag.
- Various small changes in wording and correcting
spelling errors.
- Added repeating of flags in case of systems
having multiple adresses.
-----------------------------------------------------------------
FIDONEWS 30-10 Page 17 11 Mar 2013
=================================================================
JAMNNTPD SERVERS LIST
=================================================================
The Johan Billing JamNNTPd project
This is a list of known JamNNTPd servers working. They are essentially
the modern version of Bulletin Board Systems.
You connect to them using the email client of your choice and you
don't need any other software installed on your computer -- regardless
of operating system -- but that favourite mail client of yours.
Even smart phones can handle this, giving you the opportunity to get
your daily doses of fidonet on the bus, tram or train on the way to
your job, school or whatever.
Updated 2012-03-11
URL news://felten.yi.org
Join http://felten.yi.org/join.html
NETMAIL Yes, 2:203/2
URL news://the-estar.com:1119
Join http://www.easternstar.info
NETMAIL Yes, 1:123/789
URL news://quinnspost.dyndns.org:60119
Join mailto:eskimo261@bigfoot.com
NETMAIL No
URL news://nntp.rbb.bbs.fi
Join Info in group +GETACCESS+
NETMAIL Yes, 2:221/361
URL news://news.wpusa.dynip.com
Join Info in group +GETACCESS+
NETMAIL Yes, 1:3634/12
-----------------------------------------------------------------
FIDONEWS 30-10 Page 18 11 Mar 2013
=================================================================
FIDONEWS'S FIDONET SOFTWARE LISTING
=================================================================
-=:{ FidoNet Software Reference }:=-
Type: M=Mailer T=Tosser B=BBS D=Door C=Comm/Terminal
P=Points E=Editor I=Internet U=Utility ?=Info
.- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -.
|Software: Author |Type |URL, Contact, Ver, Notes Help Node|
`- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -'
Argus |MI |http://www.ritlabs.com/argus/ 2:469/84
| | argus@ritlabs.com Tel: 373-2-246889
| | v3.210 on Mar 20th 2001
BinkleyTerm XE |M |http://btxe.sourceforge.net 1:1/102
| | v2.60XE/Gamma-6 on Nov 11th 1998
BinkD |MI |http://binkd.grumbler.org/ 2:463/69
| | v0.9.10 on Oct 2nd 2008
D'Bridge |MTCPE|http://www.net229.org/dbridge.htm 1:1/130
Nick Andre |I | v3.8 on July 10 2012
FIDO-Deluxe IP |MPUI |http://www.fido-deluxe.de.vu 2:2432/280
Michael Haase | | m.haase@gmx.net
| | v2.4 on Sep 26th 2003
FrontDoor, FD/APX: |MTPC |http://www.defsol.se 2:201/330
Definite Solutions | | sales@defsol.se 1:1/101
| | v2.26SW & v2.33ml FD, v1.15 APX
Husky Project |MTPUI|http://sf.net/projects/husky/
| | v1.4 RC5 on Apr 24th 2006
Radius |MI |http://radius.pp.ru 2:5012/38
(based on Argus) | | fido5012@zaural.net Tel: 7-3522-469463
| | Last Release: v4.010 on Jan 3nd 2005
Taurus |MI |http://taurus.rinet.ru (Russian) 2:461/70
| |http://www.fidotel.com/taurus (English)
(based on Radius) | | E-mail: taurus@rinet.ru
| | v5.000 alpha on Oct 11th 2004
Tmail |MI |http://www.tmail.spb.ru v2608
| | Website is in Russian only
WildCat! Interactive |MTBEI|http://www.santronics.com
Net Server, Platinum| | sales@santronics.com
Xpress: Santronics | | Tel: (305) 248-3204
Software, Inc. | | AUP 451.1 on April 26th 2004
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
Fidogate |TUI |http://www.fidogate.org
FIDONEWS 30-10 Page 19 11 Mar 2013
| | Martin_Junius@m-j-s.net v4.4.10
FMail |T |http://sourceforge.net/projects/fmail/
| | v1.60.GPL
JetMail: JetSys |TU |http://www.jetsys.de js@jetsys.de
(ATARI ST only) | | v1.01 on Jan 1st 2000
Squish |T |http://maximus.sourceforge.net/
| | Lanuis site redirects to above
| | Squish is part of Maximus.
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
BBBS |BI |http://www.bbbs.net b@bbbs.net
| | v4.00MP on Oct 25th 1999 2:22/222
ELEBBS: The Elevator |B |http://www.elebbs.com
Software Production | | elebbs@elebbs.com
| | v0.10.RC1 on Jun 9th 2002
Ezycom BBS |BT |http://www.ezycom-bbs.com
| | ezycom@amnet.net.au or
| | ezycom_hq@ezycom-bbs.com 3:690/682
| | v2.15g2 on 16 Nov 2009
Hermes II Project |B |http://www.hermesii.org
| | info@HermesII.org v3.5.9 Beta Final
Maximus BBS |B |http://maximus.sourceforge.net/
| | v3.03
| |Archives back online at:
| |http://maximus.outpostbbs.net/
MBSE BBS: |BI |http://mbse.sourceforge.net 2:280/2802
Michiel Broek | | mbroek@users.sourceforge.net
| | v0.60.0 on June 5th 2004
Mystic BBS |B |http://www.mysticbbs.com
| | v1.07.3 on May 13th 2001
Nexus BBS |B |http://www.nexusbbs.net
| | groberts@nexusbbs.net
| | v0.99.41-Beta on Oct 16th 2002
| | [Note: No Longer under active
| | development.]
Proboard BBS |B |http://www.proboard.be
| | v2.17 on Jun 9th 2002
RemoteAccess BBS: |B |http://www.rapro.com 1:1/120
Bruce Morse | | bfmorse@rapro.com
| | v2.62.2SW
Spitfire BBS: Buffalo|B |http://www.angelfire.com/ia/buffalo/
Creek Software | | MDWoltz@aol.com 1:1/150
FIDONEWS 30-10 Page 20 11 Mar 2013
| | v3.6 on Aug 20th 1999
Synchronet BBS |BT |http://www.synchro.net
| | sysop(at)vert(dot)synchro(dot)net
| | v3.10L Beta
Telegard BBS |B |http://www.telegard.net
| | support@telegard.net
| | v3.09g2 SP4
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
Atlantis Software |D |http://www.jimmyrose.com/atlantis/
| | Last Update: August 2004
Cheepware |DU |http://outpostbbs.net
Sean Dennis | | sean@outpostbbs.net 1:18/200
DDS (Doorware |D |http://www.doorgames.org 1:2404/201
Distribution System)| | ruth@doorgames.org
Ruth Argust | |
DoorMUD |D |http://doormud.com
| | v0.98 Jun 1st 2002
| | Website is down after
| | past the splash page.
Jibben Software |D |http://www.jibbensoftware.com
| | scott@jibben.com
| | 1995-99 Release dates
John Dailey Software |D |http://www.johndaileysoftware.com
| | support@johndaileysoftware.com
Shining Star |D |http://www.shiningstar.net/bbsdoors/
| | nannette@shiningstar.net
Sunrise Doors: |D |http://www.sunrisedoors.com
Al Lawrence | | al@sunrisedoors.com
| | Tel: (404) 256-9518
The Brainex System |D |http://www.brainex.com/brainex_system/
| | stanley@brainex.com 1994-99 Releases
Trade Wars |D |http://www.eisonline.com/tradewars/
| | jpritch@eisonline.com
| | v3.09 (DOS-32) in 2002
Vagabond Software: |D |http://www.vbsoft.org 1:124/7013
Bryan Turner | | vagabond@vbsoft.org
| | last update: Jul 17th 2002
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
APoint |PI |http://www.apoint-mail.de 2:2426/1210.13
| |http://www.apoint-mail.de/indexe.htm
| | (English Version)
FIDONEWS 30-10 Page 21 11 Mar 2013
| | dirk.pokorny@apoint-mail.de
| | v1.25
CrossPoint (XP) |P |http://www.crosspoint.de (German Only)
| | pm@crosspoint.de v3.12d Dec 22nd 1999
FreeXP |P |http://www.freexp.de 2:2433/460
| | support@freexp.de
| | v3.40 RC3 Aug 31st 2003 (Snapshot)
OpenXP/32 |PI |http://www.openxp.com 2:248/2004
| | (Site is in German Only)
| | mk@openxp.de v3.8.15 Beta Feb 10th 2004
| | Download Page comes back 404 not found.
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
GoldEd+ |E |http://golded-plus.sourceforge.net/
| | 2:5080/102
| | stas_degteff@users.sourceforge.net
| | v1.1.5 Snapshot on Feb 28th 2003
SqEd32 |E |http://www.sqed.de
| | v1.15 on Dec 15th 1999
TimEd |E |http://blizzard.dnsalias.org/fidonet
| | mail@ozzmosis.com /timed
| | v1.11.a5 in March 2003 3:633/267
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
FidoIP |MTPEIU|http://sourceforge.net/projects/fidoip
| | Maxim Sokolsky 2:5020/828.777
| | v.0.5_1 on Jan 11 2010
GiGo |UI |http://www.gigo.com
| | v0109 on Jan 9th 1997
Ifmail |UI |http://ifmail.sourceforge.net
| | crosser@average.org 2:5020/230
| | Ifmail is a FTN <-> E-Mail/News Gateway
| | Program.
Internet Rex: |UI |http://members.shaw.ca/InternetRex/
Charles Cruden | | telnet://xanadubbs.ca 1:342/806
(Khan Software) | | v2.29 on Oct 21st 2001
MakeNL |U | http://hub2000.darktech.org/makenl
| | fidonet.hub2000 [at] gmail [dot] com
| | Fido: 1:229/2000
| | FidoNet Nodelist Processor
Meltdown-BBS |UI |http://meltdown-bbs.sourceforge.net/
| | meltdown-bbs.project.petkan
| | @spamgourmet.com
| | Fido: 2:350/5
FIDONEWS 30-10 Page 22 11 Mar 2013
| | Meltdown-BBS is an FTN <->
| | Web/PHP/MySQL BBS forum system.
RNtrack |U |http://sourceforge.net/projects/ftrack-as
| |2:5080/102
| |stas_degteff@users.sourceforge.net
| | v1.1.4 Snapshot on Oct 09 2009
TransNet |UI |http://www.ressl.com.ar/transnet/
| | transnet@ressl.com.ar
| | v2.11 on Jul 18th 1998
TransX: Multiboard |UI |http://www.start.ca/software/multiboard
Communications, Inc.| | Unsure about support now but Free Keys
| | are now available. Donations accepted.
| | v3.5 (Note: KeyGen is a Windows Program)
Turquoise SuperStat |U |http://www.softwolves.pp.se/sw/
| | software/turquoise
| | peter@softwolves.pp.se
| | Version: 3.0 on 2008-01-21
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
National BBS List |? | http://www.usbbs.org
Hispanic FIDO/BBS's |? | http://www.conecta2.org/pucela_bbs/
(in Spanish only) | | (Extensive software & BBS Listings)
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
File Archives:
http://archives.thebbs.org http://www.filegate.net
http://sysopscorner.thebbs.org http://www.juge.com
http://www.dmine.com/bbscorner/ http://garbo.uwasa.fi
http://www.simtel.net http://wuarchive.wustl.edu
http://www.bbsfiles.com http://hobbes.nmsu.edu
Note: most also provide FTP access
(use ftp:// instead of http:// above)
*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*
Please send corrections & additions to: Fidonews Editor
Emeritus: Robert Couture, Ben Ritchey, Todd Cochrane,
Frank Vest, Peter Popovich
-----------------------------------------------------------------
FIDONEWS 30-10 Page 23 11 Mar 2013
=================================================================
SPECIAL INTEREST
=================================================================
Nodelist Stats
Input nodelist nodelist.067
size 322.3kb
date 2013-03-08
The nodelist has 2242 nodes in it
and a total of 3271 non-comment entries
including 4 zones
35 regions
230 hosts
191 hubs
admin overhead 460 ( 20.52 %)
and 292 private nodes
120 nodes down
157 nodes on hold
off line overhead 569 ( 25.38 %)
Speed summary:
>9600 = 165 ( 7.36 %)
9600 = 1444 ( 64.41 %)
(HST = 20 or 1.39 %)
(CSP = 0 or 0.00 %)
(PEP = 1 or 0.07 %)
(MAX = 0 or 0.00 %)
(HAY = 1 or 0.07 %)
(V32 = 689 or 47.71 %)
(V32B = 48 or 3.32 %)
(V34 = 953 or 66.00 %)
(V42 = 812 or 56.23 %)
(V42B = 53 or 3.67 %)
2400 = 11 ( 0.49 %)
1200 = 2 ( 0.09 %)
300 = 620 ( 27.65 %)
ISDN = 155 ( 6.91 %)
----------------------------------------------------------
File Req Flag Applicable software Number of systems
----------------------------------------------------------
XA Frontdoor <1.99b 645
Frontdoor 2.02+
Dutchie 2.90c
Binkleyterm >2.1
D'Bridge <1.3
TIMS
Xenia
--------------------------------------
FIDONEWS 30-10 Page 24 11 Mar 2013
XB Binkleyterm 2.0 0
Dutchie 2.90b
--------------------------------------
XC Opus 1.1 1
--------------------------------------
XP Seadog 0
--------------------------------------
XR Opus 1.03 16
--------------------------------------
XW Fido >12M 59
Tabby
KittenMail
--------------------------------------
XX D'Bridge 1.30 702
Frontdoor 1.99b
Intermail 2.01
T-Mail
--------------------------------------
None QMM 819
--------------------------------------
CrashMail capable = 1130 ( 50.40 %)
MailOnly nodes = 1113 ( 49.64 %)
Listed-only nodes = 175 ( 7.81 %)
Other = -176 ( -7.85 %)
[Report produced by NETSTATS - A PD pgm]
[ Revised by B Felten, 2:203/2]
-----------------------------------------------------------------
FIDONEWS 30-10 Page 25 11 Mar 2013
=================================================================
FIDONEWS INFORMATION
=================================================================
How to Submit an Article
If you wish to submit an article for inclusion in the Fidonews, here
are some guidelines, if you send it as an attached file; the preferred
method if you want reasonable control over how the published article
will appear in the Fidonews:
a) Plain ASCII text. If you could type it on your keyboard, it's
probably quite OK. No line may be longer than 70 characters.
b) Put a title to the article. Put the title in two times. The first
time, on the first line, with an * before it. The second time, on
the second line, without the * and centered. This will help in the
format since the title with the * is removed and used in the index,
the second line will become the headline. On the third line, put
your name and FidoNet address, present or former. If former, you
may want to add some other address where you can be reached for
personal comments.
c) Deadline for article submission is Sunday, 22:00 UTC.
Help the Editor by following the above guides. Below are some subjects
and the file extension for the article as set in the configuration
file for the making of the Fidonews. Please help by putting the file
extension of the correct subject on the file name if known.
Ideas for Subject areas:
Subject File | Subject File
----------------------------------|----------------------------------
From the *C's *.css | Rebuttals to articles *.reb
Fidonet Regional News *.reg | Fidonet Net News *.net
Retractions *.rtx | General Fidonet Articles *.art
Guest Editorial *.gue | Fidonet Current Events *.cur
Fidonet Interviews *.inv | Fidonet Software Reviews *.rev
Fidonet Web Page Reviews *.web | Fidonet Notices *.not
Getting Fidonet Technical *.ftc | Question Of The Week *.que
Humor in a Fido Vein *.hfv | Comix in ASCII *.cmx
Fidonet's Int. Kitchen *.rec | Poet's Corner *.poe
Clean Humor & Jokes *.jok | Other Stuff *.oth
Fidonet Classified Ads *.ads | Corrections *.cor
Best of Fidonet *.bof | Letters to the Editor *.let
If you don't know or are not sure, send the article anyway. Put a .TXT
on it and I'll try to figure out where it should be in the Fidonews.
If you follow these simple guidelines, there should be little problem
in getting your article published. If your submission is too far out
of specs for the Fidonews, it will be returned to you and/or a message
sent informing you of the problem. This DOES NOT mean that your
article is not accepted. It means that there is something in it that I
can not fix and I need your help on it.
FIDONEWS 30-10 Page 26 11 Mar 2013
Send articles via e-mail or netmail, file attach or message to:
Björn Felten
Fidonet 2:2/2 or 2:203/0
E-Mail bfelten @ telia dot com
Skype file bfelten
IMPORTANT! If you send the article via e-mail, make sure you put the
word "fidonews" somewhere in the subject line! That way it
will always pass the spam filter, ending up in the proper
folder.
Please include a message, telling me that you have sent an article.
That way I will know to look for it.
-----------------------------------------------------------------
FIDONEWS 30-10 Page 27 11 Mar 2013
Credits, Legal Infomation, Availability
+ -- -- -- -- -- -- -- -- FIDONEWS STAFF - -- -- -- -- -- -- -- +
| |
| Editor: Björn Felten, 2:2/2 |
| |
+ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +
+ -- -- -- -- -- -- -- - EDITORS EMERITI - -- -- -- -- -- -- -- +
| |
| Tom Jennings, Thom Henderson, Dale Lovell, Vince |
| Perriello, Tim Pozar, Sylvia Maxwell, Donald Tees, |
| Christopher Baker, Zorch Frezberg, Henk Wolsink, |
| Doug Meyers, Warren D. Bonner, Frank L. Vest |
| |
+ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +
Fidonews is published weekly by and for the members of Fidonet.
There is no copyright attached to Fidonews, though authors
retain rights to their contributed articles. Opinions expressed
by the authors are strictly their own. Noncommercial duplication
and distribution within Fidonet is encouraged. Authors are
encouraged to send their articles in ASCII text to the Editor
at one of the addresses above.
The weekly edition of Fidonews is distributed through the file
area FIDONEWS, and is published as echomail in the echo FIDONEWS.
The different articles are distributed in the file area SNOOZE.
A service to various projects for making Fidonews available on
the web with a more pleasing lay-out.
These sources are normally available through your Network
Coordinator. The current and past issues are also available from
the following sources:
+ -- -- -- -- -- -- - FIDONEWS AVAILABILITY - -- -- -- -- -- -- +
| |
| File request from 2:2/2 or 2:203/0: |
| current issue FIDONEWS |
| back issue, volume v, issue ii FNEWSvii.ZIP |
| articles, vol.no nn, issue ii INPUnnii.ZIP |
| |
| On the web: |
| http://felten.yi.org/fidonews |
| http://fidonews.eu |
| |
| The Snooze *and* the FIDONEWS echo in your newsreader: |
| news://felten.yi.org/FIDONEWS |
| |
+ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +
-----------------------------------------------------------------
Download original FidoNews · Volume 30 (2013) · ← Previous · Next →