Awesome, thanks g00r00! I hate to add another one to the list, but would it be possible to remove the SMTP username/password character limits? AWS auto-generates some really long username and password combos for their SMTP services.
To upgrade from previous prealpha just replace all your .exe files yo can do that with "install replace c:\mystic\"
Just a heads up for the win32 test build I have been starting to update this feature does not work as directed and just fires up the main
install UI menu.
Mystic BBS Installation Utility Version 1.10 A53
Copyright (C) 1997-2014 By James Coyle. All Rights Reserved.
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 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 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 ??
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
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.
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.
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 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.
Thanks :)
Getting late here but will try to update and test before eyeballs fall
out
I can connect, but I get an authorization failure:what I see internally when I force the BinkP Hostname to include a port number.
I have a feeling g00r00 may spot something soon.
I removed :24553 from your hostname in my echomail node configuratoin
and now it seems to poll you OK over SSL:
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
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
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!
I think thats just a timing thing. We are swapping versions as you're testing this stuff :)
No joy... but it may be your build needs an update to..
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 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!
Deon and Al - yep to more tests, will look to do so tomorrow.
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'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.
I have tried both of these. It connects but fails for some
reason, something about the certificates.
Maybe its the TLS < v1.2 situation?
I have tried both of these. It connects but fails for some reason, something about the certificates.
Maybe its the TLS < v1.2 situation?
So, I can't poll Synchronet or Mystic presently with binkd. Can you try polling
here?
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...
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.
OK, hub 3 is on alterant.leenooks.net:24556 (synchronet windows), and my
Anybody who wants to test binkps is welcome to.
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.
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
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
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'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?
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?
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
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).
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?
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
I am updating the prealphas with a couple minor features and fixes for Windows and Linux. Should be available in about 5 minutes.
! 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?
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)
That should be because you haven't had any SSL read errors. :)
I did not update it again.
Updated the prealphas. Very minor changes in this one.
Updated the prealphas. Very minor changes in this one.
Is there a ARM/Pi prealpha version? Didn't see it in the dir...
Updated the prealphas. Very minor changes in this one.
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
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.
If you see sometihng like this happen again please let me know. I did
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.
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) :(
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 101 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 00:38:10 |
| Calls: | 3,456 |
| Calls today: | 4 |
| Files: | 8,461 |
| Messages: | 336,008 |
| Posted today: | 6 |