• BinkIT/SBBSEcho issues - .cut files not sending

    From Massacre@VERT/SILICONU to All on Thursday, March 14, 2019 09:00:18
    I have an issue since switching to BinkIT. I was able to binkd without issues.

    When a netmail message is created, it creates a .cut file in the outbound folder and sits... When echomail is created, it creates a packet with the ??# extention like it should but just sits there.

    I then disable the BinkIT service then fire up a poll with binkd. IT then sends out the files without an issue.

    Is it a semaphore issue? Configuration issue?

    Thank you!

    ---
    þ Synchronet þ SiliconUnderground - siliconu.synchro.net
  • From Dmxrob@VERT/STLWEST to Massacre on Thursday, March 14, 2019 09:18:53
    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to All on Thu Mar 14 2019 11:00 am

    I have an issue since switching to BinkIT. I was able to binkd without issues.

    What does your timed event setup look like? I had a similar issue, turned out it was because in my timed event I didn't have it enabled properly.


    dmxrob þ BBSing from St. Louis, Missouri since 1988

    ---
    þ Synchronet þ Gateway to the West - St. Louis, Missouri - bbs.homelabber.net
  • From Dan Clough@VERT to Massacre on Thursday, March 14, 2019 12:26:00
    Massacre wrote to All <=-

    I have an issue since switching to BinkIT. I was able to binkd
    without issues.

    When a netmail message is created, it creates a .cut file in the
    outbound folder and sits... When echomail is created, it
    creates a packet with the ??# extention like it should but just
    sits there.

    I then disable the BinkIT service then fire up a poll with binkd.
    IT then sends out the files without an issue.

    Is it a semaphore issue? Configuration issue?

    Sounds like you don't have your BINKOUT timed event enabled.
    Should be listed there in the timed events, just change the
    Enabled choice from No to Yes (and don't change anything else).



    ... Nothing is so smiple that it can't get screwed up.
    === MultiMail/Linux v0.51
    --- SBBSecho 3.06-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Massacre@VERT/SILICONU to Dmxrob on Thursday, March 14, 2019 14:22:23
    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Dmxrob to Massacre on Thu Mar 14 2019 11:18 am

    Which timed events? The FIDOUT/FIDOIN ones? Like the lesr, etc. flags?

    ---
    þ Synchronet þ SiliconUnderground - siliconu.synchro.net
  • From Robert Stinnett@VERT to Massacre on Thursday, March 14, 2019 15:08:27
    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Dmxrob on Thu Mar 14 2019 04:22 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Dmxrob to Massacre on Thu Mar 14 2019 11:18 am

    Which timed events? The FIDOUT/FIDOIN ones? Like the lesr, etc. flags?

    You have to have a timed event setup for BINKIT for both outgoing and polling events. See this page for more details:

    http://wiki.synchro.net/module:binkit?s[]=binkit

    Rob
    --- SBBSecho 3.06-Linux
    * Origin: Gateway to the West BBS | St. Louis, Missouri (1:290/10)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Massacre@VERT/SILICONU to Dan Clough on Thursday, March 14, 2019 17:07:53
    Re: BinkIT/SBBSEcho issues -
    By: Dan Clough to Massacre on Thu Mar 14 2019 02:26 pm

    They are and have been enabled. I wonder if there is a switch or some kind of path, etc. that needs to change??

    ---
    þ Synchronet þ SiliconUnderground - siliconu.synchro.net
  • From Massacre@VERT/SILICONU to Robert Stinnett on Thursday, March 14, 2019 17:15:54
    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm

    I looked at the document again and went through the settings and the events were configured correctly.

    I originally used binkd and that works fine. Something feels like a config issue.

    ---
    þ Synchronet þ SiliconUnderground - siliconu.synchro.net
  • From Dan Clough@VERT to Massacre on Thursday, March 14, 2019 17:02:00
    Massacre wrote to Dan Clough <=-

    Re: BinkIT/SBBSEcho issues -
    By: Dan Clough to Massacre on Thu Mar 14 2019 02:26 pm

    They are and have been enabled. I wonder if there is a switch or
    some kind of path, etc. that needs to change??

    It would help if you would quote what you're replying to...

    I forgot to mention in my first reply, you also need the FIDOOUT
    and FIDOIN events enabled...



    ... A day without sunshine is like night.
    === MultiMail/Linux v0.51
    --- SBBSecho 3.06-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Massacre@VERT/SILICONU to Dan Clough on Thursday, March 14, 2019 20:30:47
    Re: BinkIT/SBBSEcho issues -
    By: Dan Clough to Massacre on Thu Mar 14 2019 07:02 pm

    Massacre wrote to Dan Clough <=-

    Re: BinkIT/SBBSEcho issues -
    By: Dan Clough to Massacre on Thu Mar 14 2019 02:26 pm

    They are and have been enabled. I wonder if there is a switch or
    some kind of path, etc. that needs to change??

    It would help if you would quote what you're replying to...

    I forgot to mention in my first reply, you also need the FIDOOUT
    and FIDOIN events enabled...

    Sorry. :) I removed the FIDOIN event, rebuilt it and now that works. I am going to do the same for the FIDOOUT event to see if that helps. They were previously enabled and I saw the sem files get created triggering the events.

    I hope it works. :)

    Thank you.

    ---
    þ Synchronet þ SiliconUnderground - siliconu.synchro.net
  • From Digital Man@VERT to Massacre on Thursday, March 14, 2019 22:03:31
    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Robert Stinnett on Thu Mar 14 2019 07:15 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm

    I looked at the document again and went through the settings and the events were configured correctly.

    I originally used binkd and that works fine. Something feels like a config issue.

    Are you reading the log output when binkit runs?

    digital man

    Synchronet "Real Fact" #81:
    Vertrauen has had the FidoNet node number 1:103/705 since 1992.
    Norco, CA WX: 54.1øF, 27.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Massacre@VERT/SILICONU to Digital Man on Friday, March 15, 2019 07:21:28
    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Digital Man to Massacre on Fri Mar 15 2019 12:03 am

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Robert Stinnett on Thu Mar 14 2019 07:15 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm

    I looked at the document again and went through the settings and the events were configured correctly.

    I originally used binkd and that works fine. Something feels like a config issue.

    Are you reading the log output when binkit runs?

    digital man

    Synchronet "Real Fact" #81:
    Vertrauen has had the FidoNet node number 1:103/705 since 1992.
    Norco, CA WX: 54.1øF, 27.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs

    I am seeing in the output that FIDOOUT semaphore is signaled then FIDOOUT even runs, then BINKOUT runs:

    3/14 08:00:29p Semaphore signaled for Timed Event: FIDOOUT
    3/14 08:00:29p Running native timed event: FIDOOUT
    3/14 08:00:29p FIDOOUT Executing external: C:\sbbs\exec\sbbsecho.exe -linf
    3/14 08:00:32p Timed event: FIDOOUT returned 0
    3/14 08:00:34p Semaphore signaled for Timed Event: BINKOUT
    3/14 08:00:34p Running timed event: BINKOUT

    Then BINKOUT is executed for outbound then callout:

    3/14 08:00:34p BINKOUT Executing external: ?binkit
    3/14 08:00:34p BINKOUT BinkIT/2.14 invoked with options:
    3/14 08:00:34p BINKOUT Running outbound
    3/14 08:00:34p BINKOUT Outbound roots: ["c:\\sbbs\\fido\\outbound"]
    3/14 08:00:34p BINKOUT Outbound dirs: ["c:\\sbbs\\fido\\outbound\\"]
    3/14 08:00:34p BINKOUT Running outbound dir c:\sbbs\fido\outbound\
    3/14 08:00:34p BINKOUT Locking c:\sbbs\fido\outbound\010a0200.bsy
    3/14 08:00:34p BINKOUT Lock successful.
    3/14 08:00:34p BINKOUT Attempting callout for 1:266/512@fidonet, file: c:\sbbs\fido\outbound\010a0200.cut
    3/14 08:00:34p BINKOUT JSBinkP/1.112 callout to 1:266/512@fidonet started
    3/14 08:00:34p BINKOUT connecting to 1:266/512@fidonet at cfbbs.no-ip.com
    3/14 08:00:34p BINKOUT Connecting to cfbbs.no-ip.com:24554
    3/14 08:00:34p BINKOUT Connection to cfbbs.no-ip.com:24554 successful
    3/14 08:00:34p BINKOUT Sending M_NUL command args: OPT CRYPT
    3/14 08:00:34p BINKOUT Sent M_NUL command
    3/14 08:00:34p BINKOUT Sending M_NUL command args: SYS SiliconUnderground
    3/14 08:00:34p BINKOUT Sent M_NUL command
    3/14 08:00:34p BINKOUT Sending M_NUL command args: ZYZ Jason Bock
    3/14 08:00:34p BINKOUT Sent M_NUL command
    3/14 08:00:34p BINKOUT Sending M_NUL command args: LOC Rochester, NY
    3/14 08:00:34p BINKOUT Sent M_NUL command
    3/14 08:00:34p BINKOUT Sending M_NUL command args: NDL 115200,TCP,BINKP
    3/14 08:00:34p BINKOUT Sent M_NUL command
    3/14 08:00:34p BINKOUT Sending M_NUL command args: TIME Thu Mar 14 2019 20:00:34 GMT-0400 (Eastern Daylight Time)
    3/14 08:00:34p BINKOUT Sent M_NUL command
    3/14 08:00:34p BINKOUT Sending M_NUL command args: VER BinkIT/2.14,JSBinkP/1.112,sbbs3.17b/Win32 binkp/1.1
    3/14 08:00:34p BINKOUT Sent M_NUL command
    3/14 08:00:34p BINKOUT Sending M_ADR command args: 1:267/310@fidonet
    3/14 08:00:34p BINKOUT Sent M_ADR command
    3/14 08:00:34p BINKOUT Got M_NUL command args: OPT MB CRAM-MD5-8065d8307e5dc331d9a72df407909da2
    3/14 08:00:34p BINKOUT Got M_NUL command args: SYS Christian Fellowship
    3/14 08:00:34p BINKOUT Got M_NUL command args: ZYZ Michael Luko
    3/14 08:00:34p BINKOUT Got M_NUL command args: LOC Mt. Ephraim, NJ
    3/14 08:00:34p BINKOUT Got M_NUL command args: NDL CM,INA:cfbbs.dtdns.net,IBN,ITN,IFT
    3/14 08:00:34p BINKOUT Got M_NUL command args: TIME 2019/03/14 19:58:52 -5:00
    3/14 08:00:34p BINKOUT Got M_NUL command args: VER Internet Rex 2.29 Win32 (binkp/1.1)
    3/14 08:00:34p BINKOUT Peer version: Internet Rex 2.29 Win32 (binkp/1.1)
    3/14 08:00:34p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.org 1:13/0.0@fidonet.org 1:13/3.0@fidonet.org 1:129/0.0@fidonet.org 1:266/0.0@fidonet.org 454:1/1.0@ilink.org
    3/14 08:00:34p BINKOUT Sending M_PWD command args: CRAM-MD5-e31540cd0eb26b162f18b8077b17a309
    3/14 08:00:34p BINKOUT Sent M_PWD command
    3/14 08:00:34p BINKOUT Got M_OK command args:
    3/14 08:00:34p BINKOUT Authentication successful:
    3/14 08:00:34p BINKOUT Unconfigured address 1:266/512@fidonet.
    3/14 08:00:34p BINKOUT Unconfigured address 1:13/0@fidonet.
    3/14 08:00:34p BINKOUT Unconfigured address 1:13/3@fidonet.
    3/14 08:00:34p BINKOUT Unconfigured address 1:129/0@fidonet.
    3/14 08:00:34p BINKOUT Unconfigured address 1:266/0@fidonet.
    3/14 08:00:34p BINKOUT Unconfigured address 454:1/1@ilink.or
    3/14 08:00:34p BINKOUT Sending M_EOB command args:
    3/14 08:00:34p BINKOUT Sent M_EOB command
    3/14 08:00:34p BINKOUT Got M_EOB command args:
    3/14 08:00:34p BINKOUT Unlocking c:\sbbs\fido\outbound\010a0200.bsy.
    3/14 08:00:34p BINKOUT No flow files to be processed.
    3/14 08:00:34p BINKOUT Done checking in c:\sbbs\fido\outbound\.
    3/14 08:00:34p Timed event: BINKOUT returned 0

    Once it is all done, BINKOUT returns 0 but the .cut file is still sitting in C:\SBBS\FIDO\OUTBOUND.

    I did see this:

    3/14 08:00:34p BINKOUT No flow files to be processed.
    3/14 08:00:34p BINKOUT Done checking in c:\sbbs\fido\outbound\.

    Is a flow file not telling BinkIt to send a packet out? I can disable the BINKP service in the Synchronet comtrol panel and run a binkdwin poll and it will send out the message(s) just fine.

    Inbound works great. It feels as if there is a configuration of some soret of semaphore ore flow file.

    Thank you,

    Jason

    ---
    þ Synchronet þ SiliconUnderground - siliconu.synchro.net
  • From Digital Man@VERT to Massacre on Friday, March 15, 2019 10:56:39
    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Digital Man on Fri Mar 15 2019 09:21 am

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Digital Man to Massacre on Fri Mar 15 2019 12:03 am

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Robert Stinnett on Thu Mar 14 2019 07:15 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm

    I looked at the document again and went through the settings and the events were configured correctly.

    I originally used binkd and that works fine. Something feels like a config issue.

    Are you reading the log output when binkit runs?

    digital man

    Synchronet "Real Fact" #81:
    Vertrauen has had the FidoNet node number 1:103/705 since 1992.
    Norco, CA WX: 54.1øF, 27.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs

    I am seeing in the output that FIDOOUT semaphore is signaled then FIDOOUT even runs, then BINKOUT runs:

    3/14 08:00:29p Semaphore signaled for Timed Event: FIDOOUT
    3/14 08:00:29p Running native timed event: FIDOOUT
    3/14 08:00:29p FIDOOUT Executing external: C:\sbbs\exec\sbbsecho.exe -linf
    3/14 08:00:32p Timed event: FIDOOUT returned 0
    3/14 08:00:34p Semaphore signaled for Timed Event: BINKOUT
    3/14 08:00:34p Running timed event: BINKOUT

    Then BINKOUT is executed for outbound then callout:

    3/14 08:00:34p BINKOUT Executing external: ?binkit
    3/14 08:00:34p BINKOUT BinkIT/2.14 invoked with options:
    3/14 08:00:34p BINKOUT Running outbound
    3/14 08:00:34p BINKOUT Outbound roots: ["c:\\sbbs\\fido\\outbound"]
    3/14 08:00:34p BINKOUT Outbound dirs: ["c:\\sbbs\\fido\\outbound\\"]
    3/14 08:00:34p BINKOUT Running outbound dir c:\sbbs\fido\outbound\
    3/14 08:00:34p BINKOUT Locking c:\sbbs\fido\outbound\010a0200.bsy
    3/14 08:00:34p BINKOUT Lock successful.
    3/14 08:00:34p BINKOUT Attempting callout for 1:266/512@fidonet, file: c:\sbbs\fido\outbound\010a0200.cut
    3/14 08:00:34p BINKOUT JSBinkP/1.112 callout to 1:266/512@fidonet
    Notice how this address -------------------------------^^^^^^^^^^^^^^^^^

    3/14 08:00:34p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.org
    Is different from this address ------------------------^^^^^^^^^^^^^^^^^^^^^^^

    FidoNet domains are supposed to be limited to 8 characters, so "fidonet" is a valid FTN domain while "fidonet.org" is not. And it doesn't match the system you're trying to connect to. The problem is on the uplink's side.

    digital man

    This Is Spinal Tap quote #8:
    Derek Smalls: Making a big thing out of it would have been a good idea.
    Norco, CA WX: 67.3øF, 24.0% humidity, 10 mph ENE wind, 0.00 inches rain/24hrs

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Massacre@VERT/SILICONU to Digital Man on Friday, March 15, 2019 20:41:36
    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Digital Man to Massacre on Fri Mar 15 2019 12:56 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Digital Man on Fri Mar 15 2019 09:21 am

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Digital Man to Massacre on Fri Mar 15 2019 12:03 am

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Robert Stinnett on Thu Mar 14 2019 07:15 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm

    I looked at the document again and went through the settings and the events were configured correctly.

    I originally used binkd and that works fine. Something feels like a config issue.

    Are you reading the log output when binkit runs?

    digital man

    Synchronet "Real Fact" #81:
    Vertrauen has had the FidoNet node number 1:103/705 since 1992.
    Norco, CA WX: 54.1øF, 27.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs

    I am seeing in the output that FIDOOUT semaphore is signaled then FIDOOUT even runs, then BINKOUT runs:

    3/14 08:00:29p Semaphore signaled for Timed Event: FIDOOUT
    3/14 08:00:29p Running native timed event: FIDOOUT
    3/14 08:00:29p FIDOOUT Executing external: C:\sbbs\exec\sbbsecho.exe -linf
    3/14 08:00:32p Timed event: FIDOOUT returned 0
    3/14 08:00:34p Semaphore signaled for Timed Event: BINKOUT
    3/14 08:00:34p Running timed event: BINKOUT

    Then BINKOUT is executed for outbound then callout:

    3/14 08:00:34p BINKOUT Executing external: ?binkit
    3/14 08:00:34p BINKOUT BinkIT/2.14 invoked with options:
    3/14 08:00:34p BINKOUT Running outbound
    3/14 08:00:34p BINKOUT Outbound roots: ["c:\\sbbs\\fido\\outbound"]
    3/14 08:00:34p BINKOUT Outbound dirs: ["c:\\sbbs\\fido\\outbound\\"]
    3/14 08:00:34p BINKOUT Running outbound dir c:\sbbs\fido\outbound\
    3/14 08:00:34p BINKOUT Locking c:\sbbs\fido\outbound\010a0200.bsy
    3/14 08:00:34p BINKOUT Lock successful.
    3/14 08:00:34p BINKOUT Attempting callout for 1:266/512@fidonet, file: c:\sbbs\fido\outbound\010a0200.cut
    3/14 08:00:34p BINKOUT JSBinkP/1.112 callout to 1:266/512@fidonet
    Notice how this address -------------------------------^^^^^^^^^^^^^^^^^

    3/14 08:00:34p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.org
    Is different from this address ------------------------^^^^^^^^^^^^^^^^^^^^^^^

    FidoNet domains are supposed to be limited to 8 characters, so "fidonet" is a valid FTN domain while "fidonet.org" is not. And it doesn't match the system you're trying to connect to. The problem is on the uplink's side.

    digital man

    This Is Spinal Tap quote #8:
    Derek Smalls: Making a big thing out of it would have been a good idea. Norco, CA WX: 67.3øF, 24.0% humidity, 10 mph ENE wind, 0.00 inches rain/24hrs

    Thank you for your response. Is there a work around for this?

    -Jason

    ---
    þ Synchronet þ SiliconUnderground - siliconu.synchro.net
  • From Digital Man@VERT to Massacre on Friday, March 15, 2019 18:07:01
    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Digital Man on Fri Mar 15 2019 10:41 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Digital Man to Massacre on Fri Mar 15 2019 12:56 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Digital Man on Fri Mar 15 2019 09:21 am

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Digital Man to Massacre on Fri Mar 15 2019 12:03 am

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Robert Stinnett on Thu Mar 14 2019 07:15 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm

    I looked at the document again and went through the settings and the events were configured correctly.

    I originally used binkd and that works fine. Something feels like a config issue.

    Are you reading the log output when binkit runs?

    digital man

    Synchronet "Real Fact" #81:
    Vertrauen has had the FidoNet node number 1:103/705 since 1992. Norco, CA WX: 54.1øF, 27.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs

    I am seeing in the output that FIDOOUT semaphore is signaled then FIDOOUT even runs, then BINKOUT runs:

    3/14 08:00:29p Semaphore signaled for Timed Event: FIDOOUT
    3/14 08:00:29p Running native timed event: FIDOOUT
    3/14 08:00:29p FIDOOUT Executing external: C:\sbbs\exec\sbbsecho.exe -linf
    3/14 08:00:32p Timed event: FIDOOUT returned 0
    3/14 08:00:34p Semaphore signaled for Timed Event: BINKOUT
    3/14 08:00:34p Running timed event: BINKOUT

    Then BINKOUT is executed for outbound then callout:

    3/14 08:00:34p BINKOUT Executing external: ?binkit
    3/14 08:00:34p BINKOUT BinkIT/2.14 invoked with options:
    3/14 08:00:34p BINKOUT Running outbound
    3/14 08:00:34p BINKOUT Outbound roots: ["c:\\sbbs\\fido\\outbound"]
    3/14 08:00:34p BINKOUT Outbound dirs: ["c:\\sbbs\\fido\\outbound\\"]
    3/14 08:00:34p BINKOUT Running outbound dir c:\sbbs\fido\outbound\
    3/14 08:00:34p BINKOUT Locking c:\sbbs\fido\outbound\010a0200.bsy
    3/14 08:00:34p BINKOUT Lock successful.
    3/14 08:00:34p BINKOUT Attempting callout for 1:266/512@fidonet, file: c:\sbbs\fido\outbound\010a0200.cut
    3/14 08:00:34p BINKOUT JSBinkP/1.112 callout to 1:266/512@fidonet
    Notice how this address -------------------------------^^^^^^^^^^^^^^^^^

    3/14 08:00:34p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.org
    Is different from this address ------------------------^^^^^^^^^^^^^^^^^^^^^^^

    FidoNet domains are supposed to be limited to 8 characters, so "fidonet" is a valid FTN domain while "fidonet.org" is not. And it doesn't match the system you're trying to connect to. The problem is on the uplink's side.

    Thank you for your response. Is there a work around for this?

    If you remove the "@fidonet" from your configuration (just 4D addressing) - that might do it.

    digital man

    This Is Spinal Tap quote #43:
    I feel my role in the band is ... kind of like lukewarm water.
    Norco, CA WX: 63.3øF, 21.0% humidity, 3 mph SE wind, 0.00 inches rain/24hrs

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Massacre@VERT/SILICONU to Digital Man on Friday, March 15, 2019 22:42:06
    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Digital Man to Massacre on Fri Mar 15 2019 08:07 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Digital Man on Fri Mar 15 2019 10:41 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Digital Man to Massacre on Fri Mar 15 2019 12:56 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Digital Man on Fri Mar 15 2019 09:21 am

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Digital Man to Massacre on Fri Mar 15 2019 12:03 am

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Robert Stinnett on Thu Mar 14 2019 07:15 pm

    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Robert Stinnett to Massacre on Thu Mar 14 2019 05:08 pm

    I looked at the document again and went through the settings and the events were configured correctly.

    I originally used binkd and that works fine. Something feels like a config issue.

    Are you reading the log output when binkit runs?

    digital man

    Synchronet "Real Fact" #81:
    Vertrauen has had the FidoNet node number 1:103/705 since 1992. Norco, CA WX: 54.1øF, 27.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs

    I am seeing in the output that FIDOOUT semaphore is signaled then FIDOOUT even runs, then BINKOUT runs:

    3/14 08:00:29p Semaphore signaled for Timed Event: FIDOOUT
    3/14 08:00:29p Running native timed event: FIDOOUT
    3/14 08:00:29p FIDOOUT Executing external: C:\sbbs\exec\sbbsecho.exe -linf
    3/14 08:00:32p Timed event: FIDOOUT returned 0
    3/14 08:00:34p Semaphore signaled for Timed Event: BINKOUT
    3/14 08:00:34p Running timed event: BINKOUT

    Then BINKOUT is executed for outbound then callout:

    3/14 08:00:34p BINKOUT Executing external: ?binkit
    3/14 08:00:34p BINKOUT BinkIT/2.14 invoked with options:
    3/14 08:00:34p BINKOUT Running outbound
    3/14 08:00:34p BINKOUT Outbound roots: ["c:\\sbbs\\fido\\outbound"]
    3/14 08:00:34p BINKOUT Outbound dirs: ["c:\\sbbs\\fido\\outbound\\"]
    3/14 08:00:34p BINKOUT Running outbound dir c:\sbbs\fido\outbound\
    3/14 08:00:34p BINKOUT Locking c:\sbbs\fido\outbound\010a0200.bsy
    3/14 08:00:34p BINKOUT Lock successful.
    3/14 08:00:34p BINKOUT Attempting callout for 1:266/512@fidonet, file: c:\sbbs\fido\outbound\010a0200.cut
    3/14 08:00:34p BINKOUT JSBinkP/1.112 callout to 1:266/512@fidonet
    Notice how this address -------------------------------^^^^^^^^^^^^^^^^^

    3/14 08:00:34p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.org
    Is different from this address ------------------------^^^^^^^^^^^^^^^^^^^^^^^

    FidoNet domains are supposed to be limited to 8 characters, so "fidonet" is a valid FTN domain while "fidonet.org" is not. And it doesn't match the system you're trying to connect to. The problem is on the uplink's side.

    Thank you for your response. Is there a work around for this?

    If you remove the "@fidonet" from your configuration (just 4D addressing) - that might do it.

    digital man

    This Is Spinal Tap quote #43:
    I feel my role in the band is ... kind of like lukewarm water.
    Norco, CA WX: 63.3øF, 21.0% humidity, 3 mph SE wind, 0.00 inches rain/24hrs

    I just tested with the binkd and found in the configuration the following:

    domain fidonet c:\\sbbs\\fido\\outbound 1
    domain fido alias-for fidonet
    domain fidonet.org alias-for fidonet

    I removed the bottom 2 lines, manually polled and it would not send the mail out. I added them back in, polled again and it sent the packet. The domain thing you mentioned is right on target.

    Is there a way to add the 'alias-for' in the binkit system?

    You also mentioned removing the @fidonet domain from my configuration. I removed the domain from the config and it didn't work. Is there a specific way I need to do it?

    Thank you,

    -Jason

    ---
    þ Synchronet þ SiliconUnderground - siliconu.synchro.net
  • From Tony Langdon@VERT to Digital Man on Saturday, March 16, 2019 15:48:00
    On 03-15-19 20:07, Digital Man wrote to Massacre <=-

    3/14 08:00:34p BINKOUT JSBinkP/1.112 callout to 1:266/512@fidonet
    Notice how this address -------------------------------^^^^^^^^^^^^^^^^^

    3/14 08:00:34p BINKOUT Got M_ADR command args: 1:266/512.0@fidonet.org
    Is different from this address ------------------------^^^^^^^^^^^^^^^^^^^^^^^

    FidoNet domains are supposed to be limited to 8 characters, so "fidonet" is a valid FTN domain while "fidonet.org" is not. And it doesn't match the system you're trying to connect to. The problem is on the uplink's side.

    Thank you for your response. Is there a work around for this?

    If you remove the "@fidonet" from your configuration (just 4D
    addressing) - that might do it.

    That explains why binkd would work where BinkIT doesn't. Binkd has alias support for domains, where you can specify an alias to work around incorrect configuration, and in the config file I obtained, fidonet.org is configured as an alias to fidonet, just for this situation.

    But I agree, the uplink should fix their configuration, it is broken.

    Be interesting to see if going 4D does work.


    ... I'm working on my master's thesis on Amish road rage.
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From mark lewis@VERT to Massacre on Saturday, March 16, 2019 02:56:34
    On 2019 Mar 15 22:41:36, you wrote to Digital Man:

    FidoNet domains are supposed to be limited to 8 characters, so
    "fidonet" is a valid FTN domain while "fidonet.org" is not. And it
    doesn't match the system you're trying to connect to. The problem is on
    the uplink's side.

    Thank you for your response. Is there a work around for this?

    no, not really... that link needs to FixTheirShite<tm> instead of everyone else
    having to work around their flawed configuration ;)

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Baked potatoes - Better with steak than barbecue.
    ---
    * Origin: (1:3634/12.73)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Massacre@VERT/SILICONU to mark lewis on Saturday, March 16, 2019 07:20:25
    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: mark lewis to Massacre on Sat Mar 16 2019 04:56 am

    On 2019 Mar 15 22:41:36, you wrote to Digital Man:

    FidoNet domains are supposed to be limited to 8 characters, so
    "fidonet" is a valid FTN domain while "fidonet.org" is not. And it
    doesn't match the system you're trying to connect to. The problem is on
    the uplink's side.

    Thank you for your response. Is there a work around for this?

    no, not really... that link needs to FixTheirShite<tm> instead of everyone else
    having to work around their flawed configuration ;)

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Baked potatoes - Better with steak than barbecue.
    Very true.

    ---
    þ Synchronet þ SiliconUnderground - siliconu.synchro.net
  • From Digital Man@VERT to Massacre on Saturday, March 16, 2019 13:29:51
    Re: BinkIT/SBBSEcho issues - .cut files not sending
    By: Massacre to Digital Man on Sat Mar 16 2019 12:42 am

    If you remove the "@fidonet" from your configuration (just 4D addressing) - that might do it.

    Is there a way to add the 'alias-for' in the binkit system?

    No, at least not currently.

    You also mentioned removing the @fidonet domain from my configuration. I removed the domain from the config and it didn't work. Is there a specific way I need to do it?

    Um... not that I can think of. Just remove all occurences of "@<domain>" in sbbsecho.ini. <shrug>

    digital man

    Synchronet/BBS Terminology Definition #35:
    IBM = International Business Machines (Corporation)
    Norco, CA WX: 76.8øF, 20.0% humidity, 7 mph ESE wind, 0.00 inches rain/24hrs

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net