Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| util:sbbsecho [2020/03/10 21:44] – [Install] typo and more digital man | util:sbbsecho [2025/04/09 14:20] (current) – Document areas.ini digital man | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== SBBSecho ====== | + | ====== SBBSecho |
| Synchronet' | Synchronet' | ||
| Line 65: | Line 65: | ||
| </ | </ | ||
| + | An alternative method is to instead subscribe/ | ||
| ===== Area File ===== | ===== Area File ===== | ||
| - | By default, SBBSecho will try to open an //Area File// (by default, '' | + | By default, SBBSecho will try to open an //Area File// (by default, '' |
| - | To successfully operate without an Area File, you must have your hub configured | + | The Area File can be used to associate FidoNet EchoTags with sub-boards |
| - | You will need an Area File if you are to have any downlinks (nodes | + | The Area File is optional, not strictly needed, when you have the " |
| - | [[util: | + | You **will** need an Area File if you are to have any downlinks (nodes for which you are //their// hub to the network). |
| + | |||
| + | [[util: | ||
| < | < | ||
| ╔═══════════════════════════════════════╗ | ╔═══════════════════════════════════════╗ | ||
| Line 80: | Line 83: | ||
| ║ │subs.txt | ║ │subs.txt | ||
| -> | -> | ||
| + | -> | ||
| ║ │backbone.na | ║ │backbone.na | ||
| + | ║ │newsgroup.lst | ||
| ╚═══════════════════════════════════════╝ | ╚═══════════════════════════════════════╝ | ||
| </ | </ | ||
| Line 87: | Line 92: | ||
| ==== Format ==== | ==== Format ==== | ||
| + | |||
| + | Two area file formats are supported by SBBSecho (pick one): | ||
| + | * areas.bbs - historic/ | ||
| + | * areas.ini - more modern style, one echo/area per [section] | ||
| + | |||
| + | === areas.bbs === | ||
| Each line of the SBBSecho Area File (e.g. '' | Each line of the SBBSecho Area File (e.g. '' | ||
| CODE TAG LINK [LINK] [...] | CODE TAG LINK [LINK] [...] | ||
| + | |||
| Where each field is separated by white-space (space or tab characters) and the fields are: | Where each field is separated by white-space (space or tab characters) and the fields are: | ||
| - | === CODE === | + | == CODE == |
| The '' | The '' | ||
| Internal codes consist of a combination of the Message Group' | Internal codes consist of a combination of the Message Group' | ||
| - | == Pass-through Areas == | + | = Pass-through Areas = |
| Any unrecognized internal codes are considered // | Any unrecognized internal codes are considered // | ||
| - | === TAG === | + | == TAG == |
| The '' | The '' | ||
| - | == Long Tags == | + | **Long Tags**\\ |
| Although standard FidoNet echo tags (AKA "area tag") may be as long as 35 characters, Synchronet' | Although standard FidoNet echo tags (AKA "area tag") may be as long as 35 characters, Synchronet' | ||
| - | == Bad Echo Area == | + | **Bad Echo Area**\\ |
| If an area's '' | If an area's '' | ||
| - | === LINK === | + | == LINK == |
| Each '' | Each '' | ||
| - | Lines beginning with a semicolon (;) are considered comments, and are ignored. | + | === Example === |
| - | ==== Example | + | |
| < | < | ||
| Line 123: | Line 133: | ||
| The amount of spacing (white-space characters including horizontal tabs and spaces) between each element in the line is not important. Each line may be up to 1024 characters in length. | The amount of spacing (white-space characters including horizontal tabs and spaces) between each element in the line is not important. Each line may be up to 1024 characters in length. | ||
| + | |||
| + | **Note**: | ||
| + | * Only the code and tag fields are required | ||
| + | * The code and tag fields are case in-sensitive | ||
| + | * The link fields must be 2D, 3D, or 4D FidoNet-style node addresses | ||
| + | * The ' | ||
| + | * Lines beginning with a semicolon (;) are ignored (i.e. comments) | ||
| + | * Leading white-space characters are ignored | ||
| + | * Blank lines are ignored | ||
| + | * A tag value of ' | ||
| + | * A code value of ' | ||
| + | * This file may be import/ | ||
| + | * This file may be remotely modified by authorized nodes using AreaMgr | ||
| + | |||
| + | === areas.ini === | ||
| + | |||
| + | <file areas.ini> | ||
| + | [tag] | ||
| + | sub = code | ||
| + | links = link [link ...] | ||
| + | pass-through = true or false (default: false) | ||
| + | </ | ||
| + | |||
| + | Example '' | ||
| + | |||
| + | | ||
| + | sub = FIDO_BBS_CARN | ||
| + | links = 1: | ||
| + | |||
| + | **Note**: | ||
| + | * Each area definition begins with the [tag] line (the ' | ||
| + | * The code and tag values are case in-sensitive | ||
| + | * The link values must be 2D, 3D, or 4D FidoNet-style node addresses | ||
| + | * The ' | ||
| + | * Lines beginning with a semicolon (;) are ignored (i.e. comments) | ||
| + | * Leading white-space characters are ignored | ||
| + | * Blank lines are ignored | ||
| + | * A tag value (section name) of ' | ||
| + | * This file may be import/ | ||
| + | * This file may be remotely modified by authorized nodes using AreaMgr | ||
| ===== Configure ===== | ===== Configure ===== | ||
| 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: | + | - Configure your fundamental FTN settings (e.g. system address) in [[util: |
| - | - Use the '' | + | - Use the '' |
| ==== SCFG ==== | ==== SCFG ==== | ||
| Line 181: | Line 231: | ||
| === 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 '' |
| Line 317: | Line 367: | ||
| Log Timestmap Format defines the format of the date/ | Log Timestmap Format defines the format of the date/ | ||
| along with each log message to the log file (e.g. '' | along with each log message to the log file (e.g. '' | ||
| - | The timestamp format is defined using standard C '' | + | The timestamp format is defined using standard C '' |
| The default format is: '' | The default format is: '' | ||
| For SBBSecho v2 timestamp format, use '' | For SBBSecho v2 timestamp format, use '' | ||
| Line 520: | Line 570: | ||
| == AreaFix Password == | == AreaFix Password == | ||
| - | AreaFix passwords are required to be included in the //Subject// line of received AreaFix requests (NetMail messages). | + | AreaFix passwords |
| - | AreaFix Passwords are case insensitive. | + | AreaFix Passwords are case insensitive |
| This setting may be managed by the node using AreaFix requests. | This setting may be managed by the node using AreaFix requests. | ||
| Line 771: | Line 821: | ||
| from any additionally configured EchoLists which they have | from any additionally configured EchoLists which they have | ||
| access to. | access to. | ||
| + | |||
| + | == Zone Blind SEEN-BY and PATH Lines == | ||
| + | Zone Blind SEEN-BY and PATH Lines when Enabled will cause SBBSecho to assume that node numbers are not duplicated across zones and that a net/node combination in either of these Kludge lines should be used to identify a spcific node regardless of which zone that node is located in (thus breaking the rules of FidoNet 3D addressing). | ||
| + | |||
| + | If you are having trouble with FidoNet echomail crossing Zone boundaries which does not add all the SEEN-BY and PATH nodes, then enable this option with the limit of " | ||
| === Paths and Filenames === | === Paths and Filenames === | ||
| Line 818: | Line 873: | ||
| == Area File == | == Area File == | ||
| - | This is the path and filename | + | This is the path of the file SBBSecho will use as your primary |
| - | use as it's EchoMail Message Area File. | + | list of FidoNet-style message areas. |
| - | the file '' | + | to exist if you need SBBSecho |
| + | |||
| + | Two area file formats are supported by SBBSecho (pick one): | ||
| + | * areas.bbs | ||
| + | * areas.ini - more modern style, one echo/area per [section] | ||
| + | |||
| == Bad Area File == | == Bad Area File == | ||
| Line 944: | Line 1003: | ||
| == AreaFix Keys == | == AreaFix Keys == | ||
| These are the keys required for a node to be able to gain | These are the keys required for a node to be able to gain | ||
| - | access to this particular echo list. These flags are defined | + | access to this particular echo list. These keys are then given |
| - | for each node from the ' | + | to chosen nodes in the ' |
| Selecting this option will bring you to a sub-menu where you | Selecting this option will bring you to a sub-menu where you | ||
| may add and remove keys for this EchoList. | may add and remove keys for this EchoList. | ||
| Line 957: | Line 1016: | ||
| ==== Instances ==== | ==== Instances ==== | ||
| - | SBBSecho is designed to run only one instance at a time. A mutual-exclusion file ('' | + | SBBSecho is designed to run only one instance at a time. A mutual-exclusion file ('' |
| If you get the following error message (on the console and/or the log file) and you can confirm that SBBSecho is not actually running, you can safely delete the mutex file to allow SBBSecho to again run normally: | If you get the following error message (on the console and/or the log file) and you can confirm that SBBSecho is not actually running, you can safely delete the mutex file to allow SBBSecho to again run normally: | ||
| Line 1022: | Line 1081: | ||
| Remote area manager, or AreaFix, commands are used by linked nodes in order to | Remote area manager, or AreaFix, commands are used by linked nodes in order to | ||
| turn echo areas off and on, list currently connected areas, and more. | turn echo areas off and on, list currently connected areas, and more. | ||
| - | The following text is from the file '' | + | The following text is from the file '' |
| 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 Area Management |
| - | Your Area Manager password goes on the subject | + | Your Area Manager password goes in the message |
| + | by -R, -L, or -Q for Rescan, List, or Query functions, respectively. | ||
| - | In the body of the message | + | In the body of the message, one or more: |
| - | [+]<areaname> | + | <areatag> |
| - | -<areaname> | + | -<areatag> Disconnect an area |
| %HELP | %HELP | ||
| - | %LIST | + | %LIST |
| %QUERY | %QUERY | ||
| %UNLINKED | %UNLINKED | ||
| - | %COMPRESSION < | + | %COMPRESSION < |
| %PASSWORD < | %PASSWORD < | ||
| %PKTPWD < | %PKTPWD < | ||
| %TICPWD < | %TICPWD < | ||
| %RESCAN | %RESCAN | ||
| - | %RESCAN <areaname> Request a rescan of a single connected area | + | %RESCAN <areatag> |
| + | %ECHOSTATS < | ||
| %ACTIVE | %ACTIVE | ||
| %PASSIVE | %PASSIVE | ||
| + | %NOTIFY <ON | OFF> | ||
| %FROM < | %FROM < | ||
| %+ALL | %+ALL | ||
| Line 1059: | Line 1121: | ||
| ==== Changes in Version 3 ==== | ==== Changes in Version 3 ==== | ||
| - | |||
| - | For a detailed list of changes and code differences introduced in v3.0, see [[http:// | ||
| The most major changes introduced in v3.0 are: | The most major changes introduced in v3.0 are: | ||
