Hi,
I have a points (4:902/26.X) with Status = Hold, also that points
receive tic files from file area, however i see in the log that binkit
tries to make a call to it

If i assume that the state is hold, should it avoid calling them?


May 16 00:08:00 scarlet synchronet: evnt BINKOUT JSBinkP/1.123 callout
to 4:902/26.3@fidonet started
May 16 00:08:00 scarlet synchronet: evnt BINKOUT connecting to 4:902/26.3@fidonet at undefined
May 16 00:08:00 scarlet synchronet: evnt BINKOUT Connecting to 4:902/26.3@fidonet at p3.f26.n902.z4.example.com:24554
May 16 00:08:10 scarlet synchronet: evnt BINKOUT Connection to p3.f26.n902.z4.example.com:24554 failed (Error: Unable to connect).
May 16 00:08:10 scarlet synchronet: evnt BINKOUT Unlocking /sbbs/fido/outbound/0386001a.pnt/00000003.bsy.
May 16 00:08:10 scarlet synchronet: evnt BINKOUT Locking /sbbs/fido/outbound/0386001a.pnt/00000004.bsy
May 16 00:08:10 scarlet synchronet: evnt BINKOUT Lock successful.
May 16 00:08:10 scarlet synchronet: evnt BINKOUT Attempting callout for 4:902/26.4@fidonet, file: /sbbs/fido/outbound/0386001a.pnt/00000004.flo
May 16 00:08:10 scarlet synchronet: evnt BINKOUT JSBinkP/1.123 callout
to 4:902/26.4@fidonet started
May 16 00:08:10 scarlet synchronet: evnt BINKOUT connecting to 4:902/26.4@fidonet at undefined
May 16 00:08:10 scarlet synchronet: evnt BINKOUT Connecting to 4:902/26.4@fidonet at p4.f26.n902.z4.example.com:24554
May 16 00:08:20 scarlet synchronet: evnt BINKOUT Connection to p4.f26.n902.z4.example.com:24554 failed (Error: Unable to connect).

Re: binkit.js try to call my point
By: Ragnarok to DOVE-Net.Synchronet_Discussion on Sat May 16 2020 01:02 am

Hi,
I have a points (4:902/26.X) with Status = Hold, also that points
receive tic files from file area, however i see in the log that binkit
tries to make a call to it

If i assume that the state is hold, should it avoid calling them?

tickit doesn't use the hold status of a linked node, it *always* writes to .flo files (not .hlo, which would be for "hold"). So BinkIT will try to deliver it.

digital man

Synchronet "Real Fact" #14:
SBBSecho was originally written by Allen Christiansen (King Drafus) in 1994. Norco, CA WX: 64.2øF, 70.0% humidity, 1 mph S wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: binkit.js try to call my point
By: Ragnarok to DOVE-Net.Synchronet_Discussion on Sat May 16 2020 01:02:34


Ragnarok> I have a points (4:902/26.X) with Status = Hold, also that points
Ragnarok> receive tic files from file area, however i see in the log that
Ragnarok> binkit tries to make a call to it

Ragnarok> If i assume that the state is hold, should it avoid calling them?

you're processing those TICs with tickit, right?

tickit doesn't yet know about a system's hold, crash, direct, immediate, or normal status so it generates flo files with normal status... binkit (and any other BSO mailer) will see the hlo/hut files and not attempt to send them but it/they will make the call and attempt to send flo/out, clo/cut, dlo/dut, and ilo/iut files... yes, even with hlo/hut files for the same system... this is the correct behavoir...

what needs to be done is tickit should look at a system's status that is used for echomail/netmail and use that status, too, like sbbsecho does... it is one of the things on my TODO list but it hasn't risen to the top yet :/ if someone else wants to make the code adjustment, that would be great :)


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR

El 16/5/20 a las 03:02, Digital Man escribió:

Re: binkit.js try to call my point
By: Ragnarok to DOVE-Net.Synchronet_Discussion on Sat May 16 2020 01:02 am

Hi,
I have a points (4:902/26.X) with Status = Hold, also that points
receive tic files from file area, however i see in the log that binkit tries to make a call to it

If i assume that the state is hold, should it avoid calling them?

tickit doesn't use the hold status of a linked node, it *always* writes to .flo files (not .hlo, which would be for "hold"). So BinkIT will try to deliver it.

okaa thanks!