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
util:sbbsecho [2019/08/23 15:42] – Describe AreaFile-less operation, updated echocfg screens, etc. digital manutil:sbbsecho [2024/11/08 23:33] (current) – [Area Manager Commands] update help to reflect SBBSecho v3.21 AreaMgr request format digital man
Line 1: Line 1:
-====== SBBSecho ======+====== SBBSecho - FidoNet Tosser ======
    
 Synchronet's FidoNet EchoMail Program Synchronet's FidoNet EchoMail Program
Line 20: Line 20:
 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 the program itself usually requires no special installation steps of its own. 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 the program itself usually requires no special installation steps of its own.
  
-Thing you should have before you proceed:+Things you should have before you proceed:
   - Your hub/uplink's FidoNet address   - Your hub/uplink's FidoNet address
   - Your hub/uplink's Internet hostname or IP address   - Your hub/uplink's Internet hostname or IP address
-  - Your own FidoNet address+  - Your own FidoNet address (use ''<//zone//>:<//net//>/9999'' if you have not yet been assigned a FidoNet address)
   - Your hub-agreed-upon BinkP session password   - Your hub-agreed-upon BinkP session password
   - Your hub-agreed-upon packet password (optional)   - Your hub-agreed-upon packet password (optional)
Line 65: Line 65:
 </file> </file>
  
 +An alternative method is to instead subscribe/link to the echoes (on your hub/uplink) you wish to carry on your BBS (e.g. via AreaFix request netmail message) and then as SBBSecho attempts to import received packets, it will add unknown areas to your ''[[dir:data]]/badareas.lst'' file. Import that file (''badareas.lst'') into SCFG->Message Areas->FidoNet. SBBSecho will automatically remove "known" areas from the ''badareas.lst'' file after they've been added to SCFG. You will lose some EchoMail messages using this scheme.
 ===== Area File ===== ===== Area File =====
  
-By default, SBBSecho will try to open an //Area File// (by default, ''[[dir:data]]/areas.bbs''). The Area File can be used to associate FidoNet EchoTags with sub-boards configured in [[util:SCFGG]]. You can also specify downlinks and pass-through areas in an Area File, if need be. The Area File is optional, not strictly needed, when you have the "Automatically Add New Subs to Area List" option enabled and set to "List Only" in [[util:EchoCfg]]->EchoMail Settings.+By default, SBBSecho will try to open an //Area File// (by default, ''[[dir:data]]/areas.bbs''). The Area File can be used to associate FidoNet EchoTags with sub-boards configured in [[util:SCFG]]->Message Areas. You can also specify downlinks and pass-through areas in an Area File, if need be. The Area File is optional, not strictly needed, when you have the "Automatically Add New Subs to Area List" option enabled and set to "List Only" in [[util:EchoCfg]]->EchoMail Settings.
  
-To successfully operate without an Area File, you must have your hub configured in [[util:EchoCfg]]->Linked Nodes with its "Uplink for Message Groups" setting set to the //short name// of the message group you created in [[util:SCFG]]->Message Areas for this network.+To successfully operate without an Area File, you must have your hub configured in [[util:EchoCfg]]->Linked Nodes with its "Uplink for Message Groups" setting set to the //short name// of the message group you created for this network in [[util:SCFG]]->Message Areas.
  
 You will need an Area File if you are to have any downlinks (nodes for which you are //their// hub to the network). You will need an Area File if you are to have any downlinks (nodes for which you are //their// hub to the network).
Line 127: Line 128:
    
 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 [[util:SCFG]]->Networks->FidoNet. 
-  - Use the ''[[util:echocfg]]'' utility (highly recommended) or edit your ''[[dir:ctrl]]/sbbsecho.ini'' configuration (text) file by hand+  - Use the ''[[util:EchoCfg]]'' utility (highly recommended) or edit your ''[[dir:ctrl]]/sbbsecho.ini'' configuration (text) file by hand
  
 ==== SCFG ==== ==== SCFG ====
Line 181: Line 182:
  
 === 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 ''Non-secure Inbound Directory'' setting in EchoCfg/''[[config:sbbsecho.ini]]'' and removed from future versions of [[SCFG]].+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 ''Non-secure Inbound Directory'' setting in EchoCfg/''[[config:sbbsecho.ini]]'' and removed from future versions of [[SCFG]]).
  
  
Line 317: Line 318:
 Log Timestmap Format defines the format of the date/time-stamps added   Log Timestmap Format defines the format of the date/time-stamps added  
 along with each log message to the log file (e.g. ''sbbsecho.log'').    along with each log message to the log file (e.g. ''sbbsecho.log'').   
-The timestamp format is defined using standard C ''strftime'' notation.+The timestamp format is defined using standard C ''[[custom:strftime]]'' notation.
 The default format is: ''%Y-%m-%d %H:%M:%S''.            The default format is: ''%Y-%m-%d %H:%M:%S''.           
 For SBBSecho v2 timestamp format, use ''%m/%d/%y %H:%M:%S''.             For SBBSecho v2 timestamp format, use ''%m/%d/%y %H:%M:%S''.            
Line 520: Line 521:
  
 == AreaFix Password == == AreaFix Password ==
-AreaFix passwords are required to be included in the //Subject// line of received AreaFix requests (NetMail messages). +AreaFix passwords (AKA AreaManager passwords) are required to be included in the //Subject// line of received AreaFix/AreaManager requests (NetMail messages). 
-AreaFix Passwords are case insensitive.                         +AreaFix Passwords are case insensitive and cannot contain spaces.                         
 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 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 "4".
  
 === Paths and Filenames === === Paths and Filenames ===
Line 944: Line 950:
 == 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 'Linked Nodes...' sub-menu.+to chosen nodes in the 'Linked Nodes...' sub-menu.
 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 963:
 ==== Instances ==== ==== Instances ====
  
-SBBSecho is designed to run only one instance at a time. A mutual-exclusion file (''[[dir:ctrl]]/sbbsecho.bsy'') is used to insure that multiple instances of SBBSecho are not allowed to execute concurrently. If SBBSecho crashes or is externally-killed without being able clean up after itself, it's possible this mutex file will be left behind and prevent SBBSecho from running normally for quite some time (depending on the configuration value of ''BSY Mutex File Timeout'').+SBBSecho is designed to run only one instance at a time. A mutual-exclusion file (''[[dir:ctrl]]/sbbsecho.bsy'') is used to insure that multiple instances of SBBSecho are not allowed to execute concurrently. If SBBSecho crashes or is externally-killed without being able to clean up after itself, it's possible this mutex file will be left behind and prevent SBBSecho from running normally for quite some time (depending on the configuration value of ''BSY Mutex File Timeout'').
  
 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 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 ''[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/exec/areamgr.hlp|areangr.hlp]]'' which, after installation of+The following text is from the file ''[[https://gitlab.synchro.net/main/sbbs/-/raw/master/exec/areamgr.hlp|areamgr.hlp]]'' which, after installation of
 SBBSecho, should be located in your Synchronet ''[[dir:exec]]'' directory. This file lists the SBBSecho, should be located in your Synchronet ''[[dir:exec]]'' directory. This file lists the
 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 ''[[util:echocfg]]'' program: the ''[[util:echocfg]]'' program:
 <file> <file>
-Address all requests to 'SBBSecho' or 'AreaFix' (without quotes). +Address all Area Management requests to 'AreaFix' (without quotes). 
-Your Area Manager password goes on the subject line.+Your Area Manager password goes in the message subject followed optionally 
 +by -R, -L, or -Q for Rescan, List, or Query functions, respectively.
  
-In the body of the message to Area Manager:+In the body of the message, one or more:
  
-[+]<areaname>         Connect an area +<areatag>             Connect a message area (echo) 
--<areaname>           Disconnect an area+-<areatag>            Disconnect an area
 %HELP                 Request this message %HELP                 Request this message
-%LIST                 Request a list of areas available to you+%LIST                 Request a list of areas (tags) available to you
 %QUERY                Request a list of areas to which you are connected %QUERY                Request a list of areas to which you are connected
 %UNLINKED             Request a list of areas to which you are not connected %UNLINKED             Request a list of areas to which you are not connected
-%COMPRESSION <type>   Change the compression type (e.g. ARC/ARJ/LZH/PAK/SQZ/ZIP/ZOO)+%COMPRESSION <type>   Change the compression type (e.g. ARC, ARJ, LZH, ZIP)
 %PASSWORD <password>  Change your Area Manager password %PASSWORD <password>  Change your Area Manager password
 %PKTPWD <password>    Set or change your Packet password %PKTPWD <password>    Set or change your Packet password
 %TICPWD <password>    Set or change your TIC File password %TICPWD <password>    Set or change your TIC File password
 %RESCAN               Request a rescan of all connected areas %RESCAN               Request a rescan of all connected areas
-%RESCAN <areaname>    Request a rescan of a single connected area+%RESCAN <areatag>     Request a rescan of a single connected area 
 +%ECHOSTATS <areatag>  Request statistics (import/export details) of an area
 %ACTIVE               Reconnect (resume) all temporarily disconnected areas %ACTIVE               Reconnect (resume) all temporarily disconnected areas
 %PASSIVE              Temporarily disconnect (pause) all connected areas %PASSIVE              Temporarily disconnect (pause) all connected areas
 +%NOTIFY <ON | OFF>    Turn periodic Notification Messages ON or OFF
 %FROM <address>       Remote/proxy Area Management, must be the first command %FROM <address>       Remote/proxy Area Management, must be the first command
 %+ALL                 Connect all available areas %+ALL                 Connect all available areas
Line 1059: Line 1068:
  
 ==== Changes in Version 3 ==== ==== Changes in Version 3 ====
- 
-For a detailed list of changes and code differences introduced in v3.0, see [[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/src/sbbs3/sbbsecho.c?revision=3.0&view=markup|This page in CVS]]. 
  
 The most major changes introduced in v3.0 are: The most major changes introduced in v3.0 are:

Trace: