TZUTC: -0800
MSGID: 55282.sync@1:103/705 2d7b92a1
REPLY: 2:280/464 69145c05
PID: Synchronet 3.21a-Linux master/d39e01091 Nov 03 2025 GCC 12.2.0
TID: SBBSecho 3.31-Linux master/d39e01091 Nov 03 2025 GCC 12.2.0
COLS: 80
BBSID: VERT
CHRS: CP437 2
FORMAT: flowed
NOTE: FSEditor.js v1.105
  Re: Re: Strange issues
  By: Wilfred van Velzen to Digital Man on Wed Nov 12 2025 11:05 am

 > Hi Digital,
 >
 > On 2025-11-11 13:58:33, you wrote to me:
 >
 >  >> 09:29:58.978  Error reading packet header in file:
 >  >> /home/fido/inbound/f4o5881q.pkt, renamed with extension: '.error'
 >  >>
 >  >> # xxd f4o5881q.pkt.error
 >  >> 0000000: 4269 6e6b 4954 2f32 2e34 3120 6172 6773  BinkIT/2.41 args
 >  >> 0000010: 3a20 0a                                  : .
 >  >>
 >  >>
 >  >> Firstly the .pkt file that isn't a .pkt file?
 >
 >  DM> Looks like that is the contents of a lock/.bsy file created by BinkIt.
 >  DM> These
 >  DM> files should *not* sent to the remote host, so that is very weird.
 >
 > Indeed weird, but what is the solution? ;-)

I'm not sure. Have you asked the node to be sure their Synchronet install is
up-to-date (especially their exec and load directories)?

 >  >> Secondly the 'recv' from the remote before the connection is complete,
 >  >> so my binkd flags it as 'failed'...
 >
 >  DM> I don't follow you there.
 >
 > A "normal" incoming session, like for instance one with your system ends
 > like this (as seen in the binkd log):
 >
 > ...
 > - 12 Nov 09:31:12 [22442] VER BinkIT/2.41,JSBinkP/4,sbbs3.21a/Linux
 > binkp/1.1
 > + 12 Nov 09:31:12 [22442] addr: 1:103/705@fidonet
 > ...
 > - 12 Nov 09:31:12 [22442] receiving 691445ca.pkt (1007 byte(s), off 0)
 > + 12 Nov 09:31:12 [22442] rcvd: 691445ca.pkt (1007, 1007.00 CPS,
 > 1:103/705@fidonet)
 > + 12 Nov 09:31:12 [22442] done (from 1:103/705@fidonet, OK, S/R: 0/1 (0/1007
 > bytes))
 >   12 Nov 09:31:13 [22442] session closed, quitting...
 >
 > On this system I see this:
 >
 > ...
 > - 11 Nov 09:29:58 [23984] VER BinkIT/2.41,JSBinkP/4,sbbs3.20d/FreeBSD
 > binkp/1.1 ...
 > - 11 Nov 09:29:58 [23984] receiving f4o5881q.pkt (19 byte(s), off 0)
 > + 11 Nov 09:29:58 [23984] rcvd: f4o5881q.pkt (19, 19.00 CPS,
 > 39:***/***@AmigaNet)
 > ? 11 Nov 09:29:58 [23984] recv: connection closed by foreign host
 > + 11 Nov 09:29:58 [23984] done (from 39:***/***@AmigaNet, failed, S/R: 0/1
 > (0/19 bytes))
 >   11 Nov 09:29:58 [23984] session closed, quitting...
 >
 > I don't know the exact meaning of the recv line, but it seems like a forced
 > connection close by the other end. And not a regular protocol "finish". So
 > it's flagged as "failed", and my binkd tries this node again after a
 > configured retry time...

Maybe they have an old or modified version of BinkIT or one of the dependent
files (e.g. binkp.js). If you're not seeing the same behavior with my system 
(which is using the latest and greatest), it might just be a bug specific to
that system or version of binkit (and it's dependencies).
-- 
                                            digital man (rob)

This Is Spinal Tap quote #38:
Artie Fufkin:  I'm not asking, I'm telling with this. Kick my ass.
Norco, CA WX: 63.3øF, 72.0% humidity, 1 mph NE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.31-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187
SEEN-BY: 129/14 153/7715 154/110 218/0 1 215 601 610 700 840 860 880
SEEN-BY: 226/30 227/114 229/110 112 206 317 400 426 428 470 700 705
SEEN-BY: 266/512 280/464 291/111 301/1 320/219 322/757 342/200 396/45
SEEN-BY: 460/58 633/280 712/848 902/26 5075/35
PATH: 103/705 218/700 229/426