Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

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
Next revisionBoth sides next revision
util:sbbsecho [2017/11/13 15:00] – Define "Kludge Line" digital manutil:sbbsecho [2018/07/31 15:26] – Updated Secure Operation and Long Tags sections digital man
Line 4: Line 4:
  
 ===== Introduction ===== ===== Introduction =====
-SBBSecho is an FTN echomail program (tosser/scanner) for Synchronet BBS version 2.0 and higher. SBBSecho is not a [[resource:FidoNet mailer]] (you'll still need [[resource:fidonet_mailer|one of those]]).+SBBSecho is an FTN echomail program (tosser/scanner) for Synchronet BBS version 2.0 and higher. SBBSecho is not a [[resource:FidoNet mailer]] (you'll still need [[resource:fidonet_mailer|one of those]], e.g. [[module:BinkIT]]).
  
 As of SBBSecho v2.30 (Nov-2015), SBBSecho will also export FTN NetMail from the Synchronet mail base (''data/mail'' message base) to FTS-1 (''*.msg'') files. As of SBBSecho v2.30 (Nov-2015), SBBSecho will also export FTN NetMail from the Synchronet mail base (''data/mail'' message base) to FTS-1 (''*.msg'') files.
-  * This feature allows the gating of SMTP (Internet e-mail) to FTN netmail by sending email to "**//name//@p//<point>//.f//<node>//.n//<net>//.z//<zone>//.fidonet**" or "**//name//@.f//<node>//.n//<net>//.z//<zone>//.fidonet**". The [[server:Mail|Synchronet Mail Server]] rev 1.588 (Nov-24-2015) or later will accept email addressed in this manner and save the messages in the mail base as FidoNet netmail. +  * This feature allows the gating of SMTP (Internet e-mail) to FTN netmail by sending email to "**//name//@p//<point>//.f//<node>//.n//<net>//.z//<zone>//.fidonet**" or "**//name//@f//<node>//.n//<net>//.z//<zone>//.fidonet**". The [[server:Mail|Synchronet Mail Server]] rev 1.588 (Nov-24-2015) or later will accept email addressed in this manner and save the messages in the mail base as FidoNet netmail, when addressed to a local BBS user name or alias. 
-  * This feature allows FidoNet netmail to be sent using JavaScript methods (e.g. via the [[server:web|Synchronet Web Server]])+  * This feature allows FidoNet netmail to be sent using JavaScript methods (e.g. via the [[server:web|Synchronet Web Server]]) as well as [[util:smbutil]] and [[module:postmsg]].
  
 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. Here we attempt to define some terms we will be using through this article to describe the features and functions of SBBSecho.+The terminology used with FidoNet networking technology can be as confusing as it is particular. In our [[ref:FidoNet Glossary]] we attempt to define some terms we will be using through-out this article to describe the features and functions of SBBSecho. If you come across a term you aren't familiar with, please check the [[ref:FidoNet Glossary]].
    
-==== FTN ==== +===== Installation =====
-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 (i.e. their executables can be found in your Synchronet ''[[dir:exec]]'' directory. So it usually requires no special installation steps of its own.
-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:Net/Node.Point +
- +
-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's zone is assumed. +
- +
-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's +
-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:net/node.0). When the point +
-is not specified, 0 (zero) is assumed (i.e. ''1:2/3'' and ''1:2/3.0'' are identical) +
-which indicates the system with that address is **not** a point node. +
- +
-Zones can be grouped into named domains (e.g. ''@fidonet''), but FTN domains +
-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. ''103/705''). +
- +
-A 3D (3 dimensional) address refers to an FTN address containing the zone, +
-net, and node numbers (e.g. ''1:103/705''), specifically excluding the point number +
-if it exists. +
- +
-A 4D (4 dimensional) address refers to an FTN address containing the zone, +
-net, node, and optional point numbers (e.g. ''1:103/705.1''). +
- +
-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''). +
- +
-==== Node ==== +
-All FidoNet node-listed systems are //nodes// of the network. +
- +
-**Normal Nodes** do not have a //point// value, so a ''.0'' suffix on their address is implied. The addresses ''1:103/705'' and ''1:103/705.0'' are the same node, a normal node (sometimes also called a //boss node//). +
- +
-**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 ''1:103/705.1'' would be ''1:103/705'' (the ''.0'' point value is implied). Point nodes are not listed in the network's official nodelist. Some network regions distribute a //pointlist// containing only point nodes. +
- +
-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.).  Linked Nodes may also be linked with one or more EchoMail message areas on your system as reflected in your Area File. +
- +
-==== 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. +
- +
-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. +
- +
-==== 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). +
- +
-==== Downlink ==== +
- +
-A //Downlink// is a Linked Node which your system "feeds" messages and for which your system is responsible for routing received messages from. +
- +
-==== Attach or FLO Mailer? ==== +
- +
-If you are using FrontDoor, InterMail, D'bridge, SEAdog, Dutchie, or any other +
-ArcMail *.MSG attach-style mailer, you are using what we will refer to as an +
-"ArcMail/Attach-style Mailer". Support for ArcMail/Attach-style mailers has been deprecated in SBBSecho v3 and unless there is anyone coming forward to test what support does remain, it will be removed in the future. +
- +
-If you are using BinkD (Binkley daemon), Argus/Radius/Taurus, BinkleyTerm, Portal of Power, or any other mailer that uses Binkley-Style-Outbound (BSO) directories and FLO/CLO/HLO/DLO files (a.k.a. FLO-files), you are using what we will refer to as a "Binkley/FLO-Style Mailer". +
- +
-It is very important that you select the correct "Mailer Type" in the ''[[util:echocfg]]'' utility (or ''sbbsecho.ini'' file). +
- +
-==== NetMail ==== +
- +
-Point-to-point (usually person-to-person) directly-delivered or routed messages (now more commonly referred to as "e-mail" or just "mail"). +
- +
-==== 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" for this reason. +
- +
-==== 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 ''.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. +
- +
-=== 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.  +
- +
-== Identifying Bad Packets == +
- +
-  - File length is shorter than a packet header (58 bytes) +
-  - Packet terminator (''0x0000'', 2 NUL bytes) missing from end of the file +
-  - File read failure (e.g. permissions or file locking issue) +
-  - Source address does not match expected address (e.g. for packets found in //inboxes//) +
-  - Packet header cannot be parsed (e.g. is not a ''type 2'' packet header) +
-  - Packet header contains incorrect packet password +
-  - Packet contains one or more "grunged messages" (e.g. packed //message type// is not ''2'') +
-==== 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 ''.?_?'' or ''.?-?'' (e.g. ''*.mo0'' would be renamed to ''*.m_0''). +
- +
-==== AreaFix/Area Manager ==== +
- +
-AreaFix is a synonym for area manager (the very first FTN area manager +
-program was called "AreaFix"). Area manager capabilities (remote adding/removing +
-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. The Area Manager process has also be called a "Conference Manager" ([[http://ftsc.org/docs/fsc-0057.003|ConfMgr]]). +
- +
-==== Kludge Line ====  +
-Due to historic FTN message and packet header limitations, some message metadata was defined in 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 define different metadata values.  +
- +
-Kludge/control lines are not normally displayed to messages viewers (users), but most programs have an option to view the control lines where it is customary to replace the Ctrl-A character with an ''@'' character. +
- +
-Synchronet stores FTN control lines in its message headers, so you must use the Terminal Server operator->View Header command (''H''), to view a message header to see the metadata that may have been received via FTN kludge lines. +
- +
-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. ''areas.bbs'') in your Synchronet ''[[dir:data]]'' SBBSecho expects to find an area file (e.g. ''areas.bbs'') in your Synchronet ''[[dir:data]]''
-directory. You will need to create the Area File in order for SBBSecho to do anything with EchoMail message areas.+directory. You will need to create the Area File in order for SBBSecho to do anything with EchoMail messages. Importing and exporting //NetMail// does not require an area file.
  
 [[util:SCFG]] can also export a group of message areas (sub-boards) to an SBBSecho-compatible Area File. [[util:SCFG]] can also export a group of message areas (sub-boards) to an SBBSecho-compatible Area File.
-You may want to import a network's EchoList (e.g. FidoNet's ''BACKBONE.NA'') into a message group (using [[util:SCFG]]) first and then export the networked message group(s) from [[util:SCFG]] to the SBBSecho-compatible Area File once you're linked successfully with your network hub.+You may want to first import a network's EchoList (e.g. FidoNet's ''BACKBONE.NA'') into a message group (using [[util:SCFG]]) and then export the networked message group(s) from [[util:SCFG]] to the SBBSecho-compatible Area File once you're linked successfully with your network hub. 
 + 
 +If the ''AutoAddSubs'' feature is enabled, sub-boards configured in SCFG->Message Areas may be //automatically// added to your Area File when the network hub (your uplink) has be configured in EchoCfg->Linked Nodes and the "Group Hub" setting for that link set to the name of the corresponding message group in SCFG->Message Areas. This Auto-Add procedure happens during SBBSecho initialization and is not dependent upon receiving any echomail messages for the configured message areas.
  
 ===== Area File Format ===== ===== Area File Format =====
Line 195: Line 46:
  
 === Long Tags === === Long Tags ===
-Although standard FidoNet echo tags may be as long as 35 characters, Synchronet's Sub-board //short names// are limited to 25 characters. When importing and exporting FTN areas (e.g. to/from ''areas.bbs'' or EchoList files), usually the echo tag is copied to or derived from the associated Sub-board's short name. For this reason, echo tags longer than 25 characters in length may present a problem for some import/export or auto-create scenarios.+Although standard FidoNet echo tags (AKA "area tag") may be as long as 35 characters, Synchronet's Sub-board //short names// are limited to a length of 25 characters. As of July 28, 2018, Synchronet v3.17a will import (e.g. from a ''BACKBONE.NA'' file) echo tags longer than 25 characters into the "Newsgroup" name of the sub-board. Each sub-board's "Newsgroup" name can accommodate a length of up to 63 characters (no spaces). Likewise, when exporting message areas from SCFG or SBBSecho (e.g. to an ''areas.bbs'' file), if a "Newsgroup" name is defined for a message area, it will be used for the exported echo tag of that exported area.
  
 === Bad Echo Area === === Bad Echo Area ===
Line 213: Line 64:
 </file> </file>
  
-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 ===== ===== Configuration =====
Line 230: Line 80:
 ╠══════════════════════════════════════════════════════════╣ ╠══════════════════════════════════════════════════════════╣
 ║ │System Addresses                                        ║ ║ │System Addresses                                        ║
-║ │Default Outbound Address   No                           ║ 
 ║ │Default Origin Line                                     ║ ║ │Default Origin Line                                     ║
 ║ │NetMail Semaphore          %jfidoout.now                ║ ║ │NetMail Semaphore          %jfidoout.now                ║
 ║ │EchoMail Semaphore         %jfidoout.now                ║ ║ │EchoMail Semaphore         %jfidoout.now                ║
-║ │NetMail Directory          /sbbs/netmail\               ║ +║ │NetMail Directory          ../fido/netmail/             ║ 
-║ │Allow Sending of NetMail   No                           ║ +║ │Allow Sending of NetMail   Yes                          ║ 
-║ │Allow File Attachments     Yes                          ║+║ │Allow File Attachments     No                           ║
 ║ │Send NetMail Using Alias   No                           ║ ║ │Send NetMail Using Alias   No                           ║
 ║ │NetMail Defaults to Crash  No                           ║ ║ │NetMail Defaults to Crash  No                           ║
Line 255: Line 104:
  
 === System Addresses === === System Addresses ===
-Set your main/primary FidoNet address and AKAs (secondary FTN addresses) here. If you only have a temporary address, set your //Main// address to that value.+Set your main/primary FidoNet address and AKAs (secondary/othernet FTN addresses) here. If you only have a temporary address, set your //Main// address to that value. 
 + 
 +Only 3D (zone:net/node) and 4D (zone:net/node.point) addresses are supported in this setting.
  
 === 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:fidonet_files#stored_message|Stored Messages]] (''*.msg'') format).+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:fidonet_files#stored_message|Stored Messages]] (''*.msg'' format).
  
 Synchronet can create ''*.msg'' files in this directory when sending NetMail from the terminal server. Synchronet can create ''*.msg'' files in this directory when sending NetMail from the terminal server.
  
-SBBSecho will create ''*.msg'' files in this directory when creating NetMail messages (e.g. auto-responding to ''PING'' or ''AreaFix'' requests, notices to the //Area Manager//, or exporting NetMail from the "mail" msgbase) or exporting NetMail from inbound [[ref:fidonet_files#packet|Packets]]. SBBSecho will discover ''*.msg'' files in this directory when Packing outbound NetMail, importing into the "mail" msgbase, or handling AreaFix and PING requests.+SBBSecho will create ''*.msg'' files in this directory when creating NetMail messages (e.g. auto-responding to ''PING'' or ''AreaFix'' requests, notices to the //Area Manager//, or exporting NetMail from the "mail" msgbase) or unpacking NetMail from inbound [[ref:fidonet_files#packet|Packets]]. SBBSecho will discover ''*.msg'' files in this directory when Packing outbound NetMail, importing into the "mail" msgbase, or handling AreaFix and PING requests.
  
-The other NetMail-related settings on this menu affect only FidoNet NetMail messages created by the Synchronet [[:server:Terminal]] Server; they are not used by SBBSecho.+The other NetMail-related settings on this [[util:SCFG]] menu affect only FidoNet NetMail messages created by users of the Synchronet [[:server:Terminal]] Server; they are not used by SBBSecho.
  
 === Default Origin Line === === Default Origin Line ===
 Standard FTN EchoMail messages contain a terminating ''* Origin'' line. The default Origin Line, or at least the portion between the ''* Origin'' prefix and your system's address in parenthesis, is configured here. You do not have to enter an Origin Line here, but it is customary to enter the name, hostname or IP address and/or phone number of your BBS here. SBBSecho will use the text in this setting as the default Origin Line to append to outbound EchoMail messages (posted locally or gated from other network technologies). Standard FTN EchoMail messages contain a terminating ''* Origin'' line. The default Origin Line, or at least the portion between the ''* Origin'' prefix and your system's address in parenthesis, is configured here. You do not have to enter an Origin Line here, but it is customary to enter the name, hostname or IP address and/or phone number of your BBS here. SBBSecho will use the text in this setting as the default Origin Line to append to outbound EchoMail messages (posted locally or gated from other network technologies).
 +
 +It is possible to over-ride this default Origin Line for specific message areas (sub-boards), if so desired by the sysop.
  
 === Inbound File Directory === === Inbound File Directory ===
Line 275: Line 128:
 ==== 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 (''[[config:sbbsecho.ini]]'').+The SBBSecho Config program (''echocfg'') is the program used to configure all the SBBSecho-specific settings saved exclusively in the SBBSecho configuration file (''[[config:sbbsecho.ini]]'').
  
 === Command-line Syntax === === Command-line Syntax ===
Line 313: Line 166:
 <code> <code>
 ╔═════════════════════════╗ ╔═════════════════════════╗
-║    Configure SBBSecho   ║+║    Configure FidoNet    ║
 ╠═════════════════════════╣ ╠═════════════════════════╣
 ║ │Global Settings...     ║ ║ │Global Settings...     ║
Line 321: Line 174:
 ║ │EchoMail Settings...   ║ ║ │EchoMail Settings...   ║
 ║ │Paths and Filenames... ║ ║ │Paths and Filenames... ║
 +║ │Domains...             ║
 ║ │EchoLists...           ║ ║ │EchoLists...           ║
 ╚═════════════════════════╝ ╚═════════════════════════╝
 +
 </code> </code>
  
Line 349: Line 204:
 ╠══════════════════════════════════════════════╣ ╠══════════════════════════════════════════════╣
 ║ │Mailer Type               Binkley/FLO       ║ ║ │Mailer Type               Binkley/FLO       ║
-║ │Log Level                 Informational     ║+║ │Log Level                 Debugging         ║
 ║ │Log Timestamp Format      %m/%d/%y %H:%M:%S ║ ║ │Log Timestamp Format      %m/%d/%y %H:%M:%S ║
 ║ │Strict Packet Passwords   Enabled           ║ ║ │Strict Packet Passwords   Enabled           ║
-║ │Use FTN Domain/Zone Map   Disabled          ║ 
 ║ │BSY Mutex File Timeout    12 hours          ║ ║ │BSY Mutex File Timeout    12 hours          ║
 ║ │BSO Lock Attempt Delay    10 seconds        ║ ║ │BSO Lock Attempt Delay    10 seconds        ║
 ║ │BSO Lock Attempt Limit    60                ║ ║ │BSO Lock Attempt Limit    60                ║
 ║ │Config File Backups       100               ║ ║ │Config File Backups       100               ║
 +║ │BinkP Capabilities                          ║
 +║ │BinkP Sysop Name                            ║
 ╚══════════════════════════════════════════════╝ ╚══════════════════════════════════════════════╝
 </code> </code>
Line 369: Line 225:
 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/Attach-style mailers or (the preferred) Binkley/FLO-style mailers.  Choose the one that matches your FTN by SBBSecho, either ArcMail/Attach-style mailers or (the preferred) Binkley/FLO-style mailers.  Choose the one that matches your FTN
-mailer type.+mailer type (e.g. [[module:BinkIT]] is a Binkley/FLO-style mailer).
  
 == Log Level == == Log Level ==
Line 391: Line 247:
 Log Level should normally be set to ''Informational'' but if you're          Log Level should normally be set to ''Informational'' but if you're         
 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 ''Debugging''. If you want less verbose logging,    
 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 408: Line 264:
 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    
-''ctrl/ftn_domains.ini'' to determine the mapping between FTN domains 
-and FTN zones and the relevant BSO outbound directory.            
-Default: Disabled                                                 
  
 == BSY Mutex File Timeout == == BSY Mutex File Timeout ==
Line 440: Line 290:
 SBBSecho configuration file (e.g. ''sbbsecho.ini'') that will be        SBBSecho configuration file (e.g. ''sbbsecho.ini'') that will be       
 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 ''M_NUL NDL'' line, from the default of "115200,TCP,BINKP".
 +
 +== BinkP Sysop Name ==
 +Set this value if you'd like to over-ride the BinkP Sysop Name (''ZYZ'') value (e.g. to send the sysop's real name, rather than alias).
  
 === Linked Nodes === === Linked Nodes ===
Line 457: Line 313:
 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 ''ALL'' wildcard (indicating that a node configuration will be used for *all* nodes with a specific zone or zone:net). 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 ''ALL'' wildcard (indicating that a node configuration will be used for *all* nodes with a specific zone or zone:net).
 +
 +**Note:**\\
 +The hexadecimal numbers in parentheses are provided as an aide when correlating FidoNet files and BSO directories with node numbers.   
 <code> <code>
-╔═══════════════════════════════════╗ +╔══════════════════════════════════════════════════╗ 
-║            Linked Nodes           ║ +║                   Linked Nodes                   ║ 
-╠═══════════════════════════════════╣ +╠══════════════════════════════════════════════════╣ 
-║ │2:280/464                        ║ +║ │ALL                          Everyone           ║ 
-║ │3:712/848                        ║ +║ │21:ALL           (.015)      fsxNet             ║ 
-║ │1:218/700                        ║ +║ │1:218/700        (00da02bc)  Kurt Weiske        ║ 
-║ │ALL                     Everyone ║ +║ │3:712/848        (02c80350)  Scott Little       ║ 
-║ │                                 ║ +║ │2:280/464        (011801d0)  Wilfred van Velzen ║ 
-╚═══════════════════════════════════╝+║ │1:124/5016       (007c1398)  Nigel Reed         ║ 
 +║ │1:153/757        (009902f5)  Al                 ║ 
 +║ │1:320/219        (014000db)                     ║ 
 +║ │1:320/119        (01400077)                     ║ 
 +║ │21:1/100         (00010064)  Paul Hayton (Avon) ║ 
 +║ │                                                ║ 
 +╚══════════════════════════════════════════════════╝
 </code> </code>
  
-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 476: Line 341:
 <code> <code>
 ╔═════════════════════════════════════════════╗ ╔═════════════════════════════════════════════╗
-║          Linked Node - Kurt Weiske          ║+║           Linked Node - 1:218/700           ║
 ╠═════════════════════════════════════════════╣ ╠═════════════════════════════════════════════╣
 ║ │Address                        1:218/700   ║ ║ │Address                        1:218/700   ║
-║ │Comment                        Kurt Weiske ║+║ │Domain                         fidonet     ║ 
 +║ │Name                           Kurt Weiske ║ 
 +║ │Comment                                    ║
 ║ │Archive Type                   ZIP         ║ ║ │Archive Type                   ZIP         ║
 ║ │Packet Type                    2+          ║ ║ │Packet Type                    2+          ║
 ║ │Packet Password                            ║ ║ │Packet Password                            ║
 +║ │Session Password                           ║
 ║ │TIC File Password                          ║ ║ │TIC File Password                          ║
 +║ │AreaFix Support                Yes         ║
 ║ │AreaFix Password                           ║ ║ │AreaFix Password                           ║
-║ │AreaFix Keys                               ║+║ │EchoList Keys                              ║
 ║ │Status                         Normal      ║ ║ │Status                         Normal      ║
 ║ │Direct                         No          ║ ║ │Direct                         No          ║
Line 494: Line 363:
 ║ │Inbox Directory                            ║ ║ │Inbox Directory                            ║
 ║ │Outbox Directory                           ║ ║ │Outbox Directory                           ║
 +║ │BinkP Settings...                          ║
 ╚═════════════════════════════════════════════╝ ╚═════════════════════════════════════════════╝
 </code> </code>
Line 547: Line 417:
  
 == Packet Type == == Packet Type ==
-This is the packet type that will be used when creating mail+This is the type of [[ref:fidonet packets]] that will be used when creating mail
 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 "point" address (e.g. ''1:100/100.1'') you +is 2+. If you are a "point" address (e.g. ''1:100/100**.1**'') you 
-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:
- 
 <code> <code>
 ╔═════════════╗ ╔═════════════╗
Line 572: Line 441:
 must also have no password.  Packet passwords are case insensitive.  must also have no password.  Packet 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.     
 +
 +== Session Password ==
 +When using [[module:BinkIT]] as your mailer, this setting will determine the BinkP session password used when communicating with this linked node.
  
 == TIC File Password == == TIC File Password ==
Line 578: Line 450:
 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 Password is an optional password used to enable AreaFix      +AreaFix passwords are required to be included in the //Subject// line of received AreaFix requests (NetMail messages).
-NetMail requests (Remote Area Management) from this node.       +
 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 Keys ==+== EchoList Keys ==
 When echo lists have been defined (from the When echo lists have been defined (from the
 'EchoLists...' sub-menu) these keys determine 'EchoLists...' sub-menu) these keys determine
Line 635: Line 509:
 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's obox setting).                           in combination with BinkD's obox setting).                          
 +
 +== BinkP Settings ==
 +
 +BinkP Settings are settings specific to BinkP/BinkIT mailer operation.
 +
 +<file>
 +╔═════════════════════════════╗
 +║   1:218/700 BinkP Settings  ║
 +╠═════════════════════════════╣
 +║ │Host                       ║
 +║ │Port                 24554 ║
 +║ │Poll                 Yes   ║
 +║ │Allow Plain Auth     No    ║
 +║ │Allow Plain Text     No    ║
 +║ │Source Address             ║
 +╚═════════════════════════════╝
 +</file>
  
 === Archive Types === === Archive Types ===
Line 791: Line 682:
  
 == Secure Operation == == Secure Operation ==
-When set to ''Yes'', SBBSecho will compare the origin of any +Secure Operation tells SBBSecho to check the Area File (e.g. ''areas.bbs'') to insure that the packet origin (FTN //address//) of each inbound EchoMail message is already linked to the EchoMail //area// where the message was posted. Messages denied import due to this setting are logged as a ''Security violation''. This setting defaults to ''No''.                                        
-incoming mail packets to the nodes in the Area File +
-as messages are imported.  If a packet password has been +
-defined for that node, it will also be compared to the +
-password contained in the mail packet. Packets and messages +
-failing this security will not be imported. +
  
 == Allow Nodes to Add Areas from Area File == == Allow Nodes to Add Areas from Area File ==
Line 815: Line 700:
 ║                  Paths and Filenames                  ║ ║                  Paths and Filenames                  ║
 ╠═══════════════════════════════════════════════════════╣ ╠═══════════════════════════════════════════════════════╣
-║ │Non-secure Inbound Directory   e:\binkd\nonsecure    ║ +║ │Non-secure Inbound Directory   ../fido/nonsecure     ║ 
-║ │Secure Inbound Directory       e:/binkd/inbound      ║ +║ │Secure Inbound Directory       ../fido/inbound       ║ 
-║ │Outbound Directory             e:\binkd\outbound\    ║+║ │Outbound Directory             ../fido/outbound/     ║
 ║ │Area File                      ../data/areas.bbs     ║ ║ │Area File                      ../data/areas.bbs     ║
 ║ │Bad Area File                  ../data/badareas.lst  ║ ║ │Bad Area File                  ../data/badareas.lst  ║
Line 823: Line 708:
 ║ │Echo Statistics File           ../data/echostats.ini ║ ║ │Echo Statistics File           ../data/echostats.ini ║
 ║ │Temporary File Directory       ../temp/sbbsecho      ║ ║ │Temporary File Directory       ../temp/sbbsecho      ║
-║ │Outgoing Semaphore File                              ║+║ │Outgoing Semaphore File        ../data/binkout.now   ║
 ╚═══════════════════════════════════════════════════════╝ ╚═══════════════════════════════════════════════════════╝
 </code> </code>
Line 885: Line 770:
                                                                                                                                                  
 This is an optional file to create/touch whenever there are new outbound This is an optional file to create/touch whenever there are new outbound
-files created or updated by SBBSecho.                                   +files created or updated by SBBSecho.  If you're using [[module:BinkIt]] as your mailer, then this should normally be set to ''../data/binkout.now''. 
 + 
 +=== Domains === 
 + 
 +Here you can configure the so-called "5th dimension" of FidoNet addresses, //"domains"//, here. 
 + 
 +These are the domain->zone mapping that //used// to be configured via the file: ''ftn_domains.ini'' (but is now configured in ''sbbsecho.ini'' and this utility). 
 + 
 +<file> 
 +╔══════════════════════╗ 
 +║        Domains       ║ 
 +╠══════════════════════╣ 
 +║ │fidonet   binkp.net ║ 
 +║ │fsxnet              ║ 
 +║ │                    ║ 
 +╚══════════════════════╝ 
 +</file> 
 + 
 +Selecting a node to configure will display a dialog like the following: 
 +<file> 
 +╔══════════════════════════════════════════════════════╗ 
 +║                   Domain - fidonet                   ║ 
 +╠══════════════════════════════════════════════════════╣ 
 +║ │Name                           fidonet              ║ 
 +║ │Zones                          1,2,3,4,5,6          ║ 
 +║ │DNS Suffix                     binkp.net            ║ 
 +║ │Outbound Root                  ../fido/outbound/    ║ 
 +║ │NodeList                                            ║ 
 +╚══════════════════════════════════════════════════════╝ 
 +</file>
  
 === EchoLists === === EchoLists ===
Line 934: Line 848:
 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 944: Line 858:
 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 and is not necessary if you are already receiving the +AreaFix and is not necessary if you are already receiving the 
-conferences in this list (i.e.: from Planet Connect).+conferences in this list.
  
 == AreaFix Keys == == AreaFix Keys ==
Line 959: Line 873:
 ==== Environment Variable ==== ==== Environment Variable ====
 SBBSecho requires that the system ''[[config:env#SBBSCTRL]]'' environment variable be set correctly before it may be executed. When SBBSecho is executed from the Synchronet Terminal Server's Event Thread (e.g. due to ''FIDOIN'' or ''FIDOOUT'' timed events), this environment variable will always be set correctly, automatically. SBBSecho requires that the system ''[[config:env#SBBSCTRL]]'' environment variable be set correctly before it may be executed. When SBBSecho is executed from the Synchronet Terminal Server's Event Thread (e.g. due to ''FIDOIN'' or ''FIDOOUT'' timed events), this environment variable will always be set correctly, automatically.
 +
 ==== Instances ==== ==== Instances ====
  

Trace: