Board: [fsxNet] fsxNet Network Discussion Subject: Re: Proposed changes on Hub 3 From: Jafo(21:3/241) Date: Sat May 16, 2026 06:55 de> de> I'm thinking of making some changes on Hub 3, mainly to reduce the de> unnessary work that clrghouz does - but also because I'm planning on de> playing with something new (for shits and giggles, time permitting). de> de> At the moment, when clrghouz doesnt see a node for a period of time, the de> node transitions through various states: de> de> * Its marked HOLD after 21 days de> * Its marked DOWN after 35 days de> * Its DE-LISTED after 45 days de> de> This assessment is done on Sunday's at 1am (GMT+10), so you could de> potentially add 6 more days, if they go idle on a Sunday after 1am. de> de> DE-LISTED is semi-destructive in that mail exports are stopped, de> uncollected mail is removed and the address is marked as deleted. Its de> normally pretty easy to come back - by re-activating the address, de> resubscribing, and an areafix to resend uncollected mail. The other de> states are non-destructive. de> de> Emails/Netmails are sent to the offending node at each stage, as well as de> a post here - so that in case its a surprise, the sysop can look/fix it de> or reach out. The only thing they need to do is poll in and collect mail de> before DE-LIST, and their status is reset. de> de> What I'm proposing to change this: de> de> * Its marked HOLD after 14 days - mail will continue to be exported, de> netmails will still be queued de> * Its marked DOWN after 21 days - echomail exports will stop, and de> netmail will bounce (so the sender knows they are not here) de> * Its marked DOWN after 45 days - outstanding mail is removed, and the de> address is deleted - I may also look into bouncing any queued netmails, de> so the sender knows they never got it. All good with me ... ---- Tomcat BBS - Telnet: tomcatbbs.ddns.net:2323 fsxNet: 21:3/241 * FidoNet 1:136/382 Titusville, FL. --- Mystic BBS v1.12 A48 (Windows/32) * Origin: Tombat BBS (21:3/241) .