FYI, I am migrating binkd traffic over from the broken POS binkit that comes with synchronet over to binkd proper. Hope to complete that this morning and then switch which software listens to 24554.

Just curious, what are you finding broken with binkit?

Binkit ignores a 'BinkPoll=false' setting when the node also has an outbox configured.

Binkit will ramdomly hang the system (maxing a CPU at 100%) when it cannot connect to a node, rather than time the connection out like it should. I
have reported this one twice before, and been told it is fixed, only to
then have it happen again.

sbbsecho puts outbound mail in the outbox if you have one set for a node.

Binkit was reporting connections with one node as successful when they
actually were not.

The binkit maintainer is absent from bbsing.

Since 'real' binkd is FOSS and works with sbbs I think it is better to use it vs. an imitation product, even though it means keeping an extra config file updated. I was already using it for my fido hubs + Sean, for quicker
outbound mail turnaround, so switching wasn't a big deal.

Mike

* SLMR 2.1a * ASCII stupid question - get a stupid ANSI
--- SBBSecho 3.28-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (618:250/1)

Mike Powell wrote to DAN CLOUGH <=-

FYI, I am migrating binkd traffic over from the broken POS binkit that comes with synchronet over to binkd proper. Hope to complete that this morning and then switch which software listens to 24554.

Just curious, what are you finding broken with binkit?

Binkit ignores a 'BinkPoll=false' setting when the node also has an
outbox configured.

Binkit will ramdomly hang the system (maxing a CPU at 100%) when it
cannot connect to a node, rather than time the connection out like it should. I have reported this one twice before, and been told it is
fixed, only to then have it happen again.

sbbsecho puts outbound mail in the outbox if you have one set for a
node.

Binkit was reporting connections with one node as successful when they actually were not.

The binkit maintainer is absent from bbsing.

Since 'real' binkd is FOSS and works with sbbs I think it is better to
use it vs. an imitation product, even though it means keeping an extra config file updated. I was already using it for my fido hubs + Sean,
for quicker outbound mail turnaround, so switching wasn't a big deal.

Okay cool, thanks for the info. I have thought a few times about
switching over too, just for the experience, but haven't done it.

What about things like Areafix and netmail...? Oh, those probably
aren't affected because they're actually done by SBBSecho (tosser)
rather than the mailer, right?



... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.29-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (618:250/24)

Okay cool, thanks for the info. I have thought a few times about
switching over too, just for the experience, but haven't done it.

What about things like Areafix and netmail...? Oh, those probably
aren't affected because they're actually done by SBBSecho (tosser)
rather than the mailer, right?

That should be the case, yes, so long as you remember to set the node up in both your sbbsecho.ini (with the binkit specific stuff turned off) and your binkd.cfg file.

I also wondered about tickit but, seeing as synchronet runs a separate event for that one, I also think it shouldn't cause an issue.

There are other systems that use other mailers besides binkit... binkd,
irex, etc., so I think it should all be fine. Here I was already also
running ifcico -- only my test system currently connects that way but I
have had no issues getting areafix and netmail exchanged between the two systems.

As you are a 250 net node, if you happen to notice that you are no longer getting the nodelist from me, that means I am wrong so do let me know. :D

Mike


* SLMR 2.1a * How do you know if you run out of invisible ink?
--- SBBSecho 3.28-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (618:250/1)

Mike Powell wrote to GAMGEE <=-

Okay cool, thanks for the info. I have thought a few times about
switching over too, just for the experience, but haven't done it.

What about things like Areafix and netmail...? Oh, those probably
aren't affected because they're actually done by SBBSecho (tosser)
rather than the mailer, right?

That should be the case, yes, so long as you remember to set the node
up in both your sbbsecho.ini (with the binkit specific stuff turned
off) and your binkd.cfg file.

Okay.

I also wondered about tickit but, seeing as synchronet runs a separate event for that one, I also think it shouldn't cause an issue.

Yup, that would make sense.

There are other systems that use other mailers besides binkit... binkd, irex, etc., so I think it should all be fine. Here I was already also running ifcico -- only my test system currently connects that way but I have had no issues getting areafix and netmail exchanged between the
two systems.

As you are a 250 net node, if you happen to notice that you are no
longer getting the nodelist from me, that means I am wrong so do let me know. :D

The latest nodelist I've received here is dated August 1, 2025.




... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.29-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (618:250/24)