On 22 Apr 2021 at 06:09a, Olrik pondered and said...
filetossing - only 1 file base is created (FSXNet Image} with a single file in it, but all other files are ending up in the badfile directory. Logs show the following for each incoming TIC file: 'bad destination 21:2/154'. My node is 21:2/144 so I don't know if this is the problem or how it can be fixed.
can you tell me if you still have this issue?
I checked at 2/100 and it seems as if all is correct.
I hatched another copy of the nodelist and your system picked this up at this time... here's the NET 2 HUB logs
+ 2021.04.24 21:58:10 BINKP > Connect on slot 1/10 (52.36.77.149)
+ 2021.04.24 21:58:10 BINKP 1-HostName ec2-52-36-77-149.us-west-2.compute.amazonaws.com
+ 2021.04.24 21:58:10 BINKP 1-System Outremer BBS
+ 2021.04.24 21:58:10 BINKP 1-SysOp Olrik
+ 2021.04.24 21:58:10 BINKP 1-Mailer Mystic/1.12A43 binkp/1.0
+ 2021.04.24 21:58:11 BINKP 1-Queued 3 files for 21:2/144@fsxnet
+ 2021.04.24 21:58:11 BINKP 1-Sending: 0000ffd4.sa7 (790 bytes)
+ 2021.04.24 21:58:11 BINKP 1-Remote Queue: 0 files 0 bytes
+ 2021.04.24 21:58:12 BINKP 1-Sending: FSXNET.tic (3,501 bytes)
+ 2021.04.24 21:58:12 BINKP 1-Sending: FSXNET.Z20 (11,583 bytes)
+ 2021.04.24 21:58:12 BINKP 1-Session ended (3 sent, 0 rcvd, 0 skip)
can you tell me were these files imported fine?
--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)