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 [2018/03/31 20:32] – Numerous updates to track the latest echocfg menus/options and BinkIT v2 integration digital manutil:sbbsecho [2018/09/08 15:25] – [EchoCfg] Updated the BinkP Settings docs (some copy/paste from the EchoCfg online help) digital man
Line 46: 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 515: Line 515:
  
 <file> <file>
-╔═════════════════════════════╗ +╔[■][?]═══════════════════════════════╗ 
-║   1:218/700 BinkP Settings  ║ +║       1:218/700 BinkP Settings      ║ 
-╠═════════════════════════════╣ +╠═════════════════════════════════════╣ 
-║ │Host                       ║ +║ │Host                               ║ 
-║ │Port                 24554 ║ +║ │Port                 24554         ║ 
-║ │Poll                 Yes   ║ +║ │Poll                 Yes           ║ 
-║ │Allow Plain Auth     No    ║ +║ │Authentication       CRAM-MD5 Only ║ 
-║ │Allow Plain Text     No    ║ +║ │Encryption           Supported     ║ 
-║ │Source Address             ║ +║ │Source Address                     ║ 
-╚═════════════════════════════╝+╚═════════════════════════════════════╝ 
 </file> </file>
 +
 +**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 //Plain-Password// and //CRAM-MD5//.
 +                                                                        
 +**Encryption** determines whether unencrypted data transfers will be supported or required when communicating with this linked node. With this setting set to ''Required'', only BinkD-style-encrypted BinkP sessions will be supported. //CRAM-MD5// authentication must be used when encrypting BinkP sessions.
 +                                                                        
 +**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 682: Line 695:
  
 == 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 ==

Trace: