Board: [fsxNet] fsxNet Network Discussion Subject: Proposed changes on Hub 3 From: deon(21:2/116) Date: Sat May 16, 2026 09:02 Howdy, I'm thinking of making some changes on Hub 3, mainly to reduce the unnessary work that clrghouz does - but also because I'm planning on playing with something new (for shits and giggles, time permitting). At the moment, when clrghouz doesnt see a node for a period of time, the node transitions through various states: * Its marked HOLD after 21 days * Its marked DOWN after 35 days * Its DE-LISTED after 45 days This assessment is done on Sunday's at 1am (GMT+10), so you could potentially add 6 more days, if they go idle on a Sunday after 1am. DE-LISTED is semi-destructive in that mail exports are stopped, uncollected mail is removed and the address is marked as deleted. Its normally pretty easy to come back - by re-activating the address, resubscribing, and an areafix to resend uncollected mail. The other states are non-destructive. Emails/Netmails are sent to the offending node at each stage, as well as a post here - so that in case its a surprise, the sysop can look/fix it or reach out. The only thing they need to do is poll in and collect mail before DE-LIST, and their status is reset. What I'm proposing to change this: * Its marked HOLD after 14 days - mail will continue to be exported, netmails will still be queued * Its marked DOWN after 21 days - echomail exports will stop, and netmail will bounce (so the sender knows they are not here) * Its marked DOWN after 45 days - outstanding mail is removed, and the address is deleted - I may also look into bouncing any queued netmails, so the sender knows they never got it. I've noticed that when sysops go AWOL, they normally dont come back if they have been away after 21 days, and with my proposed changes, this means they would have received two emails (and queued netmails) letting them know. Any thoughts on these proposed changes? ....δεσ∩ --- SBBSecho 3.37-Linux * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116) .