AmendHub

--- GUIDE Sat Mar 11 20:52:56 2023 +++ GUIDE Sun Mar 26 21:51:53 2023 @@ -17,13 +17,14 @@ Features - Integrated ANSI-capable local console - Local log window with smart screen blanking - Multiple threaded message boards +- FTN (FidoNet) EchoMail and NetMail support with Binkp hub synching - Multi-user interactive chat - Private messaging/mail - File uploading and downloading with ZMODEM support - Secure user password storage with SHA256 - View/menu templates with variable expansion - Configurable main menu key shortcuts -- Telnet brute-force IP banning by sending UDP packets to a firewall host +- Telnet brute-force IP banning by sending messages to a firewall host Setup ================================================================== @@ -137,6 +138,7 @@ still accessible by any key in the All Keys field, but The default mapping is: # Action:Menu Key:All Keys:Label + BOARD_LIST_FTN_AREAS:A:Aa:List FTN Areas BOARD_SHOW_FIRST:B:Bb:Message Board BOARD_SHOW_1::1:Message Board 1 BOARD_SHOW_2::2:Message Board 2 @@ -160,6 +162,42 @@ The default mapping is: WHOS_ONLINE:W:Ww:Who's Online SHOW_MENU:?:?:List Menu Options SYSOP_MENU::!:Sysop Menu + +FTN (FidoNet) Support +================================================================== +Subtext supports FTN EchoMail (distributed message boards) and NetMail +(relayed mail to a user at another node) by way of a Binkp hub. +Directly-delivered "CrashMail" is not supported. Subtext has a built-in +scanner/tosser with limited support for PKZIP archives of FTN packets. + +To get started, configure the FTN Hub Binkp hostname, port, and password +settings. The network name, hub node address (e.g., "21:3/100"), local node +address, and packet passwords must also be set. This is enough to enable +NetMail, so users can send mail to a user@XX:X/XXX and have it delivered +through the hub. Likewise, any incoming NetMail for valid usernames are +delivered, or bounced to the Sysop. + +To enable EchoMail areas, create local boards in the Sysop menu and set the +"FTN Area Name" field to match each desired area name exactly. Note that +once a board has its FTN area name set, it cannot be removed later due to +FTN boards using a different database structure than local, threaded boards. + +Once Binkp polling is enabled, Subtext will attempt to login to the Binkp hub +at the configured interval and retrieve any packets sent from the hub, saving +them to the "binkp-inbox" directory. After fetching any outstanding files, +any packets in the "binkp-outbox" directory are sent to the hub. + +Packets (or PKZIP archives of packets) in the inbox are tossed and NetMail is +delivered. Any EchoMail packets for areas that match the FTN Area Name set +in a local board are imported. + +To minimize latency, the Binkp poller will not start while there are any +users logged in. This means that NetMail messages sent locally will not be +sent out right away unless a Sysop manually triggers Binkp polling from the +Sysop menu. This comes into play when communicating back and forth with an +FTN AreaFix bot to configure which area messages should be delivered through +the Binkp hub. + Trusted Host ==================================================================