Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
config:sbbsecho.ini [2021/07/07 19:10] digital man [Node Sections] Enable ini syntax highlighting |
config:sbbsecho.ini [2022/03/14 19:54] Andre [See Also] tags |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ''[[dir:ctrl]]/sbbsecho.ini'' is the default configuration filename used by [[util:SBBSecho]] version 3, [[module:BinkIT]] version 2, and [[module:TickIT]] version 1. While other configuration filenames may be passed-to and used-by SBBSecho, the format must be the same [[ini_files|.ini format]] and only one configuration file may be used per invocation of SBBSecho. | ''[[dir:ctrl]]/sbbsecho.ini'' is the default configuration filename used by [[util:SBBSecho]] version 3, [[module:BinkIT]] version 2, and [[module:TickIT]] version 1. While other configuration filenames may be passed-to and used-by SBBSecho, the format must be the same [[ini_files|.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 [[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/sbbsecho.ini|here]]. | + | The current default ''sbbsecho.ini'' file can be downloaded from [[howto:Git]] [[https://gitlab.synchro.net/main/sbbs/-/raw/master/ctrl/sbbsecho.ini?inline=false|here]]. |
| Line 196: | Line 196: | ||
| 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. | 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. | ||
| + | |||
| + | ==== Robot Sections ==== | ||
| + | |||
| + | Each NetMail Robot Section has a prefix of "''robot:''" with the name of the robot (e.g. ''filefix'') following the prefix. Received NetMail addressed to the name of a robot will be stored in your ''[[dir:data]]/mail'' base and expected to be acted-up by a robot that is trigged when its associated semaphore file is touched. [[module:TickFix]] is an example of a NetMail robot. | ||
| + | |||
| + | ^ Key ^ Description ^ | ||
| + | | ''SemFile'' | The path and filename of a semaphore file to be //touched// by SBBSecho when a NetMail is received for the robot | | ||
| + | | ''attr'' | NetMail attribute flags to set (usually specific in hexadecimal notation with a ''0x'' prefix), ''0x20'' (In-Transit) is recommended | | ||
| ==== Domain Sections ==== | ==== Domain Sections ==== | ||
| Line 226: | Line 234: | ||
| * [[:module:BinkIT]] FidoNet/BINKP mailer | * [[:module:BinkIT]] FidoNet/BINKP mailer | ||
| - | {{tag>fidonet}} | + | |
| + | {{tag>configuration echomail fidonet ftn netmail email messaging ini}} | ||
