Subj : Re: Binkd nondinnding to certain networks
To   : Torsten Bamberg
From : Joacim Melin
Date : Fri Dec 08 2017 08:08 am

 TB> Hallo Joacim!

 TB> 07.12.2017 21:41, Joacim Melin schrieb an Wilfred van Velzen:

 JM>> ^/fido/outbound/be9ed600.pkt
 JM>> ^/fido/outbound/be9f1e00.pkt
 JM>> ^/fido/outbound/bea52300.pkt
 JM>> ^/fido/outbound/59bea5c4.su0
 JM>> ^/fido/outbound/59bea5c4.su1
 JM>> ^/fido/outbound/59bea5c4.tu0
 JM>> ^/fido/outbound/59bea5c4.tu1
 JM>> ^/fido/outbound/59bea5c4.tu2
 JM>> ^/fido/outbound/59bea5c4.tu3
 JM>> ^/fido/outbound/59bea5c4.we0
 JM>> ^/fido/outbound/59bea5c4.th0
 JM>> ^/fido/outbound/2994e600.pkt
 JM>> ^/fido/outbound/29974200.pkt

 JM>> Which, I guess, is all the outgoing packets that hasn't been sent yet.
 JM>> I wonder if the ^ symbol in front of the path is what mess things up.
 JM>> I have no idea where that symbol comes from though.

 TB> Comes for/with BSO Style outbound. The ^character means, the file
 TB> will be deleted after filetransfer.

Thanks Torsten for that info. Had no idea.

--- NiKom v2.3.1
 * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)

.