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/09 15:48] – [SCFG] More details. digital man | util:sbbsecho [2022/11/30 13:44] – [Area Manager Commands] update link to areamgr.hlp in repo (from cvs to git) digital man | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== SBBSecho ====== | + | ====== SBBSecho |
Synchronet' | Synchronet' | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | SBBSecho is an FTN echomail program (tosser/ | + | SBBSecho is an FTN echomail program (tosser/ |
As of SBBSecho v2.30 (Nov-2015), SBBSecho will also export FTN NetMail from the Synchronet mail base ('' | As of SBBSecho v2.30 (Nov-2015), SBBSecho will also export FTN NetMail from the Synchronet mail base ('' | ||
- | * This feature allows the gating of SMTP (Internet e-mail) to FTN netmail by sending email to " | + | * This feature allows the gating of SMTP (Internet e-mail) to FTN netmail by sending email to " |
- | * This feature allows FidoNet netmail to be sent using JavaScript methods (e.g. via the [[server: | + | * This feature allows FidoNet netmail to be sent using JavaScript methods (e.g. via the [[server: |
In 2016, SBBSecho was overhauled and christened //version 3//. The documentation here is in the process of being updated to reflect all the changes in SBBSecho version 3. For more details about SBBSecho version 3, see [[#Version 3]]. | In 2016, SBBSecho was overhauled and christened //version 3//. The documentation here is in the process of being updated to reflect all the changes in SBBSecho version 3. For more details about SBBSecho version 3, see [[#Version 3]]. | ||
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 ==== | + | ===== Install ===== |
- | FidoNet Technology Network: Any network using FidoNet standards for addressing, | + | |
- | mail packets, mail sessions, node lists, etc. | + | |
- | ==== Zones, Nets, Nodes, and Points? ==== | + | SBBSecho and its configuration program, EchoCfg, come with Synchronet BBS software |
- | FTN node addresses are like phone numbers, they are made up of multiple | + | |
- | components | + | |
- | The main four components are: zone, net, node, and point. | + | Things you should have before you proceed: |
- | Each component is specified by a decimal | + | - Your hub/ |
- | (no spaces): | + | - Your hub/ |
+ | - Your own FidoNet address (use ''<// | ||
+ | - Your hub-agreed-upon BinkP session password | ||
+ | - Your hub-agreed-upon packet password | ||
+ | | ||
+ | - An // | ||
- | Zone: | + | ==== Message Group ==== |
- | The zone represents the continent | + | Create a message group called " |
- | 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 | + | ║ |
- | system' | + | ╠══════════════════════════════════════════════════════════╣ |
+ | ║ │Long Name FidoNet | ||
+ | ║ │Short Name | ||
+ | ║ │Internal Code Prefix | ||
+ | ║ │Access Requirements | ||
+ | ║ │Sort Group by Sub-board | ||
+ | ║ │Clone Options | ||
+ | ║ │Export Areas... ║ | ||
+ | ║ │Import Areas... ║ | ||
+ | ║ │Message Sub-boards... | ||
+ | ╚══════════════════════════════════════════════════════════╝ | ||
- | 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 | + | ==== EchoList ==== |
- | 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 | + | Now, import a list of the public message areas (" |
- | are pretty rarely used in the twenty-first century. | + | < |
+ | ╔═════════════════════════════════════════╗ | ||
+ | ║ | ||
+ | ╠═════════════════════════════════════════╣ | ||
+ | ║ │subs.txt | ||
+ | ║ │control.dat QWK Conference List ║ | ||
+ | ║ │areas.bbs | ||
+ | ║ │areas.bbs | ||
+ | -> | ||
+ | ║ │badareas.lst | ||
+ | ╚═════════════════════════════════════════╝ | ||
+ | </ | ||
- | A 2D (2 dimensional) address refers | + | An alternative method is to instead subscribe/ |
- | net and node numbers | + | ===== Area File ===== |
- | A 3D (3 dimensional) address refers | + | By default, SBBSecho will try to open an //Area File// |
- | net, and node numbers | + | |
- | if it exists. | + | |
- | A 4D (4 dimensional) address refers to an FTN address containing the zone, | + | To successfully operate without |
- | net, node, and optional point numbers (e.g. '' | + | |
- | A 5D (5 dimensional) address refers to an FTN address consisting of a standard | + | You will need an Area File if you are to have any downlinks |
- | 3D or 4D address with an appended " | + | |
- | ==== Node ==== | + | [[util:SCFG]] can also export |
- | All FidoNet node-listed systems are //nodes// of the network. | + | <file> |
- | + | ╔═══════════════════════════════════════╗ | |
- | **Normal Nodes** do not have a //point// value, so a '' | + | ║ Export Area File Format |
- | + | ╠═══════════════════════════════════════╣ | |
- | **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 '' | + | ║ │subs.txt |
- | + | -> | |
- | 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. | + | ║ │backbone.na FidoNet EchoList |
- | + | ╚═══════════════════════════════════════╝ | |
- | 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.). | + | </file> |
- | + | ||
- | ==== 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 | + | |
- | + | ||
- | ==== 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 "Tossers" | + | |
- | + | ||
- | ==== 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]]' | + | |
- | + | ||
- | === Bad Packet === | + | |
- | If SBBSecho cannot process an inbound packet | + | |
- | + | ||
- | == 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) | + | |
- | | + | |
- | - Packet header cannot be parsed (e.g. is not a '' | + | |
- | | + | |
- | - Packet contains one or more " | + | |
- | ==== Bundle ==== | + | |
- | + | ||
- | An FTN bundle is a single file archive of one or more (usually compressed) | + | |
- | 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/Area Manager ==== | + | |
- | + | ||
- | 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 of SBBSecho will probably not get much use on your | + | |
- | system. | + | |
- | + | ||
- | + | ||
- | ===== Installation ===== | + | |
- | + | ||
- | 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 message areas. | + | |
- | [[util: | + | If the '' |
- | You may want to import a network's EchoList | + | |
- | ===== Area File Format | + | ==== Format ==== |
Each line of the SBBSecho Area File (e.g. '' | Each line of the SBBSecho Area File (e.g. '' | ||
Line 175: | Line 93: | ||
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 may be as long as 35 characters, Synchronet' | + | Although standard FidoNet echo tags (AKA "area tag" |
- | === 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. | Lines beginning with a semicolon (;) are considered comments, and are ignored. | ||
- | ==== Area File Example ==== | + | ==== Example ==== |
< | < | ||
Line 205: | Line 123: | ||
</ | </ | ||
- | The amount of spacing (white-space characters including horizontal tabs and spaces) between each element in the line is not important. Each | + | 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. |
- | line may be up to 1024 characters in length. | + | |
- | ===== Configuration | + | ===== 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 222: | Line 139: | ||
╠══════════════════════════════════════════════════════════╣ | ╠══════════════════════════════════════════════════════════╣ | ||
║ │System Addresses | ║ │System Addresses | ||
- | ║ │Default Outbound Address | ||
║ │Default Origin Line ║ | ║ │Default Origin Line ║ | ||
║ │NetMail Semaphore | ║ │NetMail Semaphore | ||
║ │EchoMail Semaphore | ║ │EchoMail Semaphore | ||
- | ║ │NetMail Directory | + | ║ │NetMail Directory |
- | ║ │Allow Sending of NetMail | + | ║ │Allow Sending of NetMail |
- | ║ │Allow File Attachments | + | ║ │Allow File Attachments |
║ │Send NetMail Using Alias | ║ │Send NetMail Using Alias | ||
║ │NetMail Defaults to Crash No ║ | ║ │NetMail Defaults to Crash No ║ | ||
Line 247: | Line 163: | ||
=== System Addresses === | === System Addresses === | ||
- | Set your main/ | + | Set your main/ |
+ | |||
+ | Only 3D (zone: | ||
=== 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 '' | ||
- | 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 [[util: |
=== 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 305: | Line 225: | ||
< | < | ||
╔═════════════════════════╗ | ╔═════════════════════════╗ | ||
- | ║ Configure | + | ║ Configure |
╠═════════════════════════╣ | ╠═════════════════════════╣ | ||
║ │Global Settings... | ║ │Global Settings... | ||
Line 313: | Line 233: | ||
║ │EchoMail Settings... | ║ │EchoMail Settings... | ||
║ │Paths and Filenames... ║ | ║ │Paths and Filenames... ║ | ||
+ | ║ │Domains... | ||
║ │EchoLists... | ║ │EchoLists... | ||
╚═════════════════════════╝ | ╚═════════════════════════╝ | ||
+ | |||
</ | </ | ||
Line 337: | Line 259: | ||
=== Global Settings === | === Global Settings === | ||
< | < | ||
- | ╔══════════════════════════════════════════════╗ | + | ╔═══════════════════════════════════════════════════╗ |
- | ║ Global Settings | + | ║ Global Settings |
- | ╠══════════════════════════════════════════════╣ | + | ╠═══════════════════════════════════════════════════╣ |
- | ║ │Mailer Type | + | ║ │Mailer Type Binkley/ |
- | ║ │Log Level Informational | + | ║ │Log Level |
- | ║ │Log Timestamp Format | + | ║ │Log Timestamp Format |
- | ║ │Strict Packet Passwords | + | ║ │Strict Packet Passwords |
- | ║ │Use | + | ║ │Config File Backups |
- | ║ │BSY Mutex File Timeout | + | ║ │Minimum Free Disk Space 10G bytes ║ |
- | ║ │BSO Lock Attempt Delay 10 seconds | + | ║ │Strip Incoming Soft CRs No ║ |
- | ║ │BSO Lock Attempt Limit 60 ║ | + | ║ │Strip Outgoing Line Feeds No |
- | ║ │Config File Backups | + | ║ │Use |
- | ╚══════════════════════════════════════════════╝ | + | ║ │BSY Mutex File Timeout |
+ | ║ │BSO Lock Attempt Delay | ||
+ | ║ │BSO Lock Attempt Limit | ||
+ | ║ │BinkP Capabilities | ||
+ | ║ │BinkP Sysop Name | ||
+ | ║ │BinkP Authentication | ||
+ | ║ │BinkP Encryption | ||
+ | ╚═══════════════════════════════════════════════════╝ | ||
</ | </ | ||
=== Mailer Type === | === Mailer Type === | ||
Line 361: | Line 290: | ||
Selecting this menu item will toggle between the mailer types supported | Selecting this menu item will toggle between the mailer types supported | ||
by SBBSecho, either ArcMail/ | by SBBSecho, either ArcMail/ | ||
- | mailer type. | + | mailer type (e.g. [[module: |
== Log Level == | == Log Level == | ||
Line 383: | Line 312: | ||
Log Level should normally be set to '' | Log Level should normally be set to '' | ||
experiencing problems with SBBSecho and would like more verbose log | experiencing problems with SBBSecho and would like more verbose log | ||
- | output, set this to Debugging. If you want less verbose logging, | + | output, set this to '' |
set to higher-severity levels to reduce the number of log messages. | set to higher-severity levels to reduce the number of log messages. | ||
Line 389: | Line 318: | ||
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 400: | Line 329: | ||
enforcement of matching packet passwords, disable this option. | enforcement of matching packet passwords, disable this option. | ||
Default: Enabled | Default: Enabled | ||
- | |||
- | == Use FTN Domain/Zone Map == | ||
- | Use FTN Domain/Zone Map, when enabled, uses the configuration file | ||
- | '' | ||
- | and FTN zones and the relevant BSO outbound directory. | ||
- | Default: Disabled | ||
== BSY Mutex File Timeout == | == BSY Mutex File Timeout == | ||
Line 432: | Line 355: | ||
SBBSecho configuration file (e.g. '' | SBBSecho configuration file (e.g. '' | ||
maintained by SBBSecho Config and SBBSecho AreaFix. | maintained by SBBSecho Config and SBBSecho AreaFix. | ||
+ | |||
+ | == BinkP Capabilities == | ||
+ | Set this value if you need to override the the text in the BinkP '' | ||
+ | |||
+ | == BinkP Sysop Name == | ||
+ | Set this value if you'd like to over-ride the BinkP Sysop Name ('' | ||
=== Linked Nodes === | === Linked Nodes === | ||
Line 449: | Line 378: | ||
add a new node, pressing the DELete key will remove the currently | add a new node, pressing the DELete key will remove the currently | ||
highlighted node. A //Node// here does not necessarily identify a single FidoNet node, but can also be used to identify a group of nodes by using the '' | highlighted node. A //Node// here does not necessarily identify a single FidoNet node, but can also be used to identify a group of nodes by using the '' | ||
+ | |||
+ | **Note:**\\ | ||
+ | The hexadecimal numbers in parentheses are provided as an aide when correlating FidoNet files and BSO directories with node numbers. | ||
< | < | ||
- | ╔═══════════════════════════════════╗ | + | ╔══════════════════════════════════════════════════╗ |
- | ║ Linked Nodes | + | ║ |
- | ╠═══════════════════════════════════╣ | + | ╠══════════════════════════════════════════════════╣ |
- | ║ │2:280/464 | + | ║ │ALL Everyone |
- | ║ │3: | + | ║ │21:ALL |
- | ║ │1:218/700 | + | ║ │1:218/700 (00da02bc) |
- | ║ │ALL | + | ║ │3: |
- | ║ │ | + | ║ │2: |
- | ╚═══════════════════════════════════╝ | + | ║ │1:124/5016 |
+ | ║ │1: | ||
+ | ║ │1: | ||
+ | ║ │1: | ||
+ | ║ │21: | ||
+ | ║ │ | ||
+ | ╚══════════════════════════════════════════════════╝ | ||
</ | </ | ||
- | Pressing ENTER on the currently | + | Pressing ENTER on a currently |
highlighted node will allow you to edit the settings for that particular | highlighted node will allow you to edit the settings for that particular | ||
node from a menu like the following (note that the node number you are | node from a menu like the following (note that the node number you are | ||
Line 468: | Line 406: | ||
< | < | ||
╔═════════════════════════════════════════════╗ | ╔═════════════════════════════════════════════╗ | ||
- | ║ Linked Node - Kurt Weiske | + | ║ |
╠═════════════════════════════════════════════╣ | ╠═════════════════════════════════════════════╣ | ||
║ │Address | ║ │Address | ||
- | ║ │Comment | + | ║ │Domain |
+ | ║ │Name | ||
+ | ║ │Comment | ||
║ │Archive Type | ║ │Archive Type | ||
║ │Packet Type 2+ ║ | ║ │Packet Type 2+ ║ | ||
║ │Packet Password | ║ │Packet Password | ||
+ | ║ │Session Password | ||
║ │TIC File Password | ║ │TIC File Password | ||
+ | ║ │AreaFix Support | ||
║ │AreaFix Password | ║ │AreaFix Password | ||
- | ║ │AreaFix | + | ║ │EchoList |
║ │Status | ║ │Status | ||
║ │Direct | ║ │Direct | ||
Line 483: | Line 425: | ||
║ │Send Notify List | ║ │Send Notify List | ||
║ │Uplink for Message Groups | ║ │Uplink for Message Groups | ||
+ | ║ │Local Address (AKA) Best Match ║ | ||
║ │Route To | ║ │Route To | ||
║ │Inbox Directory | ║ │Inbox Directory | ||
║ │Outbox Directory | ║ │Outbox Directory | ||
+ | ║ │BinkP Settings... | ||
╚═════════════════════════════════════════════╝ | ╚═════════════════════════════════════════════╝ | ||
</ | </ | ||
Line 539: | Line 483: | ||
== Packet Type == | == Packet Type == | ||
- | This is the packet | + | This is the type of [[ref: |
packets for this node. The default packet type used by SBBSecho | packets for this node. The default packet type used by SBBSecho | ||
- | is 2+. If you are a " | + | is 2+. If you are a " |
- | should use either a type 2+ or 2.2 packet since type 2 packets | + | should use either a type 2+, 2e, or 2.2 packet since type 2 packets |
do not support point numbers. Selecting this option will allow | do not support point numbers. Selecting this option will allow | ||
you to choose from a menu of currently supported packet types: | you to choose from a menu of currently supported packet types: | ||
- | |||
< | < | ||
╔═════════════╗ | ╔═════════════╗ | ||
Line 564: | Line 507: | ||
must also have no password. | must also have no password. | ||
This setting may be managed by the node using AreaFix requests. | This setting may be managed by the node using AreaFix requests. | ||
+ | |||
+ | == Session Password == | ||
+ | When using [[module: | ||
== TIC File Password == | == TIC File Password == | ||
Line 570: | Line 516: | ||
or authenticating .TIC files. | or authenticating .TIC files. | ||
This setting may be managed by the node using AreaFix requests. | This setting may be managed by the node using AreaFix requests. | ||
+ | |||
+ | == AreaFix Support == | ||
+ | Remote area management (via AreaFix requests from this linked node) may be enabled (set to Yes) or disabled (set to No) using this menu option. | ||
== AreaFix Password == | == AreaFix Password == | ||
- | AreaFix | + | AreaFix |
- | NetMail | + | |
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. | ||
- | == Areafix | + | == EchoList |
When echo lists have been defined (from the | When echo lists have been defined (from the | ||
' | ' | ||
Line 620: | Line 568: | ||
== Inbox Directory == | == Inbox Directory == | ||
Inbox Directory is only used in BSO operating mode and is an optional | Inbox Directory is only used in BSO operating mode and is an optional | ||
- | alternate directory to search for incoming files from this node | + | alternate directory to search for incoming files from this node |
- | (e.g. used in combination with BinkD' | + | (e.g. used in combination with BinkD' |
+ | |||
+ | Note: [[module: | ||
== Outbox Directory == | == Outbox Directory == | ||
- | Outbox Directory is only used in BSO operating mode and is an optional | + | Outbox Directory is only used in BSO operating mode and is an optional |
alternate directory to place outbound files for this node (e.g. used | alternate directory to place outbound files for this node (e.g. used | ||
- | in combination with BinkD' | + | in combination with BinkD' |
+ | |||
+ | Note: [[module: | ||
+ | |||
+ | == BinkP Settings == | ||
+ | |||
+ | BinkP Settings are settings specific to BinkP/ | ||
+ | |||
+ | < | ||
+ | ╔═════════════════════════════════════╗ | ||
+ | ║ | ||
+ | ╠═════════════════════════════════════╣ | ||
+ | ║ │Host | ||
+ | ║ │Port | ||
+ | ║ │Poll | ||
+ | ║ │Authentication | ||
+ | ║ │Encryption | ||
+ | ║ │Source Address | ||
+ | ╚═════════════════════════════════════╝ | ||
+ | </ | ||
+ | |||
+ | **Host** defines the TCP/IP address or host name with which to connect for sessions with this linked node. If the host is not set, then a DNS-based look-up will be attempted (e.g. the IP address for 1:103/705 would be looked-up via host name f705.n103.z1.binkp.net). Nodelist-based look-ups are also supported. | ||
+ | |||
+ | **Port** defines the TCP port used by this linked node for BinkP sessions. The default BinkP TCP port is 24554. | ||
+ | |||
+ | **Poll** defines whether or not to periodically poll this linked node. | ||
+ | |||
+ | **Authentication** determines what types of authentication will be supported during both inbound and outbound sessions with this linked node. The supported BinkP-auth methods are // | ||
+ | |||
+ | **Encryption** determines whether unencrypted data transfers will be supported or required when communicating with this linked node. With this setting set to '' | ||
+ | |||
+ | **Source** Address allows you to override the source FTN address used with outgoing BinkP mailer sessions with this linked node. Normally, this setting is left blank (not set). | ||
=== Archive Types === | === Archive Types === | ||
Line 729: | Line 710: | ||
║ │Ignore NetMail Destination Address | ║ │Ignore NetMail Destination Address | ||
║ │Ignore NetMail ' | ║ │Ignore NetMail ' | ||
+ | ║ │Ignore NetMail ' | ||
║ │Ignore NetMail ' | ║ │Ignore NetMail ' | ||
║ │Ignore NetMail ' | ║ │Ignore NetMail ' | ||
Line 755: | Line 737: | ||
║ │Notify Users of Received EchoMail | ║ │Notify Users of Received EchoMail | ||
║ │Convert Existing Tear Lines No ║ | ║ │Convert Existing Tear Lines No ║ | ||
- | ║ │Strip Line Feeds from Outgoing Messages | + | ║ │Automatically Add New Subs to Area List List/File ║ |
- | ║ │Automatically Add New Subs to Area File | + | |
║ │Allow Nodes to Add Areas from Area File Yes ║ | ║ │Allow Nodes to Add Areas from Area File Yes ║ | ||
║ │Maximum Backups to Maintain of Area File | ║ │Maximum Backups to Maintain of Area File | ||
Line 783: | Line 764: | ||
== Secure Operation == | == Secure Operation == | ||
- | When set to '' | + | Secure Operation tells SBBSecho |
- | incoming mail packets | + | |
- | as messages are imported. If a packet password has been | + | |
- | defined for that node, it will also be compared | + | |
- | password contained in the mail packet. Packets and messages | + | |
- | failing | + | |
== Allow Nodes to Add Areas from Area File == | == Allow Nodes to Add Areas from Area File == | ||
Line 797: | Line 772: | ||
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 807: | Line 787: | ||
║ Paths and Filenames | ║ Paths and Filenames | ||
╠═══════════════════════════════════════════════════════╣ | ╠═══════════════════════════════════════════════════════╣ | ||
- | ║ │Non-secure Inbound Directory | + | ║ │Non-secure Inbound Directory |
- | ║ │Secure Inbound Directory | + | ║ │Secure Inbound Directory |
- | ║ │Outbound Directory | + | ║ │Outbound Directory |
║ │Area File ../ | ║ │Area File ../ | ||
║ │Bad Area File ../ | ║ │Bad Area File ../ | ||
Line 815: | Line 795: | ||
║ │Echo Statistics File | ║ │Echo Statistics File | ||
║ │Temporary File Directory | ║ │Temporary File Directory | ||
- | ║ │Outgoing Semaphore File ║ | + | ║ │Outgoing Semaphore File |
╚═══════════════════════════════════════════════════════╝ | ╚═══════════════════════════════════════════════════════╝ | ||
</ | </ | ||
Line 877: | Line 857: | ||
| | ||
This is an optional file to create/ | This is an optional file to create/ | ||
- | files created or updated by SBBSecho. | + | files created or updated by SBBSecho. |
+ | |||
+ | === Domains === | ||
+ | |||
+ | Here you can configure the so-called "5th dimension" | ||
+ | |||
+ | These are the domain-> | ||
+ | |||
+ | < | ||
+ | ╔══════════════════════╗ | ||
+ | ║ Domains | ||
+ | ╠══════════════════════╣ | ||
+ | ║ │fidonet | ||
+ | ║ │fsxnet | ||
+ | ║ │ ║ | ||
+ | ╚══════════════════════╝ | ||
+ | </ | ||
+ | |||
+ | Selecting a node to configure will display a dialog like the following: | ||
+ | < | ||
+ | ╔══════════════════════════════════════════════════════╗ | ||
+ | ║ | ||
+ | ╠══════════════════════════════════════════════════════╣ | ||
+ | ║ │Name | ||
+ | ║ │Zones | ||
+ | ║ │DNS Suffix | ||
+ | ║ │Outbound Root ../ | ||
+ | ║ │NodeList | ||
+ | ╚══════════════════════════════════════════════════════╝ | ||
+ | </ | ||
=== EchoLists === | === EchoLists === | ||
Line 926: | Line 935: | ||
in this list. If an area is remotely added from this list | in this list. If an area is remotely added from this list | ||
(using Areafix) this address is automatically added to the | (using Areafix) this address is automatically added to the | ||
- | AREAS.BBS file. | + | Area File. |
== Forward Password == | == Forward Password == | ||
Line 936: | Line 945: | ||
request to the Hub Address specified to turn on an area from | request to the Hub Address specified to turn on an area from | ||
this list. This happens when users remotely add areas using | this list. This happens when users remotely add areas using | ||
- | Areafix | + | AreaFix |
- | conferences in this list (i.e.: from Planet Connect). | + | conferences in this list. |
== AreaFix Keys == | == AreaFix Keys == | ||
Line 951: | Line 960: | ||
==== Environment Variable ==== | ==== Environment Variable ==== | ||
SBBSecho requires that the system '' | SBBSecho requires that the system '' | ||
+ | |||
==== 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 1018: | Line 1028: | ||
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 |