This is an old revision of the document!
Table of Contents
ctrl/sbbsecho.ini is the default configuration filename used by SBBSecho version 3, BinkIT version 2, and TickIT version 1. While other configuration filenames may be passed-to and used-by SBBSecho, the format must be the same .ini format and only one configuration file may be used per invocation of SBBSecho.
The current default
sbbsecho.ini file can be downloaded from CVS here.
You can edit the
sbbsecho.ini file by hand using any text editor or, preferably, using the Synchronet EchoCfg utility.
When editing the
sbbsecho.ini file by hand, it is recommended to first make a backup copy of the file.
All of the supported .ini sections and keys are documented here.
Most of the SBBSecho configuration settings are defined in the Root Section of the
| || ||Directory where SBBSecho will look for non-secured inbound files|
| || ||Directory where SBBSecho will look for secured inbound files|
| || ||Directory where SBBSecho will place outbound files|
| || ||File where SBBSecho will load FTN-attached message areas from|
| || ||File where SBBSecho will write the names/tags of unlinked areas for which it has received echomail|
| || ||Log filename|
| || ||Time-stamp format used in the log file|
| || ||Directory where SBBSecho will create temporary/in-process files|
| ||Semaphore file SBBSecho will touch when creating outbound files|
| || ||Minimum severity of log messages written to the log file|
| || ||Strip line-feed (ASCII 10) characters from exported messages|
| || ||Mailer is BSO/FLO style (rather than ArcMail/Attach style)|
| || || Time-out duration when attempting to lock
| || ||Number of attempts to lock a BSO for a node|
| || ||Delay between BSO lock attempts|
| || ||Packets with passwords must match the corresponding configured/linked node password|
| || ||File creation mode (for *nix only)|
| || ||Number of Area File backups to maintain (for Area Manager modifications)|
| || ||Number of configuration file backups to maintain (for Area Manager or EchoCfg modifications)|
| || ||Outgoing bundles (archives), maximum file size|
| || || Outgoing packets (
| || ||Check PATH kludge lines for circular messages|
| || ||Only import EchoMail from linked nodes|
| || ||Send telegrams to BBS users when EchoMail is received for them|
| || || Convert any tear lines (
| || ||Truncate rather than delete outbound bundles after being sent|
| || || Assume that node numbers are not duplicated across zones (set to
| || ||Zone numbers less than this will be considered blind (all part of the same node number “namespace”)|
| || ||Allow echoes to be AreaFix-added from Additional EchoLists only (not Area File)|
| || ||Automatically add new Sub-boards within linked Message Groups to the Area File|
| || ||Age limit (in days) of EchoMail messages that may be imported (0 = no limit)|
| || ||Messages that are filtered (e.g. due to age) will be relayed to downlinks|
| || ||BBS user name or alias to notify (via email) of AreaFix activities and errors|
| || ||Path/filename of EchoMail Statistics (“EchoStats”) database|
| ||Name of the user account you wish to receive inbound NetMail messages that have been addressed to an unrecognized user name or alias|
| || ||Comma-separated list of names by which the sysop (user #1) may receive NetMail messages|
| || ||Use local AKAs to determine source zone information when missing|
| || ||Treat all NetMail as though it is destined for one of your systems's FTN addresses|
| || ||Export NetMail messages even when their 'Sent' attribute flag is set|
| || ||Do not delete exported NetMail messages even when their 'Kill' attribute flag is set|
| || ||Import NetMail messages even when their 'Received' attribute flag is set|
| || ||Import NetMail messages even when their 'Local' attribute flag is set|
| || ||Discard (not import or export) NetMail messages without any body|
| || ||Delete all NetMail messages/files after they have been sent or imported|
| || ||Delete packets after they've been imported|
| || ||Age limit (in days) of NetMail messages that may be imported (0 = no limit)|
[BinkP] section is used for BinkP-specific global settings (i.e. used exclusively by BinkIT version 2):
|Capabilities||<blank>|| If set, changes the text in the
|Sysop||<blank>|| If set, over-rides the sysop name (
|PlainAuthOnly|| || If set to
Archivers are used to extract packets from received bundles and create bundles of outgoing packets. Archivers are configured in the Archive Sections of the
sbbsecho.ini file (separately from any archivers configured in Synchronet/SCFG).
Each Archive Section has a prefix of “
archive:” and the name of the archive type (e.g. “ZIP”) following the prefix.
| || ||Signature offset (in bytes)|
| ||Signature (in hexadecimal)|
| ||Archive creation (pack) command-line (with Synchronet command-line specifiers)|
| ||Archive extraction (unpack) command-line (with Synchronet command-line specifiers)|
[archive:ZIP] SigOffset = 0 Sig = 504B Pack = %@zip -jD %f %s Unpack = %@unzip -ojC %f -d %s
Each Linked-Node Section has a prefix of “
node:” with the FTN address of the node following the prefix.
| || ||Type of packets to generate for this node (2+, 2e, 2.2, or 2)|
| ||Password used in password-protected packets|
| ||Password used for BinkP (BinkIT) sessions with this linked node|
| ||Password required for AreaFix/AreaMgr operations|
| || Password required for TIC files (used by
| ||Name of this linked-node's operator (e.g. real name or alias), auto-set when receiving Area Manager requests|
| ||Personal comment about this node (any text useful to you)|
| || Optional filebox for incoming files (correlates with BinkD's
| || Optional filebox for outgoing files (correlates with BinkD's
| ||List of keys (comma-separated) which enable AreaFix access to one or more Additional EchoLists|
| || ||Notify via NetMail of node's current AreaFix settings whenever SBBSecho is run with the '`-g`' option|
| || ||Temporarily disable the packing and sending of EchoMail for this node|
| || ||Connect to this node directly (whenever possible) when sending mail to this node|
| || ||Default mode for sending mail to this node: Normal, Hold (wait for pickup) or Crash (immediate)|
| || ||Name of a configured archive type or “None”|
| ||FTN address (e.g. of a hub) to route all EchoMail and NetMail destined for this node's address|
| ||List of Message Groups (comma-separated) for which this linked node is your system's uplink (hub)|
| ||Host name or IP address of this link's BinkP mailer (optional)|
| || ||TCP port number of this link's BinkP mailer|
| || || Poll this link (e.g. as part of the
| || ||Allow plain-password (in addition to CRAM-MD5) when authenticating with this linked node|
| || ||Only support plain-password authentication when connecting (outbound) with this linked node|
| || ||Allow plain-text (unencrypted) communication with this linked node|
| ||Use an alternative FTN address as the source address when communicating with this node via BinkP|
ALL may replace one or more fields of the configured node's FTN address. Configured node's with wildcard addresses cannot have an Inbox our Outbox set.
[node:1:218/700] Comment = My Hub AreafixPwd = PacketPwd = PacketType = 2+ Archive = ZIP Inbox = Outbox = Passive = false Direct = false Notify = false Keys = Status = Normal [node:1:ALL] Comment = Everyone in FidoNet Zone 1 AreafixPwd = PacketPwd = PacketType = 2+ Archive = ZIP Inbox = Outbox = Passive = false Direct = false Notify = false Keys = Status = Normal Route = 1:218/700
The evolution of the BinkIT/BinkP session-security related settings has lead to a potentially confusing array of 3 interrelated Boolean options with only 4 valid combinations of values. Here is a table to explain these valid combinations and their impact on the security and interoperability of BinkP sessions with the linked-node:
|Minimum|| || || ||Passwords and message packets will always be sent as clear-text (maximum interoperability)|
|Normal|| || || ||Passwords may be obscured via CRAM-MD5 authentication|
|Enhanced|| || || ||Passwords must be obscured via CRAM-MD5 authentication|
|Maximum|| || || ||Passwords and message packets must be obscured or encrypted 1)|
In general, the lower the security setting, the higher the level of insured compatibility with other BinkP mailers. When debugging authentication (password) issues, it might be a good idea to use the minimum level of security and increase the security level incrementally once you have the minimum level of secured-session working with the linked-node.
Also note: authentication is performed by the answering BinkP node (server/service), so while one security level may work okay for outgoing connections to a linked-node, its possible that there could be problems (incompatibilities) with incoming connections from that same linked-node. It's a good idea to test both incoming and outgoing connections with a linked-node before increasing the BinkP session security level.
Each FTN Domain Section has a prefix of “
domain:” with the name of the domain (e.g.
fsxnet) following the prefix.
| ||List of zone numbers (comma-separated) associated with this domain|
| || Optional suffix used for DNS-based IP address look-ups of nodes in this domain (e.g.
| ||Optional nodelist path/filename to use for hostname/IP address look-ups for this domain|
| ||Optional alternate outbound root directory to use for this domain|
FTN domains used to be configured in the now-deprecated
Each Additional EchoList Section has a prefix of “
echolist:” with the path/filename of the EchoList following the prefix.
| ||List of keys (comma-separated) which enable Linked Node AreaFix access to this EchoList|
| ||The FTN address of hub which provides the areas in this EchoList|
| || ||Forward AreaFix requests to hub of this EchoList?|
| ||AreaFix password to include in AreaFix requests forwarded to the hub of this EchoList|