Subj : Hub 3 upcoming changes
To   : All
From : deon
Date : Sat May 11 2024 09:58 pm

Howdy,

I'm about to push an update to clrghouz that hopefully (and ideally) nobody will really notice :)

I've been working on a couple of things:
* More backend performance improvements, mostly visible from the web ui.
* Feeding nodelist segments upstream - so when you update your BBS name, hostname/port, etc that it automatically updates the nodelist
* Automating "havent seen you for a long time" messages, which will transition your node to HOLD and then DOWN and ultimately an email to you to let you know that your node has been de-listed if you dont collect mail (and it seems you are offline).
* Automatically determining address roles based on the AKA (ie: ZC/RC/NC/Hub/Node/Point)
* More fine tuning of automatic routing - to fix a shortfall that I identified.

These have all kinda been related and as I started to plan one thing, I realised that I needed to re-jig/re-do some of the automatic logic that is used.

In the past when I've pushed through an update that, its affected the from address that packets were sent to nodes (its worked out automatically) - or the to address (mostly for other hubs which run multiple addresses). Its mostly visible by the from address for any test messages in FSX_TST.

So if you notice that packets in your inbound are being marked bad - or mail is being tossed to a bad area, please let me know and I'll dig into it quickly. My initial testing appears that I havent broken it, but sometimes that still escapes me :(

I'll post another message when I pushed out the update (in the next 24hrs or so), so if you dont see it, take a look at your logs and see if things are being tossed bad.


....лоеп
--- SBBSecho 3.20-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

.