| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision |
| config:sbbsecho.ini [2022/03/02 22:47] – [SBBSecho (FidoNet EchoMail Program) Configuration] Updated links from CVS->Git digital man | config:sbbsecho.ini [2022/03/02 22:55] – Document robots digital man |
|---|
| 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 ==== |
