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)