Hello Rj!   
      
   26 Sep 16 12:27, you wrote to all:   
      
    RC> Has anyone seen an error like that come up before? I'm now running   
    RC> v1.0.6.8 for my 1:120/544 hub node and that error is coming up for   
    RC> when just one of my downlinks attempts to connect:   
      
    RC> + 26-Sep-2016 00:14:54 mbcico[24206] Binkp: send   
    RC> "/opt/mbse/var/bso/outbound/0000ffa0.tu3" as "0000ffa0.tu3"   
    RC> + 26-Sep-2016 00:14:54 mbcico[24206] Binkp: size 210469 bytes, dated   
    RC> Sep 20   
    RC> 23:34:29, comp No   
    RC> ? 26-Sep-2016 00:14:54 mbcico[24206] tty_write: hanged_up flag   
    RC> + 26-Sep-2016 00:14:54 mbcico[24206] Binkp: transmitter failure   
    RC> + 26-Sep-2016 00:14:54 mbcico[24206] Binkp: session finished, rc=108   
    RC> + 26-Sep-2016 00:14:56 mbcico[24206] Incoming call failed (rc=108)   
    RC> + 26-Sep-2016 00:14:56 mbcico[24206] Terminated with error 108   
      
      
    RC> The '0000ffa0.tu3' file itself does not appear to have any permissions   
    RC> issues. That '108' error appears to be a "File Transfer Error"...   
      
    RC> The other system uses this (which I'm not familiar with...):   
    RC> BinkIT/1.39,JSBinkP/1.54/Win32 binkp/1.1   
      
   I've never seen this error connecting to BinkD (for OS/2 or Windows), Argus,    
   Radius, Taurus, and even Fred Riccio's experimental Binkp mailer.  I suspect    
   that the issue lies with BinkIT, but will need to test further to confirm    
   that.   
      
    RC> Also;  depending on the intent of that error message, it may actually   
    RC> be mis-spelled...   
      
   I'll know more after checking out the debug log of a session with a BinkIT    
   node.   
      
   Andrew   
      
   --- GoldED+/LNX 1.1.5-b20160322   
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)