Synchronet v3.21e-Win32 (install) has been released (Mar-2026).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
ref:fidonet_glossary [2020/04/22 14:54] – Alphabetized. digital manref:fidonet_glossary [2024/08/09 13:17] (current) – [AreaFix/Area Manager] Mention how FTN nodes usually use areafix digital man
Line 1: Line 1:
 ====== FidoNet Glossary ====== ====== FidoNet Glossary ======
  
-This is our glossary of technical terms specific to FidoNet.+This is the Synchronet glossary of technical terms specific to FidoNet.
  
-==== AKA ====+===== AKA =====
 AKAs are additional/alias addresses for an FTN node. Some times you'll see the //Main/Primary// address also referred to as an "AKA", but just know this just means an FTN address, possibly one of many, that may be used to reach a single FTN node. AKAs are additional/alias addresses for an FTN node. Some times you'll see the //Main/Primary// address also referred to as an "AKA", but just know this just means an FTN address, possibly one of many, that may be used to reach a single FTN node.
  
 If a node belongs to multiple FTN networks (e.g. FidoNet and one or more "othernets"), then they will usually have their FidoNet address (Zones 1-4) as their //Main// address and the "othernet" addresses as their AKAs. If a node belongs to multiple FTN networks (e.g. FidoNet and one or more "othernets"), then they will usually have their FidoNet address (Zones 1-4) as their //Main// address and the "othernet" addresses as their AKAs.
  
-==== AreaFix/Area Manager ====+===== Area ===== 
 + 
 +A FidoNet //Area// may refer to a networked message area (a.k.a. "echo") typically devoted to a single discussion topic or a networked file area. Every area must have a unique //AreaTag//. EchoMail messages are identified by the ''AREA:'' kludge line which specifies the //AreaTag// in which the message was posted. 
 + 
 +===== AreaFix/Area Manager =====
  
 AreaFix is a synonym for area manager (the very first FTN area manager AreaFix is a synonym for area manager (the very first FTN area manager
Line 15: Line 19:
 no external area manager program is required. If you are not an FTN hub, then no external area manager program is required. If you are not an FTN hub, then
 the area manager portion of SBBSecho will probably not get much use on your the area manager portion of SBBSecho will probably not get much use on your
-system. The Area Manager process has also be called a "Conference Manager" ([[http://ftsc.org/docs/fsc-0057.003|ConfMgr]]).+system. The Area Manager process has also been called a "Conference Manager" ([[http://ftsc.org/docs/fsc-0057.003|ConfMgr]]). 
 + 
 +As a FidoNet node, you may be required to send a netmail message to your hub's area manager (usually sent to "AreaFix @ your-hub's-ftn-address", with your area manager password in the mail subject) in order to link echomail areas. 
 +===== Area Tag =====
  
-==== Attach or FLO Mailer? ====+A FidoNet //Area Tag// (a.k.a. Area Name or Echo Tag) is a unique area identifier made of up to 50 US-ASCII (traditionally, all uppercase) alphanumeric characters with a few punctuation and symbolic characters (e.g. ''!'', ''.'', ''-'' and ''_'') allowed. 
 +===== Attach or FLO Mailer? =====
  
 If you are using FrontDoor, InterMail, D'bridge, SEAdog, Dutchie, or any other If you are using FrontDoor, InterMail, D'bridge, SEAdog, Dutchie, or any other
Line 27: Line 35:
 It is very important that you select the correct "Mailer Type" in the ''[[util:echocfg]]'' utility (or ''sbbsecho.ini'' file). It is very important that you select the correct "Mailer Type" in the ''[[util:echocfg]]'' utility (or ''sbbsecho.ini'' file).
  
-=== Bad Packet ===+===== Bad Packet =====
 If SBBSecho cannot process an inbound packet file, it will rename the file, giving it a ''.bad'' extension. Checking the SBBSecho log file  (e.g. ''[[dir:data]]/sbbsecho.log'') for the reason for the ''Bad packet detected'', if you can then remedy the problem and rename the ''*.bad'' files to ''*.pkt'', SBBSecho will rediscover and attempt to re-process the packet files. Alternatively, you can just delete ''.bad'' packets and perform a hub re-scan if you expect the packets contain only EchoMail (no NetMail) and you want the missing EchoMail messages from the packets.  If SBBSecho cannot process an inbound packet file, it will rename the file, giving it a ''.bad'' extension. Checking the SBBSecho log file  (e.g. ''[[dir:data]]/sbbsecho.log'') for the reason for the ''Bad packet detected'', if you can then remedy the problem and rename the ''*.bad'' files to ''*.pkt'', SBBSecho will rediscover and attempt to re-process the packet files. Alternatively, you can just delete ''.bad'' packets and perform a hub re-scan if you expect the packets contain only EchoMail (no NetMail) and you want the missing EchoMail messages from the packets. 
  
-== Identifying Bad Packets ==+==== Identifying Bad Packets ====
  
   - File length is shorter than a packet header (58 bytes)   - File length is shorter than a packet header (58 bytes)
Line 40: Line 48:
   - Packet contains one or more "grunged messages" (e.g. packed //message type// is not ''2'')   - Packet contains one or more "grunged messages" (e.g. packed //message type// is not ''2'')
  
-==== BinkP ====+===== BinkP =====
  
 [[wp>BinkP]] is the //BinkD Protocol//, a TCP application protocol invented by Dima Maloff in 1996 and later standardized by the FTSC, for transferring files (primarily, [[ref:FidoNet Packets]]) between Internet hosts over IP. The BinkP protocol was originally implemented as an ad-hoc protocol for the transferring of files between instances of the Binkley Daemon FidoNet mailer ([[https://2f.ru/binkd/|BinkD]]). The protocol was later adopted by other FidoNet mailers and later became a FidoNet standard. [[wp>BinkP]] is the //BinkD Protocol//, a TCP application protocol invented by Dima Maloff in 1996 and later standardized by the FTSC, for transferring files (primarily, [[ref:FidoNet Packets]]) between Internet hosts over IP. The BinkP protocol was originally implemented as an ad-hoc protocol for the transferring of files between instances of the Binkley Daemon FidoNet mailer ([[https://2f.ru/binkd/|BinkD]]). The protocol was later adopted by other FidoNet mailers and later became a FidoNet standard.
  
-==== Bundle ====+===== Boss ===== 
 + 
 +A //Boss Node// is a FidoNet node that has one or more //Point Nodes// (a.k.a. points) has subordinate and dependent nodes. 
 +===== Bundle =====
  
 An FTN bundle is a single file archive of one or more (usually compressed) An FTN bundle is a single file archive of one or more (usually compressed)
Line 55: Line 66:
 inbound bundles to ''.?_?'' or ''.?-?'' (e.g. ''*.mo0'' would be renamed to ''*.m_0''). inbound bundles to ''.?_?'' or ''.?-?'' (e.g. ''*.mo0'' would be renamed to ''*.m_0'').
  
-==== Downlink ====+===== Downlink =====
  
 A //Downlink// is a Linked Node which your system "feeds" messages and for which your system is responsible for routing received messages from. A //Downlink// is a Linked Node which your system "feeds" messages and for which your system is responsible for routing received messages from.
  
-==== EchoMail ====+===== Echo ===== 
 +  * Message echo - A way to distribute messages between systems (see EchoMail). 
 +  * File echo - Like a message echo, but for distributing files instead of messages. 
 + 
 +===== EchoMail =====
  
 Group or conference messages of a particular subject matter (a.k.a. Message Area). Usually Group or conference messages of a particular subject matter (a.k.a. Message Area). Usually
Line 67: Line 82:
  
  
-==== FTN ====+===== FTN =====
 FidoNet Technology Network: Any network using FidoNet standards for addressing, FidoNet Technology Network: Any network using FidoNet standards for addressing,
 mail packets, mail sessions, node lists, etc. mail packets, mail sessions, node lists, etc.
  
-==== Kludge Line ==== +===== Kludge Line ===== 
 Due to historic FTN message and packet header limitations, some message metadata was defined in the body text of each message in the form of "control lines" (often called //kludge lines//). Each control line begins with a Ctrl-A (ASCII 1) character followed by a keyword, a space, some optional data, and terminated with a carriage return (ASCII 13) character. Different control line keywords are used to define different metadata values.  Due to historic FTN message and packet header limitations, some message metadata was defined in the body text of each message in the form of "control lines" (often called //kludge lines//). Each control line begins with a Ctrl-A (ASCII 1) character followed by a keyword, a space, some optional data, and terminated with a carriage return (ASCII 13) character. Different control line keywords are used to define different metadata values. 
  
Line 80: Line 95:
 Some control lines are only expected in EchoMail messages, some only in NetMail, and some may appear in either. Some control lines are only expected in EchoMail messages, some only in NetMail, and some may appear in either.
  
-==== Mailer ====+===== Mailer =====
  
 A [[resource:FidoNet Mailer]] is the software component which transfers [[ref:FidoNet Packets]] between systems ("FidoNet nodes"). A [[resource:FidoNet Mailer]] is the software component which transfers [[ref:FidoNet Packets]] between systems ("FidoNet nodes").
Line 88: Line 103:
 These types of mailers (e.g. FrontDoor, D'Bridge, Portal of Power, etc.) were often called "front-end mailers" and are fairly obsolete today, replaced by modern mailers that support Internet-based FidoNet packet transfers (e.g. using [[#BinkP]] over TCP/IP). These types of mailers (e.g. FrontDoor, D'Bridge, Portal of Power, etc.) were often called "front-end mailers" and are fairly obsolete today, replaced by modern mailers that support Internet-based FidoNet packet transfers (e.g. using [[#BinkP]] over TCP/IP).
  
-==== NetMail ====+===== NetMail =====
  
 Point-to-point (usually person-to-person) directly-delivered or routed messages (now more commonly referred to as "e-mail" or just "mail"). Point-to-point (usually person-to-person) directly-delivered or routed messages (now more commonly referred to as "e-mail" or just "mail").
  
-==== Node ====+===== Network Coordinator ===== 
 +Primarily a node who has the added task of administering a LOCAL segment of the nodelist for his/her NET, a NET may cover part or all of a city and or part of a country. 
 + 
 +===== Node ===== 
 +How a particular FTN/Fidonet system is referred to. 
 All FidoNet node-listed systems are //nodes// of the network. All FidoNet node-listed systems are //nodes// of the network.
  
Line 103: Line 123:
 A **Linked Node** is a node which is linked with your system in some pre-arranged way and is reflected in your SBBSecho configuration (e.g. packet password, AreaFix password, packet type, archive type, etc.).  Linked Nodes may also be linked with one or more EchoMail message areas on your system as reflected in your Area File. A **Linked Node** is a node which is linked with your system in some pre-arranged way and is reflected in your SBBSecho configuration (e.g. packet password, AreaFix password, packet type, archive type, etc.).  Linked Nodes may also be linked with one or more EchoMail message areas on your system as reflected in your Area File.
  
-==== Nodelist ====+===== Nodelist =====
  
 A text file, in a standardized structured format that is both human and computer-readable, that lists all the nodes of a FidoNet-style network along with metadata describing each node's location, operator, capabilities and its role within the network hierarchy. A text file, in a standardized structured format that is both human and computer-readable, that lists all the nodes of a FidoNet-style network along with metadata describing each node's location, operator, capabilities and its role within the network hierarchy.
  
-==== Packet ====+===== Packet =====
  
-An [[ref:FidoNet packets|FTN packet]] is a group of one or more messages contained in a single +An [[ref:FidoNet packets|FTN packet]] is a group of one or more messages contained in a single uncompressed binary file. Packets may contain EchoMail and/or NetMail messages.
-uncompressed file. Packets may contain echomail and/or netmail messages. +
-Packets files usually have a ''.pkt'' extension, although outbound NetMail packets for +
-Binkley/FLO Mailers will have ''.?ut'' extensions (where ? is either ''o'', ''c'', ''d'', or ''h'', e.g ''.out'', ''.cut'', etc.). The +
-first eight characters of the filename may be anything, but are usually decimal or hexadecimal +
-digits representing the date and time the packet was created.+
  
-You can use the [[person:digital man]]'s ''pktdump'' utility to view packet headers and help identify and fix problems with inbound and outbound packets.+Packet files usually have a ''.pkt'' suffix/extension, although outbound NetMail packets for Binkley/FLO Mailers will have ''.?ut'' extensions (where ? is either ''o'', ''c'', ''d'', or ''h'', e.g. ''.out'', ''.cut'', ''.hut'', etc.). The first eight characters of the filename may be anything, but are usually decimal or hexadecimal digits representing the date and time the packet was created.
  
-It is generally **not** a good idea to try and use a plain-text viewer or editor to inspect [[ref:FidoNet packets]] since they contain binary integer values that may be interpreted as terminal control characters and the header data just won't be human-readable in this manner.+You can use the [[person:digital man]]'s ''pktdump'' utility to view packet headers and help identify and fix problems with inbound and outbound FTN packets.
  
-==== Scan ====+It is generally **not** a good idea to try and use a plain-text viewer or editor to inspect [[ref:FidoNet packets]] since they contain binary integer values that may be interpreted as terminal control characters and the header data just won't be human-readable in this manner. Use a tool specifically designed to view FTN packets (e.g. ''pktdump''). 
 + 
 +===== Point ===== 
 + 
 +A //Point Node// is an FTN node with an address that ends in ''.1'' or another non-zero fractional value. An FTN node address without a period/dot (''.'') or that ends in ''.0'' is **not** a point node address. 
 + 
 +A Point Node is not listed in the network's nodelist and is dependent on its //Boss Node// to receive and deliver files, including NetMail and EchoMail packets, on its behalf. 
 + 
 +===== Poll ===== 
 + 
 +A poll of a node is when a connection is attempted to a linked-node even though there are no files (e.g. mail) waiting to be sent to that node. 
 + 
 +===== Region ===== 
 +A REGION may cover an entire country or just a part of a country depending on it's size, the REGIONAL address is not obvious in the end node address. 
 + 
 +===== Regional Coordinator ===== 
 +Primarily a node who has the added task of administering a REGIONAL segment of the nodelist for his/her REGION. 
 + 
 +===== Scan =====
  
 To //scan// message bases means to //export// locally-posted messages from your BBS's local message bases into EchoMail packets to be sent to your upstream link (hub) and any downstream linked nodes you may have. To //scan// message bases means to //export// locally-posted messages from your BBS's local message bases into EchoMail packets to be sent to your upstream link (hub) and any downstream linked nodes you may have.
  
-==== Toss ====+===== TIC ===== 
 + 
 +"TIC" is the standard file extension for the information file that is sent along with a file that is distributed in a File Echo 
 + 
 +===== Toss =====
  
 To //toss// EchoMail packets or messages means to //import// the packed messages into your BBS's local message bases where your users can read and reply to the messages. FidoNet EchoMail programs, like SBBSecho, are often referred to as "Tossers" for this reason. To //toss// EchoMail packets or messages means to //import// the packed messages into your BBS's local message bases where your users can read and reply to the messages. FidoNet EchoMail programs, like SBBSecho, are often referred to as "Tossers" for this reason.
  
-==== Uplink ====+===== Uplink =====
  
 An //Uplink// is a Linked Node which is your system's pre-arranged conduit to the rest of the message network (a.k.a. your hub). An //Uplink// is a Linked Node which is your system's pre-arranged conduit to the rest of the message network (a.k.a. your hub).
  
-==== Zones, Nets, Nodes, and Points? ====+===== Zones, Nets, Nodes, and Points? =====
 FTN node addresses are like phone numbers, they are made up of multiple FTN node addresses are like phone numbers, they are made up of multiple
 components (four usually, but sometimes three and sometimes five).  components (four usually, but sometimes three and sometimes five). 
Line 176: Line 213:
 A 5D (5 dimensional) address refers to an FTN address consisting of a standard A 5D (5 dimensional) address refers to an FTN address consisting of a standard
 3D or 4D address with an appended "@domain" (e.g. ''1:103/705@fidonet''). This domain component is limited to 8 case-insensitive characters - it is **not** an Internet domain. 3D or 4D address with an appended "@domain" (e.g. ''1:103/705@fidonet''). This domain component is limited to 8 case-insensitive characters - it is **not** an Internet domain.
 +
 +===== Zone Coordinator =====
 +Primarily a node who has the added task of administering a ZONE segment of the nodelist for his/her ZONE, a ZONE can cover a single country or several countries.
  
 ===== See Also ===== ===== See Also =====

Trace: