Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
util:sbbsecho [2017/11/13 15:00] – Define "Kludge Line" digital man | util:sbbsecho [2018/03/01 12:11] – Links to util:binkit changed to module:binkit digital man | ||
---|---|---|---|
Line 14: | Line 14: | ||
===== Terminology ===== | ===== Terminology ===== | ||
- | The terminology used with FidoNet networking technology can be as confusing as it is particular. | + | The terminology used with FidoNet networking technology can be as confusing as it is particular. |
- | ==== FTN ==== | + | ===== Installation ===== |
- | FidoNet Technology Network: Any network using FidoNet standards for addressing, | + | |
- | mail packets, mail sessions, node lists, etc. | + | |
- | ==== Zones, Nets, Nodes, | + | SBBSecho |
- | FTN node addresses are like phone numbers, they are made up of multiple | + | |
- | components (four usually, but sometimes three and sometimes five). | + | |
- | + | ||
- | The main four components are: zone, net, node, and point. | + | |
- | Each component is specified by a decimal (base-10) number, separated by symbols | + | |
- | (no spaces): | + | |
- | + | ||
- | Zone: | + | |
- | + | ||
- | The zone represents the continent (if FidoNet) or the network number (if other | + | |
- | FTN network). All FidoNet nodes in North America have a zone 1 address. When | + | |
- | the zone is specified in an address, it is the first component and must be | + | |
- | followed by a colon. If the zone is not present in an address, the local | + | |
- | system' | + | |
- | + | ||
- | The net represents the network number of the FTN node. Duplicate net numbers | + | |
- | may exist between zones. If the net number is not present, the local system' | + | |
- | net is assumed. | + | |
- | + | ||
- | The node number specifies an exact FTN node within a network. The node number | + | |
- | is the only required element of an FTN node address. | + | |
- | The point is an optional component which specifies a sub-node that does not | + | |
- | directly receive mail and is also not listed in the main FTN node list, but | + | |
- | instead gets all its mail from its boss-node (zone: | + | |
- | is not specified, 0 (zero) is assumed (i.e. '' | + | |
- | which indicates the system with that address is **not** a point node. | + | |
- | + | ||
- | Zones can be grouped into named domains (e.g. '' | + | |
- | are pretty rarely used in the twenty-first century. | + | |
- | + | ||
- | A 2D (2 dimensional) address refers to an FTN address containing just the | + | |
- | net and node numbers (e.g. '' | + | |
- | + | ||
- | A 3D (3 dimensional) address refers to an FTN address containing the zone, | + | |
- | net, and node numbers (e.g. '' | + | |
- | if it exists. | + | |
- | + | ||
- | A 4D (4 dimensional) address refers to an FTN address containing the zone, | + | |
- | net, node, and optional point numbers (e.g. '' | + | |
- | + | ||
- | A 5D (5 dimensional) address refers to an FTN address consisting of a standard | + | |
- | 3D or 4D address | + | |
- | + | ||
- | ==== Node ==== | + | |
- | All FidoNet node-listed systems are //nodes// of the network. | + | |
- | + | ||
- | **Normal Nodes** do not have a //point// value, so a '' | + | |
- | + | ||
- | **Point Nodes** (nodes with non-zero point value) may only directly connect and communicate with their //boss node//. The boss node of a point node with the address '' | + | |
- | + | ||
- | A **Boss Node** is just a normal node that has one or more //point nodes// for which they are responsible to deliver and receive messages and files. | + | |
- | + | ||
- | 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.). | + | |
- | + | ||
- | ==== AKA ==== | + | |
- | AKAs are additional/ | + | |
- | + | ||
- | If a node belongs to multiple FTN networks (e.g. FidoNet and one or more " | + | |
- | + | ||
- | ==== Uplink ==== | + | |
- | + | ||
- | An //Uplink// is a Linked Node which is your system' | + | |
- | + | ||
- | ==== Downlink ==== | + | |
- | + | ||
- | A // | + | |
- | + | ||
- | ==== Attach or FLO Mailer? ==== | + | |
- | + | ||
- | If you are using FrontDoor, InterMail, D' | + | |
- | ArcMail *.MSG attach-style mailer, you are using what we will refer to as an | + | |
- | " | + | |
- | + | ||
- | If you are using BinkD (Binkley daemon), Argus/ | + | |
- | + | ||
- | It is very important that you select the correct " | + | |
- | + | ||
- | ==== NetMail ==== | + | |
- | + | ||
- | Point-to-point (usually person-to-person) directly-delivered or routed messages (now more commonly referred to as " | + | |
- | + | ||
- | ==== EchoMail ==== | + | |
- | + | ||
- | Group or conference messages of a particular subject matter (a.k.a. Message Area). Usually | + | |
- | distributed on a regional or continental scale (e.g. FidoNet Zone 1 backbone). | + | |
- | FTN style echomail areas have a unique name associated with them to | + | |
- | distinguish each area from the others. These agreed upon area names are called //Area Tags// or //Echo Tags//. | + | |
- | + | ||
- | ==== 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 " | + | |
- | + | ||
- | ==== 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. | + | |
- | + | ||
- | ==== Packet ==== | + | |
- | + | ||
- | An FTN packet is a group of one or more messages contained in a single | + | |
- | uncompressed file. Packets may contain echomail and/or netmail messages. | + | |
- | Packets files usually have a '' | + | |
- | Binkley/FLO Mailers will have '' | + | |
- | 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 '' | + | |
- | + | ||
- | === Bad Packet === | + | |
- | If SBBSecho cannot process an inbound packet file, it will rename the file, giving it a '' | + | |
- | + | ||
- | == Identifying Bad Packets == | + | |
- | + | ||
- | - File length is shorter than a packet header (58 bytes) | + | |
- | - Packet terminator ('' | + | |
- | - File read failure (e.g. permissions or file locking issue) | + | |
- | - Source address does not match expected address (e.g. for packets found in // | + | |
- | - Packet header cannot be parsed (e.g. is not a '' | + | |
- | - Packet header contains incorrect packet password | + | |
- | - Packet contains one or more " | + | |
- | ==== Bundle ==== | + | |
- | + | ||
- | An FTN bundle is a single file archive of one or more (usually | + | |
- | packets. Bundles will have file extensions where the first two characters | + | |
- | represent the day of the week the bundle was created (MO, TU, WE, TH, FR, SA, | + | |
- | and SU) and the third character of the extension is a number or letter. The | + | |
- | first eight characters of the filename may be anything, but are usually | + | |
- | hexadecimal digits representing the FTN node address (or relative address) of | + | |
- | the system that created the bundle. SBBSecho changes the file extension of bad | + | |
- | inbound bundles to '' | + | |
- | + | ||
- | ==== AreaFix/ | + | |
- | + | ||
- | AreaFix is a synonym for area manager (the very first FTN area manager | + | |
- | program was called " | + | |
- | of areas, changing compression type, etc) are built into SBBSecho, so therefore | + | |
- | no external area manager program is required. If you are not an FTN hub, then | + | |
- | the area manager portion | + | |
- | system. The Area Manager process has also be called a " | + | |
- | + | ||
- | ==== Kludge Line ==== | + | |
- | Due to historic FTN message and packet header limitations, | + | |
- | + | ||
- | Kludge/ | + | |
- | + | ||
- | Synchronet stores FTN control lines in its message headers, so you must use the Terminal Server operator-> | + | |
- | + | ||
- | Some control lines are only expected in EchoMail messages, some only in NetMail, and some in either. | + | |
- | + | ||
- | ===== Installation ===== | + | |
SBBSecho expects to find an area file (e.g. '' | SBBSecho expects to find an area file (e.g. '' | ||
- | directory. You will need to create the Area File in order for SBBSecho to do anything with EchoMail | + | directory. You will need to create the Area File in order for SBBSecho to do anything with EchoMail |
- | [[util:SCFG]] can also export a group of message areas (sub-boards) to an SBBSecho-compatible Area File. | + | [[module:binkit]] can also export a group of message areas (sub-boards) to an SBBSecho-compatible Area File. |
- | You may want to import a network' | + | You may want to first import a network' |
===== Area File Format ===== | ===== Area File Format ===== | ||
Line 189: | Line 38: | ||
=== Pass-through Areas === | === Pass-through Areas === | ||
- | Any unrecognized internal codes are considered // | + | Any unrecognized internal codes are considered // |
==== TAG ==== | ==== TAG ==== | ||
Line 219: | Line 68: | ||
In order to set up SBBSecho for your system you must: | In order to set up SBBSecho for your system you must: | ||
- | - Configure your fundamental FTN settings (e.g. system address) in [[util:SCFG]] | + | - Configure your fundamental FTN settings (e.g. system address) in [[module:binkit]] |
- | - Use the '' | + | - Use the '' |
==== SCFG ==== | ==== SCFG ==== | ||
- | The fundamental FTN-related system settings are configured via [[SCFG]]-> | + | The fundamental FTN-related system settings are configured via [[module: |
< | < | ||
╔══════════════════════════════════════════════════════════╗ | ╔══════════════════════════════════════════════════════════╗ | ||
Line 258: | Line 107: | ||
=== NetMail Directory === | === NetMail Directory === | ||
- | This is the path to a directory on your local system where both inbound and outbound FTN NetMail will be stored. The only files placed in this directory should be FTN [[ref: | + | This is the path to a directory on your local system where both inbound and outbound FTN NetMail will be stored. The only files placed in this directory should be FTN [[ref: |
Synchronet can create '' | Synchronet can create '' | ||
Line 264: | Line 113: | ||
SBBSecho will create '' | SBBSecho will create '' | ||
- | The other NetMail-related settings on this menu affect only FidoNet NetMail messages created by the Synchronet [[: | + | The other NetMail-related settings on this [[module: |
=== Default Origin Line === | === Default Origin Line === | ||
Standard FTN EchoMail messages contain a terminating '' | Standard FTN EchoMail messages contain a terminating '' | ||
+ | |||
+ | It is possible to over-ride this default Origin Line for specific message areas (sub-boards), | ||
=== Inbound File Directory === | === Inbound File Directory === | ||
- | Older versions of SCFG (e.g. v3.16) contained this FidoNet setting which was used to specify the directory where non-secure inbound FidoNet files would be received by your FTN mailer. SBBSecho v2 used this setting, however Synchronet itself did not, so it was deprecated with SBBSecho v3 (replaced with the '' | + | Older versions of SCFG (e.g. v3.16) contained this FidoNet setting which was used to specify the directory where non-secure inbound FidoNet files would be received by your FTN mailer. SBBSecho v2 used this setting, however Synchronet itself did not, so it was deprecated with SBBSecho v3 (replaced with the '' |
==== EchoCfg ==== | ==== EchoCfg ==== | ||
- | The SBBSecho Config program (echocfg) is the program used to configure all the SBBSecho-specific settings saved exclusively in the SBBSecho configuration file ('' | + | The SBBSecho Config program ('' |
=== Command-line Syntax === | === Command-line Syntax === | ||
Line 304: | Line 155: | ||
- | Upon running '' | + | Upon running '' |
program. The path and filename of the configuration file being modified will | program. The path and filename of the configuration file being modified will | ||
appear at the top of the menu. Following are screen captures of available menus | appear at the top of the menu. Following are screen captures of available menus | ||
Line 978: | Line 829: | ||
==== Command Line ==== | ==== Command Line ==== | ||
- | Although you //can// just run SBBSecho (e.g. '' | + | Although you //can// just run SBBSecho (e.g. '' |
For importing netmail and echomail (e.g. '' | For importing netmail and echomail (e.g. '' | ||
sbbsecho -ce | sbbsecho -ce | ||
Line 1029: | Line 880: | ||
SBBSecho, should be located in your Synchronet '' | SBBSecho, should be located in your Synchronet '' | ||
area manager commands available to the linked nodes which have been configured using | area manager commands available to the linked nodes which have been configured using | ||
- | the '' | + | the '' |
< | < | ||
Address all requests to ' | Address all requests to ' | ||
Line 1070: | Line 921: | ||
- New configuration file format ('' | - New configuration file format ('' | ||
- Support for FileBoxes (BinkD-style inbox and outbox, configured per linked-node) | - Support for FileBoxes (BinkD-style inbox and outbox, configured per linked-node) | ||
- | - Much better organized and user-friendly '' | + | - Much better organized and user-friendly '' |
- Attach/ | - Attach/ | ||
- " | - " | ||
Line 1101: | Line 952: | ||
**Note**: | **Note**: | ||
- | In SBBSecho v2, if you did not have an '' | + | In SBBSecho v2, if you did not have an '' |
**Note**: | **Note**: | ||
Line 1108: | Line 959: | ||
==== Migrating Command-lines to Version 3 ==== | ==== Migrating Command-lines to Version 3 ==== | ||
- | Although the old import and export SBBSecho command-lines (e.g. pre-configured for the '' | + | Although the old import and export SBBSecho command-lines (e.g. pre-configured for the '' |
^ Option ^ Version 2 ^ Version 3 ^ | ^ Option ^ Version 2 ^ Version 3 ^ | ||
Line 1114: | Line 965: | ||
|'' | |'' | ||
|'' | |'' | ||
- | |'' | + | |'' |
|'' | |'' | ||
|'' | |'' | ||
Line 1149: | Line 1000: | ||
* [[: | * [[: | ||
* [[: | * [[: | ||
- | * [[:util:|Utilities]] | + | * [[module:binkit|Utilities]] |