I am updating the pre-alphas right now. Fixes and only minor changes.

Still looking to release an A45 bugfix within the next week before I start adding/breaking more stuff.

So if you know of anything not working in A45 please let me know! Or if you already told me and its not addressed yet please tell me again because I may have forgot.

Keep in mind A45 will just be a simply copy over so anything that would involve record changes (like enabling log rolling configuration for MIS, etc) or something that would cause it not to be a simple copy-over will be A46.

--- Mystic BBS v1.12 A45 2020/02/14 (Windows/64)
* Origin: Sector 7 (21:1/108)

I am updating prealphas with some fixes and changes including several to BINKP that I would appreciate getting tested. They will be up in about 5 minutes
or less.

--- Mystic BBS v1.12 A45 2020/02/15 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 15 Feb 2020 at 07:51p, g00r00 pondered and said...

I am updating prealphas with some fixes and changes including several to BINKP that I would appreciate getting tested. They will be up in about
5 minutes or less.

I will update NET 1 in the coming hour or so. Just need to collect a teenager from the movies in 30 mins :)

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

On 15 Feb 2020 at 07:51p, g00r00 pondered and said...

I am updating prealphas with some fixes and changes including several to BINKP that I would appreciate getting tested. They will be up in about
5 minutes or less.

Just checking is it build v1.12 A45 Windows/32 Compiled 2020/02/15 20:28:45 ??

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

I am updating prealphas with some fixes and changes including several BINKP that I would appreciate getting tested. They will be up in abo 5 minutes or less.

Just checking is it build v1.12 A45 Windows/32 Compiled 2020/02/15 20:28:45 ??

Yes I think that is it

--- Mystic BBS v1.12 A45 2020/02/15 (Windows/64)
* Origin: Sector 7 (21:1/108)

I am updating prealphas with some fixes and changes including several to BINKP that I would appreciate getting tested. They will be up in about

Just got a copy of it. Will be doing the back up & install it over like
normal.

Thanks again for the update.

ACME BBS-Member of fsxNet/WWIVNet/SciNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A45 2020/02/09 (Windows/32)
* Origin: ACME BBS-I am Wile E Ki-oh-tay, super genius (21:2/147)

I am updating the Prealphas today it should be done in a few minutes.

This update will have some changes to the new MIS POLL to fix display errors and to introduce some other statistical tracking.

The MUTIL [EchoMailTracker] is enabled but if you decide to try it please be very careful because it has not had a good run through of testing yet. I
will be setting up some test cases for these features soon.

I would love assistance if someone wants to try it, but I recognize this is mostly for HUBs where they may not want to risk restoring if something doesn't work.

At the very least MIS POLL seems stable and complete though in this build.

--- Mystic BBS v1.12 A46 2020/03/01 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 01 Mar 2020 at 12:39p, g00r00 pondered and said...

I am updating the Prealphas today it should be done in a few minutes.

applied this to 1/100

This update will have some changes to the new MIS POLL to fix display errors and to introduce some other statistical tracking.

The updated display looks cool and very busy. I'll try and grab a screen shot of it here.

20:14:11 2-SysOp Night Stalker
20:14:11 2-Info TIME Sun, 01 Mar 2020 02:14:12 -0500
20:14:11 1-Polling 21:1/183 on slot 1 via BINKP
20:14:11 2-Mailer Mystic/1.12A43 binkp/1.0
20:14:11 1-Connecting to vert.synchro.net on port 24554
20:14:11 5-Session ended (1 sent, 0 rcvd, 0 skip)
20:14:11 Queued 1 files (770 bytes) for 21:1/185
20:14:11 5-Polling 21:1/185 on slot 5 via BINKP
20:14:11 2-Info BUILD 2019/03/03 01:42:47 Raspberry Pi/32
20:14:11 Queued 1 files (770 bytes) for 21:1/186
20:14:11 5-Connecting to idomain.synchro.net on port 24554
20:14:11 Waiting for available send slot for 21:1/186
20:14:11 4-Sending: 0000ffb0.suc (770 bytes) ──────────────────────────────────────────────────────────────────────────
System ────────────────── SysOp ────────────────────────── Address/Domain
Rob Swindell / Vertrauen B Rob Swindell 21:1/183@fsxnet
Dave Vandermeer / Internal Dave Vandermeer 21:1/178@fsxnet Ismar Hasanbegovic / Dali' Ismar Hasanbegovic 21:1/177@fsxnet
Jeff Thiele / Perceptronic Jeff Thiele 21:1/180@fsxnet Steve Helferich / Immortal Steve Helferich 21:1/185@fsxnet Jordan McGilvray / Colossu Jordan McGilvray 21:1/182@fsxnet

The MUTIL [EchoMailTracker] is enabled but if you decide to try it
please be very careful because it has not had a good run through of testing yet. I will be setting up some test cases for these features soon.

I would love assistance if someone wants to try it, but I recognize this is mostly for HUBs where they may not want to risk restoring if
something doesn't work.

At the very least MIS POLL seems stable and complete though in this
build.

I'm going to try and get the SSH going on 24553 first. If anyone wants to
test this at 21:1/100 please let me know.

The port should now be open and the server running.

--- Mystic BBS v1.12 A46 2020/02/29 (Windows/32)
* Origin: All extremists should be shot. (21:1/101)

I'm going to try and get the SSH going on 24553 first. If anyone wants to test this at 21:1/100 please let me know.

The port should now be open and the server running.

I just tried it and it couldn't connect. Is the port behind a firewall by chance? Could of couse be a bug. I should retest locally to make sure I
didnt break anything.

--------------------- POLL v1.12 A46 2020/03/01 Sun, Mar 01 2020 (loglevel 2) + 2020.03.01 14:59:34 Poll BINKP node via address lookup: 21:1/100
+ 2020.03.01 14:59:34 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.01 14:59:34 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.01 14:59:41 1-Unable to connect
+ 2020.03.01 14:59:41 Polled 1 systems

--- Mystic BBS v1.12 A46 2020/03/01 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 01 Mar 2020 at 02:55p, g00r00 pondered and said...

I just tried it and it couldn't connect. Is the port behind a firewall
by chance? Could of couse be a bug. I should retest locally to make
sure I didnt break anything.

I'm fairly sure its open. will keep playing, just posted some stuff to the
echo about this :)

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

Hello Avon!

On 01 Mar 2020, Avon said the following...

I'm going to try and get the SSH going on 24553 first. If anyone wants to test this at 21:1/100 please let me know.

The port should now be open and the server running.

I can connect, but I get an authorization failure:

--------------------- POLL v1.12 A46 2020/03/01 Sun, Mar 01 2020 (loglevel 2) + 2020.03.01 09:13:47 Polling all nodes of session type ALL
+ 2020.03.01 09:13:47 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.01 09:13:47 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.01 09:13:47 1-Connected by IPV4 to 219.89.83.33
+ 2020.03.01 09:13:48 1-Connection lost
+ 2020.03.01 09:13:48 1-Authorization failed
+ 2020.03.01 09:13:49 Polled 1 systems

I have scbbs.nsupdate.info:24553 up and running if you'd like to try a forced send to me or similar. =)

(I have reverted to agency.bbs.nz:24556 and Use SSL/TLS: No in the mean time
so that I can fetch mail from you.)

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/03/01 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

On 01 Mar 2020 at 09:18a, Zip pondered and said...

I can connect, but I get an authorization failure:

--------------------- POLL v1.12 A46 2020/03/01 Sun, Mar 01 2020 (loglevel 2) + 2020.03.01 09:13:47 Polling all nodes of session type ALL + 2020.03.01 09:13:47 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.01 09:13:47 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.01 09:13:47 1-Connected by IPV4 to 219.89.83.33
+ 2020.03.01 09:13:48 1-Connection lost
+ 2020.03.01 09:13:48 1-Authorization failed
+ 2020.03.01 09:13:49 Polled 1 systems

what I see internally when I force the BinkP Hostname to include a port
number.

I have scbbs.nsupdate.info:24553 up and running if you'd like to try a forced send to me or similar. =)

I changed your settings at 1/100 to

BINKP Hostname │ scbbs.nsupdate.info
IP Type │ IPV4
Password │ *******
Time Out │ 30
Block Size │ 16384
CRAM-MD5 │ Yes
Use SSL/TLS │ Yes
Hide AKAs │ Yes
│

The did a MIS POLL 21:1/202

--------------------- POLL v1.12 A46 2020/03/01 Sun, Mar 01 2020 (loglevel 2) + 2020.03.01 21:24:04 Poll BINKP node via address lookup: 21:1/202
+ 2020.03.01 21:24:04 Queued 1 files (3,409 bytes) for 21:1/202
+ 2020.03.01 21:24:04 1-Polling 21:1/202 on slot 1 via BINKP
+ 2020.03.01 21:24:04 1-Connecting to scbbs.nsupdate.info on port 24553
+ 2020.03.01 21:24:11 1-Unable to connect
+ 2020.03.01 21:24:11 Polled 1 systems

No joy there.

Then opted to try stating the port in the BinkP Hostname

BINKP Hostname │ scbbs.nsupdate.info:24553
IP Type │ IPV4
Password │ *******
Time Out │ 30
Block Size │ 16384
CRAM-MD5 │ Yes
Use SSL/TLS │ Yes
Hide AKAs │ Yes

and tried another poll

21:25:25 Poll BINKP node via address lookup: 21:1/202
21:25:25 Queued 1 files (3,409 bytes) for 21:1/202
21:25:25 1-Polling 21:1/202 on slot 1 via BINKP
21:25:25 1-Connecting to scbbs.nsupdate.info on port 24553
21:25:26 1-Connected by IPV4 to 83.254.233.176
21:25:27 1-Error receiving data (Msg= Size=0/6351) (Res=-1)
21:25:27 1-Connection lost
21:25:27 1-Authorization failed
21:25:27 Polled 1 systems

so that worked better but not success..

I will revert to SSL = NO and go back to your usual port for now

I have a feeling g00r00 may spot something soon.

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

I just tried it and it couldn't connect. Is the port behind a firewa by chance? Could of couse be a bug. I should retest locally to make sure I didnt break anything.

I'm fairly sure its open. will keep playing, just posted some stuff to
the echo about this :)

Found the issue I believe, and I am uploading a new version as I type this.

--- Mystic BBS v1.12 A46 2020/03/01 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 01 Mar 2020 at 03:38p, g00r00 pondered and said...

Found the issue I believe, and I am uploading a new version as I type this.

Thanks :)

Getting late here but will try to update and test before eyeballs fall out

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

Thanks :)

Getting late here but will try to update and test before eyeballs fall
out

Well good news I just successfully exchanged via SSL with you. So at least
its working with another Mystic system.

Hopefully eyeballs have preserved and will live another day!

--- Mystic BBS v1.12 A46 2020/03/01 (Windows/64)
* Origin: Sector 7 (21:1/108)

Hello Avon!

On 01 Mar 2020, Avon said the following...

I can connect, but I get an authorization failure:

what I see internally when I force the BinkP Hostname to include a port number.

Thanks!

I removed :24553 from your hostname in my echomail node configuratoin and now it seems to poll you OK over SSL:

--------------------- POLL v1.12 A46 2020/03/01 Sun, Mar 01 2020 (loglevel 2) + 2020.03.01 09:52:48 Polling all nodes of session type ALL
+ 2020.03.01 09:52:48 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.01 09:52:48 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.01 09:52:51 1-Connected by IPV4 SSL to 219.89.83.33
+ 2020.03.01 09:52:51 1-System fsxHUB Risa [NET1]
+ 2020.03.01 09:52:51 1-SysOp Avon
+ 2020.03.01 09:52:51 1-Info TIME Sun, 01 Mar 2020 21:52:50 +1300
+ 2020.03.01 09:52:51 1-Mailer Mystic/1.12A46 binkp/1.0
+ 2020.03.01 09:52:51 1-Info BUILD 2020/03/01 15:36:07 Windows/32
+ 2020.03.01 09:52:53 1-Remote Queue: 0 files 0 bytes
+ 2020.03.01 09:52:53 1-Session ended (0 sent, 0 rcvd, 0 skip)
+ 2020.03.01 09:52:54 Polled 1 systems

But then you should have been able to poll me as well? Hmm...

I have a feeling g00r00 may spot something soon.

Perhaps something related to Cryptlib on Windows?

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/03/01 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

I removed :24553 from your hostname in my echomail node configuratoin
and now it seems to poll you OK over SSL:

I think thats just a timing thing. We are swapping versions as you're
testing this stuff :)

--- Mystic BBS v1.12 A46 2020/03/01 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 01 Mar 2020 at 09:57a, Zip pondered and said...

I removed :24553 from your hostname in my echomail node configuratoin
and now it seems to poll you OK over SSL:

--------------------- POLL v1.12 A46 2020/03/01 Sun, Mar 01 2020 (loglevel 2) + 2020.03.01 09:52:48 Polling all nodes of session type ALL + 2020.03.01 09:52:48 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.01 09:52:48 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.01 09:52:51 1-Connected by IPV4 SSL to 219.89.83.33

that's good :)

But then you should have been able to poll me as well? Hmm...

I have a feeling g00r00 may spot something soon.

Perhaps something related to Cryptlib on Windows?

Best regards

It was a windows bug that g00r00 just fixed and I updated at 1/100 so let me try a poll to you now... hang a tic.


--------------------- POLL v1.12 A46 2020/03/01 Sun, Mar 01 2020 (loglevel 2) + 2020.03.01 22:02:13 Poll BINKP node via address lookup: 21:1/202
+ 2020.03.01 22:02:13 Queued 1 files (2,681 bytes) for 21:1/202
+ 2020.03.01 22:02:13 1-Polling 21:1/202 on slot 1 via BINKP
+ 2020.03.01 22:02:13 1-Connecting to scbbs.nsupdate.info on port 24553
+ 2020.03.01 22:02:14 1-Connected by IPV4 to 83.254.233.176
+ 2020.03.01 22:02:16 1-Error receiving data (Msg= Size=0/6351) (Res=-1)
+ 2020.03.01 22:02:16 1-Connection lost
+ 2020.03.01 22:02:16 1-Authorization failed
+ 2020.03.01 22:02:16 Polled 1 systems

No joy... but it may be your build needs an update to..

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

On 01 Mar 2020 at 03:56p, g00r00 pondered and said...

Well good news I just successfully exchanged via SSL with you. So at least its working with another Mystic system.

Hopefully eyeballs have preserved and will live another day!

:)

Righto it's coming up 10pm Sun night here and I have work in the morning so
I'm going to need to pull the plug for now and get to bed.

Happy to test some more tomorrow night etc. and thanks to all for your help testing 1/100 I am going to leave the port 24553 up for SSL connects from now on.

Deon and Al - yep to more tests, will look to do so tomorrow.

Night all.

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

Hello g00r00!

On 01 Mar 2020, g00r00 said the following...

I think thats just a timing thing. We are swapping versions as you're testing this stuff :)

Yep! =)

I just upgraded my L64 version as well (downloaded it 5 minutes ago),
and it seems to (still) poll just fine using SSL.

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/03/01 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Hello Avon!

On 01 Mar 2020, Avon said the following...

No joy... but it may be your build needs an update to..

Just updated it, so please try again! :)

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/03/01 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

I just upgraded my L64 version as well (downloaded it 5 minutes ago),
and it seems to (still) poll just fine using SSL.

Great to hear and that will save me some time.

I've been pushing really hard the last few days to get the new MIS POLL function, SSL, and all of the new download hub automation stuff in place.

I think its time for me to go do something else for a few hours this evening for my own sanity. :)

Thanks for helping to test!

--- Mystic BBS v1.12 A46 2020/03/01 (Windows/64)
* Origin: Sector 7 (21:1/108)

Hello g00r00!

On 01 Mar 2020, g00r00 said the following...

Great to hear and that will save me some time.

Glad to hear that! :)

I think its time for me to go do something else for a few hours this evening for my own sanity. :)

=)

Thanks for helping to test!

You're very welcome!

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/03/01 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Re: Re: Prealphas
By: Avon to g00r00 on Sun Mar 01 2020 10:07 pm

Deon and Al - yep to more tests, will look to do so tomorrow.

FYI, I update Hub 3 to the latest synchronet, and SSL polled you:

Connection to agency.bbs.nz:24553 successful
Negotiating TLS
...
Got M_NUL command args: OPT CRAM-MD5-fc08764d08635b53228507c91c69b24c
Got M_NUL command args: SYS fsxHUB Risa [NET1]
Got M_NUL command args: ZYZ Avon
Got M_NUL command args: TIME Mon, 02 Mar 2020 00:32:12 +1300
Got M_NUL command args: VER Mystic/1.12A46 binkp/1.0
Peer version: Mystic/1.12A46 binkp/1.0
Got M_NUL command args: BUILD 2020/03/01 15:36:07 Windows/32
Got M_ADR command args: 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
Sending M_PWD command args: CRAM-MD5-2638083c2692688b68843157b3113a9f
Sent M_PWD command
Got M_OK command args: secure
Authentication successful: secure
...
Adding outbound files for 21:1/100@fsxnet
Sending M_EOB command args:
Sent M_EOB command
Got M_NUL command args: QSIZE 0 files 0 bytes
Got M_EOB command args:
Unlocking C:/mailer/outbound.015\00010064.bsy.

It was a success :)

I'll setup Hub 3 to receive inbound TLS - and send the details.
...deon


... What do you mean? You actually read this Tagline?!?
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: Prealphas
By: alter ego to Avon on Sun Mar 01 2020 10:37 pm

I'll setup Hub 3 to receive inbound TLS - and send the details.

OK, hub 3 is on alterant.leenooks.net:24556 (synchronet windows), and my BBS 2/116 is on alterant.leenooks.net:24553 (synchronet linux).

Anybody who wants to test binkps is welcome to.
...deon


... There are some things worth dying for. Kirk, Errand of Mercy, stardate 320 --- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hello alter,

OK, hub 3 is on alterant.leenooks.net:24556 (synchronet windows), and
my BBS 2/116 is on alterant.leenooks.net:24553 (synchronet linux).

I tried both 21 3/0 and 2/116 and I get the same key too small error.

So, I can't poll Synchronet or Mystic presently with binkd. Can you try polling
here?

21:4/106 trmb.ca:24553.

I'm not sure what the solution is here, I'll have to ask Oli for advice.

Maybe I need to tone my ssl down or Mystic and SBBS need to turn it up. That's a technical detail I don't know.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hello alter,

I'll setup Hub 3 to receive inbound TLS - and send the details.

OK, hub 3 is on alterant.leenooks.net:24556 (synchronet windows), and
my BBS 2/116 is on alterant.leenooks.net:24553 (synchronet linux).

I have tried both of these. It connects but fails for some reason, something about the certificates.

If you have made changes those certs may need to be deleted and recreated. I'm guessing there. I'm not sure what the problem is.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 01 Mar 2020, Al said the following...

I have tried both of these. It connects but fails for some reason, something about the certificates.

Maybe its the TLS < v1.2 situation?

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: DaRK Game BBS (21:2/161)

Hello buanzo,

I have tried both of these. It connects but fails for some
reason, something about the certificates.

Maybe its the TLS < v1.2 situation?

Maybe, that one is still under investigation. I did use -cipher ALL:@SECLEVEL=1
for that test. openssl spit out some errors and I'm not exactly sure why.

Will have to keep testing.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

I have tried both of these. It connects but fails for some reason, something about the certificates.

Maybe its the TLS < v1.2 situation?

Mystic requires TLS 1.2 and won't operate on anything less so that should not be a factor.

--- Mystic BBS v1.12 A46 2020/03/01 (Windows/64)
* Origin: Sector 7 (21:1/108)

Re: Prealphas
By: Al to alter ego on Sun Mar 01 2020 10:00 am

So, I can't poll Synchronet or Mystic presently with binkd. Can you try polling
here?

So I've set you up on Hub 3, and did a poll, looks like it worked :)

Connecting to 21:4/106@fsxnet at trmb.ca:24553
Connection to trmb.ca:24553 successful
Negotiating TLS
...
Sent M_ADR command
Got M_NUL command args: OPT CRAM-MD5-275803802e25bf0161500a83b4c501ee
Got M_NUL command args: SYS The Rusty MailBox
Got M_NUL command args: ZYZ Alan Ianson
Got M_NUL command args: LOC Penticton, BC Canada
Got M_NUL command args: NDL 115200,CM,XW,IBN
Got M_NUL command args: TIME Sun, 1 Mar 2020 18:03:12 -0800
Got M_NUL command args: VER binkd/1.1a-101/Linux binkp/1.1
Peer version: binkd/1.1a-101/Linux binkp/1.1
Got M_ADR command args: 1:153/757@fidonet 1:153/0@fidonet 21:4/106@fsxnet 32:1/5@gamenet
Sending M_PWD command args: CRAM-MD5-da81f5a253dc6b35cdb0cad3f7ec582c
Sent M_PWD command
Got M_NUL command args: TRF 0 0
Got M_NUL command args: OPT EXTCMD GZ BZ2
Got M_OK command args: non-secure
Authentication successful: non-secure
Adding outbound files for 21:4/106@fsxnet
Error in recv() of first byte of packet header
Unlocking C:/mailer/outbound.015\0004006a.bsy.
C:\BBS\SBBS\exec\binkit.js executed in 3.80 seconds

Although, "Error in recv()..." not sure what you see on your side...
...deon


... An optimist is a man who starts a crossword puzzle with a fountain pen.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hello alter,

So, I can't poll Synchronet or Mystic presently with binkd. Can
you try polling here?

Error in recv() of first byte of packet header

Although, "Error in recv()..." not sure what you see on your side...

I'm not sure either. That poll looks good here. I was being a little chincy with my log level but have turned it up a bit now. I don't see any errors here on my side..


=== Cut ===
- 01 Mar 18:03:12 [31320] incoming from 127.0.0.1 (48332)
+ 01 Mar 18:03:12 [8507] incoming session with localhost [127.0.0.1]

The above means the poll was answered on port 24553 by a web server and passed to binkd.

- 01 Mar 18:03:12 [8507] SYS W7-1-1
- 01 Mar 18:03:12 [8507] ZYZ alterego
- 01 Mar 18:03:12 [8507] LOC Parkdale VIC
- 01 Mar 18:03:12 [8507] NDL 115200,TCP,BINKP
- 01 Mar 18:03:12 [8507] TIME Mon Mar 02 2020 13:03:12 GMT+1100 (AUS Eastern Daylight Time)
- 01 Mar 18:03:12 [8507] VER BinkIT/2.28,JSBinkP/1.122,sbbs3.17c/Win32 binkp/1.1
+ 01 Mar 18:03:12 [8507] addr: 21:3/100@fsxnet
+ 01 Mar 18:03:12 [8507] addr: 618:510/2@micronet (n/a or busy)
+ 01 Mar 18:03:12 [8507] addr: 10:1/2@private (n/a or busy)
+ 01 Mar 18:03:12 [8507] addr: 516:999/998@videotex (n/a or busy)
+ 01 Mar 18:03:12 [8507] done (from 21:3/100@fsxnet, OK, S/R: 0/0 (0/0 bytes))
01 Mar 18:03:12 [8507] session closed, quitting...
01 Mar 18:03:12 [31320] rc(8507)=0
=== Cut ===

There is no mention of errors in my log but I have now turned up the verbosity so it may show more now. Also in my setup the tls is done by openssl so it is not logged by binkd.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Re: Prealphas
By: Al to alter ego on Sun Mar 01 2020 06:17 pm

There is no mention of errors in my log but I have now turned up the verbosity so it may show more now. Also in my setup the tls is done by openssl so it is not logged by binkd.

Hmm, ok, it might be that we dont have a password set, now that I've defined you in echocfg.

Although I do see "timeout receiving first byte of packet..." so not sure why it thinks a packet is transferring..

Interesting, I also see "Will Encrypt Session", which seems redundant if its a TLS session - but I'll pay more attention when there is some mail flow and check with DM if it continues.

Let me know if you want a password so that you can pull some packets from Hub 3.
...deon


... It is a rather pleasant experience to be alone in a bank at night.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 01 Mar 2020 at 10:53p, alter ego pondered and said...

OK, hub 3 is on alterant.leenooks.net:24556 (synchronet windows), and my

Anybody who wants to test binkps is welcome to.

I tried using both 2/100 and 1/100 and hit the same sort of errors

20:59:59 Poll BINKP node via address lookup: 21:3/100
20:59:59 1-Polling 21:3/100 on slot 1 via BINKP
20:59:59 1-Connecting to alterant.leenooks.net on port 24556
20:59:59 1-Connected by IPV4 to 101.186.5.106
21:00:31 1-Data frame timeout
21:00:31 1-Connection lost
21:00:31 1-Authorization failed
21:00:32 Polled 1 systems

I have a theory that because I am stating a port in your Mystic BinkP
Hostname for some reason the session with SSL set to yes is failing.

I found this was happening when I tested 2/100 polling 1/100 with agency.bbs.nz:24553 set as the BinkP Hostname and SSL set to Yes

But if I removed the port and left SSL set to yes when Mystic polled 1/100 I got a successful SSL connect. I saw a similar thing for Dan at NET 4

With port number in BinkP Hostname

--------------------- POLL v1.12 A46 2020/03/01 Mon, Mar 02 2020 (loglevel 2) + 2020.03.02 03:04:50 Poll BINKP node via address lookup: 21:4/100
+ 2020.03.02 03:04:50 1-Polling 21:4/100 on slot 1 via BINKP
+ 2020.03.02 03:04:50 1-Connecting to BBS.CASTLEROCKBBS.COM on port 24553
+ 2020.03.02 03:04:50 1-Connected by IPV4 to 184.155.113.241
+ 2020.03.02 03:04:53 1-Connection lost
+ 2020.03.02 03:04:53 1-Authorization failed
+ 2020.03.02 03:04:53 Polled 1 systems

With no port number in BinkP Hostname..


--------------------- POLL v1.12 A46 2020/03/01 Mon, Mar 02 2020 (loglevel 2) + 2020.03.02 03:05:17 Poll BINKP node via address lookup: 21:4/100
+ 2020.03.02 03:05:17 1-Polling 21:4/100 on slot 1 via BINKP
+ 2020.03.02 03:05:17 1-Connecting to BBS.CASTLEROCKBBS.COM on port 24553
+ 2020.03.02 03:05:18 1-Connected by IPV4 SSL to 184.155.113.241
+ 2020.03.02 03:05:18 1-System fsxHUB Niba [NET4]
+ 2020.03.02 03:05:18 1-SysOp Black Panther
+ 2020.03.02 03:05:18 1-Info TIME Mon, 02 Mar 2020 01:05:19 -0700
+ 2020.03.02 03:05:18 1-Mailer Mystic/1.12A46 binkp/1.0
+ 2020.03.02 03:05:18 1-Info BUILD 2020/03/01 15:36:07 Windows/32
+ 2020.03.02 03:05:18 1-Remote Queue: 0 files 0 bytes
+ 2020.03.02 03:05:18 1-Session ended (0 sent, 0 rcvd, 0 skip)
+ 2020.03.02 03:05:20 Polled 1 systems

I think g00r00 may need to look at this a little further :)

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

Hello alter,

Although I do see "timeout receiving first byte of packet..." so not
sure why it thinks a packet is transferring..

I've seen that error reported in my own logs before. I don't know why but it was never troublesome so I never worried about it any.

Might be good to resolve that if we can.

Interesting, I also see "Will Encrypt Session", which seems redundant
if its a TLS session - but I'll pay more attention when there is some
mail flow and check with DM if it continues.

The binkp protocol hasn't been updated at all for binkps. The protocol and session works as always. We have just put binkp on a secure channel.

Let me know if you want a password so that you can pull some packets
from Hub 3.

If you can set my node up and send me the details I'll setup likewise. If we get incomunicado somehow you can email me at agianson {at} gmail {dot} com

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Re: Prealphas
By: Al to alter ego on Mon Mar 02 2020 03:46 am

If you can set my node up and send me the details I'll setup likewise. If we get incomunicado somehow you can email me at agianson {at} gmail {dot} com

Just sent an email - let me know if you find anythig amiss...
...deon


... What a man needs in gardening is a cast iron back with a hinge in it.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Prealphas
By: alter ego to Al on Mon Mar 02 2020 11:47 pm

If you can set my node up and send me the details I'll setup
likewise. If we get incomunicado somehow you can email me at

Looks like it is working well...

3/3 07:35:38a 0296 BINKPS connection accepted from: 172.105.21.200 port 43462
3/3 07:35:38a 0296 BINKPS BinkIT/2.28 invoked with options:
3/3 07:35:38a 0296 BINKPS JSBinkP/1.122 inbound connection from 172.105.21.200:43462
3/3 07:35:39a 0296 BINKPS Peer version: binkd/1.1a-101/Linux binkp/1.1
3/3 07:35:39a 0296 BINKPS Will encrypt session.
3/3 07:35:39a 0296 BINKPS Remote addresses: 1:153/757@fidonet 1:153/0@fidonet 21:4/106@fsxnet 32:1/5@gamenet
3/3 07:35:39a 0296 BINKPS Inbound session for: 21:4/106@fsxnet
3/3 07:35:39a 0296 BINKPS CRAM-MD5 password match for 21:4/106@fsxnet
3/3 07:37:39a 0296 BINKPS Timed out receiving first byte of packet header!
3/3 07:37:39a 0296 BINKPS service thread terminated (0 clients remain, 0 total, 31 served)
...deon


... Confound these ancestors They've stolen our best ideas!
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Alright you have my interest..

I've been reading the ongoing discussion on binkps and I would like to join
the "fun" if you will. I'm all about using SSL wherever possible. I'm
assuming however, in order to join the "fun" I need to upgrade to A46.. This has been the only thing that is keeping me from joining in on the "fun".

I've also noticed A46 introduces a new mis poll, is there action(s) I'll need to take to get my networks functional once I upgrade?

Originally, I was planning to wait for A46 to be released as more "stable",
as I recently trashed my BBS last weekend due to a mistake on my part.. But this binkps is a bit too tempting to wait on..

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Eggy BBS (21:4/143)

I've been reading the ongoing discussion on binkps and I would like to join the "fun" if you will. I'm all about using SSL wherever possible.

Most of that discussion is about BINKD and SSL. The SSL in Mystic has changed in A46 to be more compatible with the mailers that just tunnel SSL instead of opportunistic SSL that it used in A43, A44, A45, etc.

If you want to use SSL with BINKP you will need to upgrade to the latest A46 prealpha (and there is potential that everyone will need to delete their ssl.cert in DATA folder but that remains to be confirmed. And its also possible this will break compatibility with Synchronet).

I've also noticed A46 introduces a new mis poll, is there action(s) I'll need to take to get my networks functional once I upgrade?

You just change "fidopoll" to "mis poll" and thats it. The commands are
still the same otherwise. So if you have "fidopol send" you would change
that to "mis poll send".

--- Mystic BBS v1.12 A46 2020/03/02 (Windows/64)
* Origin: Sector 7 (21:1/108)

Re: Re: Prealphas
By: g00r00 to eggy on Tue Mar 03 2020 10:11 am

their ssl.cert in DATA folder but that remains to be confirmed. And its also possible this will break compatibility with Synchronet).

Have we worked out what the issue is?

I can certainly poll mystic systems with binkps and from my view of the world, it is successful.

They just cant poll me... (I believe)
...deon


... Who is General Failure, and why is he reading my disk?
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Have we worked out what the issue is?

As of now I don't know any issues with Mystic. Are you using the latest release and are the system you're connecting with?

--- Mystic BBS v1.12 A46 2020/03/02 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 02 Mar 2020 at 09:06p, Avon pondered and said...

20:59:59 Poll BINKP node via address lookup: 21:3/100
20:59:59 1-Polling 21:3/100 on slot 1 via BINKP
20:59:59 1-Connecting to alterant.leenooks.net on port 24556
20:59:59 1-Connected by IPV4 to 101.186.5.106
21:00:31 1-Data frame timeout
21:00:31 1-Connection lost
21:00:31 1-Authorization failed
21:00:32 Polled 1 systems

OK progress tonight... just tested the latest build from g00r00 and set BinkP Hostname to your domain:24556 and tried a poll from 1/100 which I have just updated.

20:08:29 Poll BINKP node via address lookup: 21:3/100
20:08:29 1-Polling 21:3/100 on slot 1 via BINKP
20:08:29 1-Connecting to alterant.leenooks.net on port 24556
20:08:30 1-Connected by IPV4 SSL to 101.186.5.106
20:08:30 1-System W7-1-1
20:08:30 1-SysOp alterego
20:08:30 1-Location Parkdale VIC
20:08:30 1-Info NDL 115200,TCP,BINKP
20:08:30 1-Info TIME Tue Mar 03 2020 18:08:35 GMT+1100 (AUS Eastern Daylight 20:08:30 1-Mailer BinkIT/2.28,JSBinkP/1.122,sbbs3.17c/Win32 binkp/1.1
20:08:30 1-Session ended (0 sent, 0 rcvd, 0 skip)
20:08:31 Polled 1 systems

So success there. I am now working on NET 3 to update and will test/report on that shortly.

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

If you want to use SSL with BINKP you will need to upgrade to the latest A46 prealpha (and there is potential that everyone will need to delete their ssl.cert in DATA folder but that remains to be confirmed. And its also possible this will break compatibility with Synchronet).

I'm getting ahead of myself but I have a cert from letsyncrypt for my BBS's website. Would it be possible at some point to configure Mystic's BINKPS to present my official/signed cert?

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: monterey bbs (21:1/168)

Re: Re: Prealphas
By: g00r00 to alter ego on Tue Mar 03 2020 01:38 pm

As of now I don't know any issues with Mystic. Are you using the latest release and are the system you're connecting with?

Yes and yes.

I was under the impression that Avon gave you some details and it seemed to be port issues. IE: When trying to connect to a "non standard" (in this case not 24553), MIS was doing unusual things. I havent really been following it closely, so things may have progressed since then.

But it is unusual that I can poll Mystic ok, but it cannot poll me on a non-standard port.

(Other systems can poll me fine - Al is using binkd with openssl in front.) ...deon


... Variables won`t; constants aren`t.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

I was under the impression that Avon gave you some details and it seemed to be port issues. IE: When trying to connect to a "non standard" (in
this case not 24553), MIS was doing unusual things. I havent really been

Yes that was fixed in the same 30 minute or so window that we were testing. I use a custom port set on my setup here to connect to Avon and my test network locally uses non-standar SSL ports. All are working.

Thats why I am asking if you're absolutely sure you have the latest version. If you don't, the exact problem you're describing happens. If you do, it shouldn't.

I'll reupload it just in case so we can make sure we're on the same page, and once everyone has the March 4th version we can go from there.

--- Mystic BBS v1.12 A46 2020/03/04 (Windows/64)
* Origin: Sector 7 (21:1/108)

I am updating the prealphas with a couple minor features and fixes for
Windows and Linux. Should be available in about 5 minutes.

--- Mystic BBS v1.12 A46 2020/03/07 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 07 Mar 2020 at 07:51p, g00r00 pondered and said...

I am updating the prealphas with a couple minor features and fixes for Windows and Linux. Should be available in about 5 minutes.

Thank you. I have updated 1/100 and 1/101 and will work to do the same with 2/100 and 4/100 over the coming hours

[snip]

+ Users now have a new flag that when set to Yes will always log them in as
invisible, bypassing the login as invisisble prompt when set to Yes.

[snip]

Thanks for this. It's a real time saver.

[snip]

! Fixed a bug with BINKP where Mystic could send a 0 byte length data frame
if a file size was exactly evenly divisible by the buffer size.

[snip]

Hopefully that may solve the issue the HUBs have been experiencing?

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

! Fixed a bug with BINKP where Mystic could send a 0 byte length data frame if a file size was exactly evenly divisible by the buffer size.

[snip]

Hopefully that may solve the issue the HUBs have been experiencing?

I think if this happened it would have been very rare and some mailers may not even have worried about a 0 byte data frame anyway (not sure about that it very well could have totally blew them up too). So my thoughts are that it won't fix the random quirkiness but at the very least its an improvement in some very rare circumstance. Or maybe it wasn't as rare as I expect, and it does who knows ;)

As I mentioned in another mail, at least some of the errors looked to be at fault of a non-Mystic mailer that was choking when Mystic sends its EOB before a GOT frame (which is fine, but it looked like the mailer thought the session should end at that point and was showing an error)

So it seems like there could be a series of different issues. I have added more detailed poll.txt and it will also create ssl.txt if it gets an SSL read error. But on that note, I haven't had any issues with the latest build (yet).

--- Mystic BBS v1.12 A46 2020/03/07 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 08 Mar 2020 at 07:53a, g00r00 pondered and said...

So it seems like there could be a series of different issues. I have added more detailed poll.txt and it will also create ssl.txt if it gets
an SSL read error. But on that note, I haven't had any issues with the latest build (yet).

I'm picking you must have updated the build again today then, as I am not seeing any ssl.txt logging in the one I applied this morning (my time) I'll
try to update things later and once on the same build I'm thinking perhaps
just setting up SSL polling between NET 1 to NET 2 and NET 1 to NET 3 but
leave NET 2 and NET 3 polling NET 1 as is.. I know NET2 is polling using std BinkP and Deon has NET 3 polling NET 1 using SSL :)

[snip]

+ 2020.03.08 14:33:26 BINKP > Connect on slot 1/25 SSL (2001:8003:4C06:5700:5863:4586:2DEC:493B)
+ 2020.03.08 14:33:26 BINKP 1-HostName Unknown
+ 2020.03.08 14:33:26 BINKP 1-Country Unknown (-)
+ 2020.03.08 14:33:26 BINKP 1-Unsecure True
+ 2020.03.08 14:33:26 BINKP 1-ForceMD5 False
+ 2020.03.08 14:33:26 BINKP 1-Rename 0
+ 2020.03.08 14:33:27 BINKP 1-System W7-1-1
+ 2020.03.08 14:33:27 BINKP 1-SysOp alterego
+ 2020.03.08 14:33:27 BINKP 1-Location Parkdale VIC
+ 2020.03.08 14:33:27 BINKP 1-Info NDL 115200,TCP,BINKP
+ 2020.03.08 14:33:27 BINKP 1-Info TIME Sun Mar 08 2020 12:33:39 GMT+1100
(AUS Eastern Daylight Time)
+ 2020.03.08 14:33:27 BINKP 1-Mailer
BinkIT/2.28,JSBinkP/1.122,sbbs3.17c/Win32 binkp/1.1
+ 2020.03.08 14:33:27 BINKP 1-Authenticating 21:3/100@fsxnet by CRAM-MD5
+ 2020.03.08 14:33:27 BINKP 1-Node is busy processing mail
+ 2020.03.08 14:33:27 BINKP 1-Queued 0 files for 21:3/100@fsxnet
+ 2020.03.08 14:33:27 BINKP 1-Receiving: 5e644b6c.pkt (698 bytes)
+ 2020.03.08 14:33:27 BINKP 1-Session ended (0 sent, 1 rcvd, 0 skip)
+ 2020.03.08 14:33:28 EVENT Res: 0

[snip]

Then we can start to look at what's happening

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

I'm picking you must have updated the build again today then, as I am not seeing any ssl.txt logging in the one I applied this morning (my time)

That should be because you haven't had any SSL read errors. :)

I did not update it again.

--- Mystic BBS v1.12 A46 2020/03/07 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 08 Mar 2020 at 11:25a, g00r00 pondered and said...

That should be because you haven't had any SSL read errors. :)

I did not update it again.

aha, OK thanks... righto I'll start some tests and let you know if something occurs.

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

Updated the prealphas. Very minor changes in this one.

--- Mystic BBS v1.12 A46 2020/03/12 (Windows/64)
* Origin: Sector 7 (21:1/108)

Updated the prealphas. Very minor changes in this one.

Is there a ARM/Pi prealpha version? Didn't see it in the dir...

|08.|07..|15.. |11Alpha |07- |11Card & Claw BBS

--- Mystic BBS v1.12 A46 2020/03/07 (Linux/64)
* Origin: Card & Claw BBS | Analog Gaming: Board Games, RPGs (21:4/158)

Updated the prealphas. Very minor changes in this one.

Is there a ARM/Pi prealpha version? Didn't see it in the dir...

No I don't release ARM prealphas often, mostly because I often don't have access to my Pi to compile it and it takes some time. I won't have access to my Pi probably for another month..

--- Mystic BBS v1.12 A46 2020/03/12 (Windows/64)
* Origin: Sector 7 (21:1/108)

Hello g00r00!

On 12 Mar 2020, g00r00 said the following...

Updated the prealphas. Very minor changes in this one.

Thanks!

I noticed there is a prompts.bak in the data directory (when performing a
fresh install) -- is that one needed for anything? =)

I also managed to get "Error 0" when polling HUB 1 two times in close succession:

--------------------- POLL v1.12 A46 2020/03/09 Thu, Mar 12 2020 (loglevel 2) + 2020.03.12 06:14:08 Sending to all nodes of session type ALL
+ 2020.03.12 06:14:08 Queued 1 files (666 bytes) for 21:1/100
+ 2020.03.12 06:14:08 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.12 06:14:08 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.12 06:14:10 1-Connected by IPV4 SSL to 219.89.83.33
+ 2020.03.12 06:14:10 1-System fsxHUB Risa [NET1]
+ 2020.03.12 06:14:10 1-SysOp Avon
+ 2020.03.12 06:14:10 1-Info TIME Thu, 12 Mar 2020 18:14:04 +1300
+ 2020.03.12 06:14:10 1-Mailer Mystic/1.12A46 binkp/1.0
+ 2020.03.12 06:14:10 1-Info BUILD 2020/03/09 16:40:24 Windows/32
+ 2020.03.12 06:14:11 1-Sending: 00000066.th0 (666 bytes)
+ 2020.03.12 06:14:11 1-Remote Queue: 0 files 0 bytes
+ 2020.03.12 06:14:12 1-Session ended (1 sent, 0 rcvd, 0 skip)
+ 2020.03.12 06:14:13 Polled 1 systems

--------------------- POLL v1.12 A46 2020/03/11 Thu, Mar 12 2020 (loglevel 2) + 2020.03.12 06:25:05 Polling all nodes of session type ALL
+ 2020.03.12 06:25:05 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.12 06:25:05 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.12 06:25:07 1-Connected by IPV4 SSL to 219.89.83.33
+ 2020.03.12 06:25:07 1-System fsxHUB Risa [NET1]
+ 2020.03.12 06:25:07 1-SysOp Avon
+ 2020.03.12 06:25:07 1-Info TIME Thu, 12 Mar 2020 18:25:01 +1300
+ 2020.03.12 06:25:07 1-Mailer Mystic/1.12A46 binkp/1.0
+ 2020.03.12 06:25:07 1-Info BUILD 2020/03/09 16:40:24 Windows/32
+ 2020.03.12 06:25:09 1-Remote Queue: 0 files 0 bytes
+ 2020.03.12 06:25:09 1-Error 0

Creating another poll.now semaphore made "./mis poll forced" run, but nothing happened (it just hung there) -- had to restart MIS to get things working again:

--------------------- Mystic v1.12 A46 2020/03/11 Thu, Mar 12 2020 (loglevel 2)
+ 2020.03.12 06:24:34 MANAGER Starting event system
+ 2020.03.12 06:24:34 MANAGER Starting 4 server(s)
+ 2020.03.12 06:24:34 TELNET Listening on IPV4 port 50023 using interface "0.0.0.0"
+ 2020.03.12 06:24:34 TELNET Listening on IPV6 port 50023 using interface
"::"
+ 2020.03.12 06:24:34 MGETTY Listening on IPV4 port 50123 using interface "127.0.0.1"
+ 2020.03.12 06:24:34 SSH Listening on IPV4 port 50022 using interface "0.0.0.0"
+ 2020.03.12 06:24:34 SSH Listening on IPV6 port 50022 using interface "::"
+ 2020.03.12 06:24:34 MANAGER Starting servers in DAEMON mode
+ 2020.03.12 06:24:34 BINKP Listening on IPV4 port 24554 using interface "0.0.0.0"
+ 2020.03.12 06:24:34 MGETTY Listening on IPV6 port 50123 using interface "::1"
+ 2020.03.12 06:24:34 BINKP Listening on IPV4 SSL port 24553 using interface "0.0.0.0"
+ 2020.03.12 06:24:34 BINKP Listening on IPV6 port 24554 using interface "::" + 2020.03.12 06:24:34 BINKP Listening on IPV6 SSL port 24553 using interface "::"
+ 2020.03.12 06:24:35 SENDMAIL Relaying mail to 127.0.0.1
+ 2020.03.12 06:24:35 EVENT Starting 5 event(s)
+ 2020.03.12 06:25:05 EVENT Removing: /mnt/bbs/mystic/semaphore/poll.now
+ 2020.03.12 06:25:05 EVENT Running event: CUSTOM: Poll EchoMail/NetMail
+ 2020.03.12 06:25:05 EVENT Cmd: ./mis poll forced
+ 2020.03.12 06:27:26 MANAGER Received shutdown event
+ 2020.03.12 06:27:26 MANAGER Shutdown signal received from OS
+ 2020.03.12 06:27:26 MANAGER Shutdown: EVENT
+ 2020.03.12 06:27:26 MANAGER Shutdown: SENDMAIL
+ 2020.03.12 06:27:26 MANAGER Shutdown: TELNET
+ 2020.03.12 06:27:26 MANAGER Shutdown: MGETTY
+ 2020.03.12 06:27:26 MANAGER Shutdown: SSH
+ 2020.03.12 06:27:26 MANAGER Shutdown: BINKP
+ 2020.03.12 06:27:26 MANAGER Waiting for servers to stop (up to 30 seconds)
+ 2020.03.12 06:27:26 EVENT Res: 0
+ 2020.03.12 06:27:26 SENDMAIL Shutting down
+ 2020.03.12 06:27:27 EVENT Event system stopped
+ 2020.03.12 06:27:27 MANAGER Shutdown complete

Not sure what could be the cause of this. Connection blocking in BINKP at HUB
1 because I was too quick? Different Mystic version there? But it worked just fine polling two times in succession after restarting MIS...

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/03/11 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

On 12 Mar 2020 at 04:22a, g00r00 pondered and said...

Updated the prealphas. Very minor changes in this one.

all three HUBs running Mystic are now on that 'latest' build.

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

Thanks!

I noticed there is a prompts.bak in the data directory (when performing a fresh install) -- is that one needed for anything? =)

No, I just did that just in case there was some issue that went undetected
with all the new theme stuff, so that people wouldn't lose their custom prompts. There is no need to keep it.

I also managed to get "Error 0" when polling HUB 1 two times in close

Thanks I haven't seen or heard about that before but I will poke around and see what might have caused that message. An error 0 typically means no error so its odd that it was triggered, and for that message to show a pretty serious issue had to occur.

If you see sometihng like this happen again please let me know. I did relax some of the status drawing functions in the latest release and maybe that change could have caused a problem so I will just put it back to where it was to be safe. Maybe that will fix whatever happened here, but its hard to say.

Unfortuately I just removed the extra logging that was going on too, and that would have better pinpointed what was going on at the time of failure.

--- Mystic BBS v1.12 A46 2020/03/12 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 12 Mar 2020 at 04:22a, g00r00 pondered and said...

Updated the prealphas. Very minor changes in this one.

all three HUBs running Mystic are now on that 'latest' build.

Thanks this should have the unlink feature in the NodeTracker that you wanted.

--- Mystic BBS v1.12 A46 2020/03/12 (Windows/64)
* Origin: Sector 7 (21:1/108)

Hello g00r00!

Thank you for your reply!

On 12 Mar 2020, g00r00 said the following...

If you see sometihng like this happen again please let me know. I did

Will do!

(No new occurrences during the day here.)

Best regards
Zip

--- Mystic BBS v1.12 A46 2020/03/11 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Updating the prealphas again because I failed to include the upgrade instructions in the first build yesterday (and MIS was actually starting up instead of printing out an error message when the upgrade wasn't performed)

--- Mystic BBS v1.12 A46 2020/03/15 (Windows/64)
* Origin: Sector 7 (21:1/108)

Awesome, thanks g00r00! I hate to add another one to the list, but wo it be possible to remove the SMTP username/password character limits? auto-generates some really long username and password combos for thei SMTP services.

Yeah we can get that expanded. Its probably limited to what it is
because I didn't want to change the data file formats. Worst case it
will have to wait until A45 since I already sent out the A44 upgrade but maybe I can figure something out.

I'm not sure if this is always consistent with AWS but in my case the
username is 20 characters and the password is 44 characters long (brutally
long I know) :(

Thanks again!
Mike

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

Awesome, thanks g00r00! I hate to add another one to the list, b it be possible to remove the SMTP username/password character li auto-generates some really long username and password combos for SMTP services.

Yeah we can get that expanded. Its probably limited to what it is because I didn't want to change the data file formats. Worst case it will have to wait until A45 since I already sent out the A44 upgrade maybe I can figure something out.

I'm not sure if this is always consistent with AWS but in my case the username is 20 characters and the password is 44 characters long
(brutally long I know) :(

Yeah, I wanted to use SendGrid for SMTP, but they use very long API keys,
more characters than Mystic accepts in the PW field.

|08.|07..|15.. |05Alpha |07- |13Card & Claw BBS |07- |08Berkeley, CA USA

--- Mystic BBS v1.12 A46 2020/03/16 (Linux/64)
* Origin: Card and Claw BBS | cardandclaw.com:8888 (21:4/158)