Subj : Binkd nondinnding to certain networks
To   : Joacim Melin
From : Torsten Bamberg
Date : Thu Dec 07 2017 11:10 pm

Hallo Joacim!

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.

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

Bye/2 Torsten

.... MAILBOX: up 3d 3h 23m load: 28 proc, 131 threads (tbupv1.0)
--- GoldED+ 1.1.5-17
 * Origin: DatenBahn BBS Hamburg (2:240/5832)

.