Subj : Binkit Issues
To : All
From : Dumas Walker
Date : Fri Aug 29 2025 01:33 pm
(1) if a node is set to BinkpPoll = false *but* the system has an outbox
defined *and* sbbsecho or binkit has moved the packets for that node into said
outbox, binkit will poll the node anyway.
(a) I don't think it should be moving outbound mail packets into the outbox...
I think that is normally only for "non-mail" files
(b) regardless, if a node is set to BinkpPoll = false, binkit shouldn't be
trying to connect to it.
I use BinkpPoll = false when I have nodes that can call in fine but where the
mailers don't answer incoming calls correctly, for example.
(2) Don't know what is causing this one... will include output... but I have a
node where my system tries sending a bunch of mail but where you can see only
two packets are reported sent, and no errors except "We got an M_EOB, but there
are still 1 files pending M_GOT" (which I thought could be ignored) are
displayed:
FYI, all of the packets listed exist on this end. I am going to try this node
with binkd and see what happens.
(3) binkit is "hanging" sometimes when it hits a node it cannot connect to,
maxing out a whole CPU until I force-stop the sbbs instance -- this is related
to problem #1 and would probably be fixed if #1 was working right. That said,
I remember asking for a fix a while back to have binkit time when it takes too
long to connect, but that is not working in this case.
