Anyone know how to correct this:

(normal polling info shorten ...)
Scanning 21:1/100
Queued 0 files....
Polling BINKP node 21:1/100..
Connecting...
Connected....
RB Socket read result 113
Connection lost
Authorization failed
Getting this when polling a node, any node. Connects fine then says that.

--- Mystic BBS v1.12 A39 2018/02/28 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 03/21/18, David said the following...

Anyone know how to correct this:

(normal polling info shorten ...)
Scanning 21:1/100
Queued 0 files....
Polling BINKP node 21:1/100..
Connecting...
Connected....
RB Socket read result 113
Connection lost
Authorization failed
Getting this when polling a node, any node. Connects fine then says that.

--- Mystic BBS v1.12 A39 2018/02/28 (Windows/32)

Several Sysops, including myself, have reported similar errors. I reverted to the first A39 PreAlpha and that took care of it for me.. Someone else, sorry can't remember who, reported that they replaced the fidopoll executable with
a prior version and that worked for him.

--- Mystic BBS v1.12 A39 2018/02/28 (Linux/64)
* Origin: CombatNet Support BBS | bbs.combatnet.us (21:1/138.2)

On 03/21/18, Fat Rastus said the following...

Someone else, sorry can't remember who, reported that they replaced the fidopoll executable with a prior version and that worked for him.

That was me and you are correct. Since fidopoll doesn't need to write to databases and just dumps ftn packets into your inbound directory, a minor version mismatch isn't a big deal.

--- Mystic BBS v1.12 A39 2018/03/17 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

Anyone know how to correct this:
Connected....
RB Socket read result 113
Connection lost

The version and operating system might be helpful here, as error messages
come from the OS and vary between OS.

I can only assume you're using a Unix-based system based on the error, which would mean 113 is "No route to host". Can you "ping <hostname>" and see if the responses from the host come back successfully?

There could be a packet filter or firewall in the way, possibly? This really seems like a network related error not anything Mystic would have any involvement in. That error comes from the operating system itself (as
opposed to be generated by Mystic).

--- Mystic BBS v1.12 A39 2018/03/26 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Hello g00r00,

Connected....
RB Socket read result 113
Connection lost

I am getting the same/similar response when polling using FIDOPOLL. It started when I upgraded to A39.

The version and operating system might be helpful here, as error messages come from the OS and vary between OS.
I can only assume you're using a Unix-based system based on the error, which would mean 113 is "No route to host". Can you "ping <hostname>" and see if the responses from the host come back successfully?

It looks here to only be happening with the Linux versions of Mystic. I can poll ok using the Win32 version of Mystic (Fidopoll). I get different result numbers when attempting a IPv4 connection versus a IPv6 connection using the Linux64 version of Fidopoll. When attempting a connection using Fidopoll I get:

Mar 26 20:58:21 FIDOPOLL Version 1.12 A39 2018/03/12 Mar 26 20:58:21 Scanning 21:1/100
Mar 26 20:58:21 Queued 0 files (0 bytes) to 21:1/100 Mar 26 20:58:21 Polling BINKP node 21:1/100 by IPV4 Mar 26 20:58:21 Connecting to agency.bbs.nz:24556 Mar 26 20:58:22 Connected
Mar 26 20:58:22 WB Socket Write loop 115 Mar 26 20:58:22 WB Socket Write result
115 Mar 26 20:58:22 S: NUL SYS The Ouijaboard II Mar 26 20:58:22 WB Socket Write loop 115 Mar 26 20:58:22 WB Socket Write result 115 Mar 26 20:58:22 S: NUL ZYZ Jeff Smith Mar 26 20:58:22 WB Socket Write loop 115 Mar 26 20:58:22 WB Socket Write result 115 Mar 26 20:58:22 S: NUL VER Mystic/1.12A39 binkp/1.0 Mar
26 20:58:22 WB Socket Write loop 115 Mar 26 20:58:22 WB Socket Write result 115 Mar 26 20:58:22 S: ADR 1:282/1032@fidonet 21:1/128@fsxnet Mar 26 20:58:22 Connection lost
Mar 26 20:58:22 Authorization failed

Mar 26 20:04:42 FIDOPOLL Version 1.12 A39 2018/03/12 Mar 26 20:04:42 Scanning 21:1/100
Mar 26 20:04:42 Queued 0 files (0 bytes) to 21:1/100 Mar 26 20:04:42 Polling BINKP node 21:1/100 by IPV6 Mar 26 20:04:42 Connecting to agency.bbs.nz:24556 Mar 26 20:04:43 Connected
Mar 26 20:04:43 RB Socket read loop 107 Mar 26 20:04:43 RB Socket read result 107 Mar 26 20:04:43 RB Socket read loop 107 Mar 26 20:04:43 RB Socket read result 107 Mar 26 20:04:43 Connection lost
Mar 26 20:04:43 Authorization failed

This connection issue happens regardless of who I poll. I haven't made any OS related changes except to upgrade Mystic. I will try to revert to an earlier of
Mystic and see if it makes a difference.

I also did the same poll test using the Pi3 version of Mystic and get the same "RB Socket read result 107" response.

As a test I did the same poll using the same OS (Ubuntu 17.10 64b) with BBBS and it polled fine.

I installed the current release of A39 on a fresh install of CentOS on a spare 64b PC and upon executing FIDOPOLL I get the same response from FIDOPOLL.

Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

Connected....
RB Socket read result 113
Connection lost

I am getting the same/similar response when polling using FIDOPOLL. It started when I upgraded to A39.

WB Socket Write loop 115 Mar 26 20:58:22 WB Socket Write result 115 Mar
26 20:58:22 S: NUL ZYZ Jeff Smith Mar 26 20:58:22 WB Socket Write loop
115 Mar 26 20:58:22 WB Socket Write result 115 Mar 26 20:58:22 S: NUL
VER Mystic/1.12A39 binkp/1.0 Mar 26 20:58:22 WB Socket Write loop 115

Hmmm They are both errors reported by the operating system. Mystic is just logging the results after calling an OS function... But it does sound like something I should test.

I'll have to set up my BBS on the Linux side and do some testing maybe this weekend to see what is going on. I haven't done any BINKP testing on Linux for quite a while actually.

Thanks for letting me know.

--- Mystic BBS v1.12 A39 2018/03/26 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Several Sysops, including myself, have reported similar errors. I

This was the first I heard of it. :)

Does it happen on every connection every time?

Can you guys look to see what your "IPV4/IPV6" settings are for the sites you are connecting to? Or are these connections to nodes resolved from the nodelist?

I am planning to test this weekend in Linux so I just want to make sure that
I am accurately testing the situation in which this happens.

--- Mystic BBS v1.12 A39 2018/03/26 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Hello g00r00,

On 03/28/18, g00r00 said the following...

Does it happen on every connection every time?

So far it happens here on every outbound poll using FIDOPOLL.

Can you guys look to see what your "IPV4/IPV6" settings are for the
sites you are connecting to? Or are these connections to nodes resolved from the nodelist?

Here the connection issue is using the node specification in Mystic as well
as nodelisted node specifications. I have tried making both Ipv4 as well as IPv6 connections and get a similar response although the result number
changes.

I for example have polled Avon at 21:1/100 which is configured as a node specification in Mystic. And I have polled nodes that are not in Mystic as
a node specification and in either case I get the same connection issue.


Jeff.

--- Mystic BBS v1.12 A39 2018/03/26 (Windows/64)
* Origin: The Ouijaboard V (21:1/128.5)

On 03/28/18, g00r00 said the following...

Several Sysops, including myself, have reported similar errors. I

The message you quoted was a reply to another user who had a similar error, I am getting error 115. The first release of 112a39 works, I'm using it now,
but the last two have not.

Can you guys look to see what your "IPV4/IPV6" settings are for the
sites you are connecting to? Or are these connections to nodes resolved from the nodelist?

It's an entry in Networking/Echomail Nodes. IPv4

Log Entry:

Mar 29 01:04:11 FIDOPOLL Version 1.12 A39 2018/03/26
Mar 29 01:04:11 Scanning 1:227/201
Mar 29 01:04:11 Queued 0 files (0 bytes) to 1:227/201
Mar 29 01:04:11 Polling BINKP node 1:227/201 by IPV4
Mar 29 01:04:11 Connecting to bbs.ewbbs.net
Mar 29 01:04:11 Connected via IPV4
Mar 29 01:04:11 WB Socket Write loop 115
Mar 29 01:04:11 WB Socket Write result 115
Mar 29 01:04:11 S: NUL SYS CombatNet Support BBS
Mar 29 01:04:11 WB Socket Write loop 115
Mar 29 01:04:11 WB Socket Write result 115
Mar 29 01:04:11 S: NUL ZYZ Fat Rastus
Mar 29 01:04:11 WB Socket Write loop 115
Mar 29 01:04:11 WB Socket Write result 115
Mar 29 01:04:11 S: NUL VER Mystic/1.12A39 binkp/1.0
Mar 29 01:04:11 WB Socket Write loop 115
Mar 29 01:04:11 WB Socket Write result 115
Mar 29 01:04:11 S: ADR 411:411/101@combatnt 1:227/201.2@fidonet 46:1/107.2@agoranet 21:1/138.2@fsxnet 80:774/40.2@retronet
Mar 29 01:04:11 Connection lost
Mar 29 01:04:11 Authorization failed

The Hub (binkd) Logged:

+ 29 Mar 01:03:11 [2992] incoming session with 104.236.205.106
- 29 Mar 01:03:11 [2992] SYS CombatNet Support BBS
- 29 Mar 01:03:11 [2992] ZYZ Fat Rastus
- 29 Mar 01:03:11 [2992] VER Mystic/1.12A39 binkp/1.0
+ 29 Mar 01:03:11 [2992] addr: 411:411/101@combatnt
+ 29 Mar 01:03:11 [2992] addr: 1:227/201.2@fidonet
+ 29 Mar 01:03:11 [2992] addr: 46:1/107.2@agoranet
+ 29 Mar 01:03:11 [2992] addr: 21:1/138.2@fsxnet
+ 29 Mar 01:03:11 [2992] addr: 80:774/40.2@retronet
- 29 Mar 01:03:11 [2992] hiding aka 110:217/1@linuxnet
- 29 Mar 01:03:11 [2992] hiding aka 510:319/5@justaxnet
- 29 Mar 01:03:11 [2992] hiding aka 777:777/2@xnet
- 29 Mar 01:03:11 [2992] hiding aka 57:57/11@gatornet
- 29 Mar 01:03:11 [2992] hiding aka 9:91/14@survnet
? 29 Mar 01:03:11 [2992] recv: connection closed by foreign host
+ 29 Mar 01:03:11 [2992] done (from 411:411/101@combatnt, failed, S/R: 0/0
(0/0 bytes))

(huh.. just noticed one of my clocks is off by a minute)

--- Mystic BBS v1.12 A39 2018/02/28 (Linux/64)
* Origin: CombatNet Support BBS | bbs.combatnet.us (21:1/138.2)

On 03/28/18, Jeffs pondered and said...

I for example have polled Avon at 21:1/100 which is configured as a node specification in Mystic. And I have polled nodes that are not in Mystic
as a node specification and in either case I get the same connection issue.

Here's what I see

[snip]

+ 2018.03.29 20:12:08 BINKP > Connect on slot 1/25 (65.103.12.162)
+ 2018.03.29 20:12:08 BINKP 1-HostName Unknown
+ 2018.03.29 20:12:08 BINKP 1-Country United States of America (US)
+ 2018.03.29 20:12:08 BINKP 1-C: NUL SYS The Ouijaboard II
+ 2018.03.29 20:12:08 BINKP 1-System The Ouijaboard II
+ 2018.03.29 20:12:08 BINKP 1-S: NUL OPT CRAM-MD5-b094a7f110625aba4cc8bb93bef12a23
+ 2018.03.29 20:12:08 BINKP 1-C: NUL ZYZ Jeff Smith
+ 2018.03.29 20:12:08 BINKP 1-SysOp Jeff Smith
+ 2018.03.29 20:12:08 BINKP 1-S: NUL SYS fsxHUB [fsxNet WHQ]
+ 2018.03.29 20:12:08 BINKP 1-S: NUL ZYZ Paul Hayton
+ 2018.03.29 20:12:08 BINKP 1-S: NUL VER Mystic/1.12A39 binkp/1.0
+ 2018.03.29 20:12:08 BINKP 1-S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
+ 2018.03.29 20:12:08 BINKP 1-C: NUL VER Mystic/1.12A39 binkp/1.0
+ 2018.03.29 20:12:08 BINKP 1-Mailer Mystic/1.12A39 binkp/1.0
+ 2018.03.29 20:12:08 BINKP 1-C: ADR 1:282/1032@fidonet 21:1/128@fsxnet
+ 2018.03.29 20:12:08 BINKP 1-C: ADR 1:282/1032@fidonet 21:1/128@fsxnet
+ 2018.03.29 20:12:08 BINKP 1-Connection lost
+ 2018.03.29 20:12:08 BINKP 1-Client shutting down


[snip]

and an earlier one..

[snip]

+ 2018.03.29 19:41:55 BINKP > Connect on slot 1/25 (65.103.12.162)
+ 2018.03.29 19:41:55 BINKP 1-HostName Unknown
+ 2018.03.29 19:41:55 BINKP 1-Country United States of America (US)
+ 2018.03.29 19:41:55 BINKP 1-S: NUL OPT CRAM-MD5-ef0d4e99da5b2895345f093d7ee24a71
+ 2018.03.29 19:41:55 BINKP 1-C: NUL SYS The Ouijaboard II
+ 2018.03.29 19:41:55 BINKP 1-System The Ouijaboard II
+ 2018.03.29 19:41:55 BINKP 1-S: NUL SYS fsxHUB [fsxNet WHQ]
+ 2018.03.29 19:41:55 BINKP 1-S: NUL ZYZ Paul Hayton
+ 2018.03.29 19:41:55 BINKP 1-S: NUL VER Mystic/1.12A39 binkp/1.0
+ 2018.03.29 19:41:55 BINKP 1-S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
+ 2018.03.29 19:41:55 BINKP 1-C: NUL ZYZ Jeff Smith
+ 2018.03.29 19:41:55 BINKP 1-SysOp Jeff Smith
+ 2018.03.29 19:41:55 BINKP 1-C: NUL VER Mystic/1.12A39 binkp/1.0
+ 2018.03.29 19:41:55 BINKP 1-Mailer Mystic/1.12A39 binkp/1.0
+ 2018.03.29 19:41:55 BINKP 1-C: ADR 1:282/1032@fidonet 21:1/128@fsxnet
+ 2018.03.29 19:41:55 BINKP 1-C: ADR 1:282/1032@fidonet 21:1/128@fsxnet
+ 2018.03.29 19:41:55 BINKP 1-Connection lost
+ 2018.03.29 19:41:55 BINKP 1-Client shutting down

[snip]

compare this to another system... I note your end is sending the ADR line twice, I wonder why?

+ 2018.03.29 19:40:19 BINKP > Connect on slot 1/25 (155.4.23.116)
+ 2018.03.29 19:40:19 BINKP 1-HostName h-23-116.A230.priv.bahnhof.se
+ 2018.03.29 19:40:19 BINKP 1-Country Sweden (SE)
+ 2018.03.29 19:40:19 BINKP 1-S: NUL OPT CRAM-MD5-0f692f0a0976dbe2c1b83b71fa48304b
+ 2018.03.29 19:40:19 BINKP 1-C: NUL SYS Circle of Life Unl.
+ 2018.03.29 19:40:19 BINKP 1-System Circle of Life Unl.
+ 2018.03.29 19:40:19 BINKP 1-S: NUL SYS fsxHUB [fsxNet WHQ]
+ 2018.03.29 19:40:19 BINKP 1-S: NUL ZYZ Paul Hayton
+ 2018.03.29 19:40:19 BINKP 1-S: NUL VER Mystic/1.12A39 binkp/1.0
+ 2018.03.29 19:40:19 BINKP 1-S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
+ 2018.03.29 19:40:19 BINKP 1-C: NUL ZYZ Scuttle
+ 2018.03.29 19:40:19 BINKP 1-SysOp Scuttle
+ 2018.03.29 19:40:19 BINKP 1-C: NUL VER Mystic/1.12A35 binkp/1.0
+ 2018.03.29 19:40:19 BINKP 1-Mailer Mystic/1.12A35 binkp/1.0
+ 2018.03.29 19:40:19 BINKP 1-C: ADR 21:1/168@fsxnet
+ 2018.03.29 19:40:20 BINKP 1-C: PWD
+ 2018.03.29 19:40:20 BINKP 1-Authenticating 21:1/168@fsxnet by CRAM-MD5
+ 2018.03.29 19:40:20 BINKP 1-S: OK secure
+ 2018.03.29 19:40:20 BINKP 1-Queued 0 files for 21:1/168@fsxnet
+ 2018.03.29 19:40:20 BINKP 1-S: EOB
+ 2018.03.29 19:40:20 BINKP 1-C: EOB
+ 2018.03.29 19:40:20 BINKP 1-Session ended (0 sent, 0 rcvd, 0 skip)
+ 2018.03.29 19:40:20 BINKP 1-Client shutting down

Best, Paul

--- Mystic BBS v1.12 A39 2018/03/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Here the connection issue is using the node specification in Mystic as well as nodelisted node specifications. I have tried making both Ipv4 as well as IPv6 connections and get a similar response although the result number changes.

Okay, thanks for the information. I'll try to get my BBS moved over to Linux or the Pi for some more testing.

--- Mystic BBS v1.12 A39 2018/03/26 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Can you guys look to see what your "IPV4/IPV6" settings are for the sites you are connecting to? Or are these connections to nodes resol from the nodelist?

It's an entry in Networking/Echomail Nodes. IPv4

Okay just to confirm: I am going to assume in your echomail node settings for the node you're connecting to that you have the IP type set to "IPV4"? (not "Default IPV4" or something else). If that is NOT the case let me know.

Thanks for the update. I'll see what I can figure out!

--- Mystic BBS v1.12 A39 2018/03/26 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

compare this to another system... I note your end is sending the ADR line twice, I wonder why?

I think its because the OS is reporting to Mystic that it should try to resend, and when it does, it gets the same error again and the connection drops. Thats sort of what it looked like based on the error messages.

I am going to try to move my BBS over to Pi or Linux this weekend and get it fixed up. Maybe I'll just leave it up on the Pi for a while and schedule it to poll you every couple of hours to see how it keeps up.

I just recently added the "Auto IP" functions to binkp, ftp client, and sendmail client, along with nodespy telnet/ssh/rlogin clients. Obviously something isn't going right on the Linux side...

--- Mystic BBS v1.12 A39 2018/03/26 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Hello g00r00,

Here the connection issue is using the node specification in Mystic as
well as nodelisted node specifications. I have tried making both Ipv4 as
well as IPv6 connections and get a similar response although the result
number changes.

Okay, thanks for the information. I'll try to get my BBS moved over to Linux or the Pi for some more testing.

Cool, thanks. Currently I have Mystic installed on two Windows PC's (Win32, Win64) and Linux 64b x2, as well as a Raspberry Pi3 32b. But am currently using
BBBS to connect to Avon for echomail.

If I can be of any assistance or if I can provide an necessary info. Just let me know.


Jeff


--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

On 03/28/18, Jeffs pondered and said...

So far it happens here on every outbound poll using FIDOPOLL.

Can you guys look to see what your "IPV4/IPV6" settings are for the sites you are connecting to? Or are these connections to nodes resol from the nodelist?

Here the connection issue is using the node specification in Mystic as well as nodelisted node specifications. I have tried making both Ipv4 as well as IPv6 connections and get a similar response although the result number changes.

I for example have polled Avon at 21:1/100 which is configured as a node specification in Mystic. And I have polled nodes that are not in Mystic
as a node specification and in either case I get the same connection issue.

I see the following at this end when I Fidopoll you from the HUB now

[snip]

Mar 30 16:41:49 Queued 1 files (28060 bytes) to 21:1/128
Mar 30 16:41:49 Polling BINKP node 21:1/128 by IPV4
Mar 30 16:41:49 Connecting to bbs2.ouijabrd.net
Mar 30 16:41:49 Using address 65.103.12.162
Mar 30 16:41:49 Connected IPV4 to 65.103.12.162
Mar 30 16:41:49 S: NUL SYS fsxHUB [fsxNet WHQ]
Mar 30 16:41:49 S: NUL ZYZ Paul Hayton
Mar 30 16:41:49 S: NUL VER Mystic/1.12A39 binkp/1.0
Mar 30 16:41:49 S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
Mar 30 16:41:49 C: NUL
Mar 30 16:41:51 Info
Mar 30 16:41:51 RB Socket read result 10053
Mar 30 16:41:51 RB Socket read result 10053
Mar 30 16:41:51 Connection lost
Mar 30 16:41:51 Authorization failed


[snip]


There's a ton of chars that don't seem to post in this logging but in the
text file it's a mess and the fidopoll screen was busy also :)

--- Mystic BBS v1.12 A39 2018/03/29 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I see the following at this end when I Fidopoll you from the HUB now

I am assuming he's not using the fixed version.

--- Mystic BBS v1.12 A39 2018/03/30 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 03/30/18, g00r00 pondered and said...

I am assuming he's not using the fixed version.

Not sure.

I did a test poll using an earlier build and saw this

[snip]

Mar 31 16:02:20 Polling BINKP node 21:1/128 by IPV4
Mar 31 16:02:20 Connecting to bbs2.ouijabrd.net
Mar 31 16:02:21 Connected
Mar 31 16:02:21 S: NUL SYS fsxHUB Mutura [NET3]
Mar 31 16:02:21 S: NUL ZYZ Paul Hayton
Mar 31 16:02:21 S: NUL VER Mystic/1.12A39 binkp/1.0
Mar 31 16:02:21 S: ADR 21:3/100@fsxnet
Mar 31 16:02:21 RB Socket read loop 0
Mar 31 16:02:21 RB Socket read result 0
Mar 31 16:02:21 RB Socket read loop 0
Mar 31 16:02:21 RB Socket read result 0
Mar 31 16:02:21 Connection lost
Mar 31 16:02:21 Authorization failed

[snip]

a recent poll using the latest build I have looks like

[snip]

Mar 31 16:01:12 Scanning 21:1/128
Mar 31 16:01:12 Queued 1 files (1378 bytes) to 21:1/128
Mar 31 16:01:12 Polling BINKP node 21:1/128 by IPV4
Mar 31 16:01:12 Connecting to bbs2.ouijabrd.net
Mar 31 16:01:13 Using address 65.103.12.162
Mar 31 16:01:13 Connected IPV4 to 65.103.12.162
Mar 31 16:01:13 S: NUL SYS fsxHUB [fsxNet WHQ]
Mar 31 16:01:13 S: NUL ZYZ Paul Hayton
Mar 31 16:01:13 S: NUL VER Mystic/1.12A39 binkp/1.0
Mar 31 16:01:13 S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
Mar 31 16:01:13 C: NUL
Mar 31 16:01:13 Info
Mar 31 16:01:13 RB Socket read result 10053
Mar 31 16:01:13 Error receiving data (RB Socket read buffer result -1 10053 Size=15469/25600)
Mar 31 16:01:13 Connection lost
Mar 31 16:01:13 Authorization failed

[snip]

When I look at the logs using Notepad++ I see a DLE character repeated over
and over on both NUL and Info lines despite the fact they appear blank above.

Incoming logs in MIS look OK

[snip]

+ 2018.03.31 15:49:53 BINKP > Connect on slot 1/25 (65.103.12.162)
+ 2018.03.31 15:49:53 BINKP 1-HostName Unknown
+ 2018.03.31 15:49:53 BINKP 1-Country United States of America (US)
+ 2018.03.31 15:49:53 BINKP 1-S: NUL OPT CRAM-MD5-558d4ae9f154b8fd2b4170a8ecce87b7
+ 2018.03.31 15:49:53 BINKP 1-C: NUL SYS The Ouijaboard II
+ 2018.03.31 15:49:53 BINKP 1-System The Ouijaboard II
+ 2018.03.31 15:49:53 BINKP 1-S: NUL SYS fsxHUB [fsxNet WHQ]
+ 2018.03.31 15:49:53 BINKP 1-S: NUL ZYZ Paul Hayton
+ 2018.03.31 15:49:53 BINKP 1-S: NUL VER Mystic/1.12A39 binkp/1.0
+ 2018.03.31 15:49:53 BINKP 1-S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
+ 2018.03.31 15:49:53 BINKP 1-C: NUL ZYZ Jeff Smith
+ 2018.03.31 15:49:53 BINKP 1-SysOp Jeff Smith
+ 2018.03.31 15:49:53 BINKP 1-C: NUL VER Mystic/1.12A39 binkp/1.0
+ 2018.03.31 15:49:53 BINKP 1-Mailer Mystic/1.12A39 binkp/1.0
+ 2018.03.31 15:49:53 BINKP 1-C: ADR 1:282/1032@fidonet 21:1/128@fsxnet
+ 2018.03.31 15:49:54 BINKP 1-C: PWD
+ 2018.03.31 15:49:54 BINKP 1-Authenticating 21:1/128@fsxnet by Cleartext
+ 2018.03.31 15:49:54 BINKP 1-S: OK secure
+ 2018.03.31 15:49:54 BINKP 1-Queued 1 files for 21:1/128@fsxnet
+ 2018.03.31 15:49:54 BINKP 1-Sending: 0000ffe4.saj (2,383 bytes)
+ 2018.03.31 15:49:54 BINKP 1-S: FILE 0000ffe4.saj 2383 1522510988 0
+ 2018.03.31 15:49:54 BINKP 1-C: EOB
+ 2018.03.31 15:49:54 BINKP 1-C: GOT 0000ffe4.saj 2383 1522510988
+ 2018.03.31 15:49:55 BINKP 1-S: EOB
+ 2018.03.31 15:49:55 BINKP 1-Session ended (1 sent, 0 rcvd, 0 skip)

[snip]

I'll contact Jeff to see what I can figure out.

--- Mystic BBS v1.12 A39 2018/03/29 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)