Hey Folks,

This is mainly for Hub 3 nodes...

For the last couple of weeks I've been re-writing my BINKP implementation. My original BINKP was a port from qico (I think), and I've never been happy with it. It really was a hack, difficult to debug and only implemented some BINKP features. It also often didnt always cleanly shutdown a connection.

I've re-written it from scratch, and also implemented some missing features (like compression, CRC) as well as optimised the queries that it uses to build outgoing mail and the code overall. Much happier with this implementation, if anything it should make it easier for me to debug, uses less memory and is marginally faster.

You may notice some extra OPT compression options, and while I know there arent other mailers that can use these new compression options, other clrghouz implementations will.

I'm going to roll it over the next couple of days, firstly it'll handle outgoing polls, and eventually it'll also handle incoming polls. I'll progressively move folks over (using firewall rules) to the new implemenation, and when I'm confident I've addressed all the bugs, it'll become the default.

If you notice anything odd, please let me know - with some details and some debug logging if you can, it'll certainly help me find the issue and fix it.

Hope folks are well :)


...ëîåï
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Updates to BINKP on Clrghouz (Hub 3)
By: deon to All on Wed Oct 01 2025 08:29 pm

Hey Folks,

This is mainly for Hub 3 nodes...

I'm going to roll it over the next couple of days, firstly it'll handle outgoing polls, and eventually it'll also handle incoming polls. I'll progressively move folks over (using firewall rules) to the new implemenation, and when I'm confident I've addressed all the bugs, it'll become the default.

Well some things went as planned, and some didnt.

Over the weekend I've been debugging my new binkp implementation and cleared out a few anomolies that cropped up with different binkp implementations that everybody uses.

I didnt have just discover that clrghouz wasnt bundling packets with the correct address when polling outbound. While you would have been sent your own mail, you might have found that your tosser rejected the packets with invalid password and/or wrong addresses, and the messages in the packet would have been for an fsxnet (or an othernet if you get other nets from me)

I've just triggered clrghouz to resend all mail sent over the weekend - so hopefully your dupe detection is working - for those mails that that were processed correctly, the resend of mails should be detected as a dupe and discarded.

For mail that wasnt processed correctly, it should be processed correctly this time (with the correct address and packet password, and correct mail for that address).

I've temporarily disabled outbound polling while I fix this issue and I'll re-enable it when its ready.

(Inbound polling is still using the old binkp implementation.)

Hope this makes sense :)

Yell out if something doesnt appear right...


...ëîåï
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)