sbbsecho.ini file

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 sbbsecho.ini file.

The [BinkP] section is used for BinkP-specific global settings (i.e. used exclusively by BinkIT version 2):

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.

Example:

[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.

NOTE: The wildcard 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:

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. fidonet, fsxnet) following the prefix.

Note:
FTN domains used to be configured in the now-deprecated ctrl/ftn_domains.ini file.

Each Additional EchoList Section has a prefix of “echolist:” with the path/filename of the EchoList following the prefix.

• config index
• SBBSecho
• echocfg