Hello everybody!
I am having an Mystic to Mystic connection issue with another system.
When I poll his Mystic system I get:
Mailer Mystic/1.12A31 binkp/1.0
Error receiving data (Msg= Size=0/256)
Connection lost
Authorization failed
It is my understanding that we are both using the same session
password. I haven't run into this particular error before so...
Raspberry Pi. When polling him moments ago I get:
Mailer Mystic/1.12A31 binkp/1.0 Authorization failed
I no longer get the "Error receiving data (Msg= Size=0/256)" I have
tried polling him from my other systems here BBBS, SBBS,
and a standalone install of BinkD and get similar results.
Anyone have any thoughts?
to seemingly no avail. He is running a slightly older version of Mystic
on a Raspberry Pi. He has stated that he has issues with the new Mystic version on a Raspberry Pi.
Will do. He setup BinkD and I can connect to him fine. I have a couple Raspberry
Pi3's but I haven't put a mailer/bbs on them so far. RB's are mainly used with Ham Radios and digital coms.
If you can connect to his BinkD setup then it is more than likely the fact he has you in his blacklist.txt file. Let me know if that fixes the issue.
On 07-02-19 15:38, Deon George wrote to Jeff Smith <=-
On 01 Jul 2019, Jeff Smith said the following...
to seemingly no avail. He is running a slightly older version of Mystic
on a Raspberry Pi. He has stated that he has issues with the new Mystic version on a Raspberry Pi.
I run the latest Mystic on a Pi with no troubles :)
Raspberry Pi. When polling him moments ago I get:
Mailer Mystic/1.12A31 binkp/1.0 Authorization failed
I no longer get the "Error receiving data (Msg= Size=0/256)" I
have tried polling him from my other systems here BBBS, SBBS, and
a standalone install of BinkD and get similar results. Anyone
have any thoughts?
Have him make sure your ip address isn't listed in his blacklist.txt
file. I had a similar issue with one of my downlinks a while back and
that was the issue. Have him put your ip in his whitelist.txt to make
sure you don't end up back in the blacklist.txt.
Will do. He setup BinkD and I can connect to him fine. I have a couple Raspberry
Pi3's but I haven't put a mailer/bbs on them so far. RB's are mainly
used with Ham Radios and digital coms.
Can't say that I can do that. :-( As he decided to drop Mystic due to the problems he was having. He tells me that he has switched over to BinkD, Husky, and Golded. An arrangement that I have used in the past for
years. The problem I was having (Connecting) has been fixed. I offered
to help him work out his issues with Mystic but alas the decision is his.
If you can connect to his BinkD setup then it is more than likely the f he has you in his blacklist.txt file. Let me know if that fixes the is
Can't say that I can do that. :-( As he decided to drop Mystic due to the problems he was having. He tells me that he has switched over to BinkD, Husky, and Golded. An arrangement that I have used in the past for
years. The problem I was having (Connecting) has been fixed. I offered
to help him work out his issues with Mystic but alas the decision is his.
Mystic is a great all in one solution for sysops, but still has it's quirks here and there, but it is alpha software, it is to be expected.
On 07-03-19 19:55, Paul Hayton wrote to Netsurge <=-
fsxNet has been using Mystic for all HUB duties since day one and I
have to say it's been great.
On 07-03-19 01:32, Jeff Smith wrote to Netsurge <=-
Hello Netsurge,
Mystic is a great all in one solution for sysops, but still has it's quirks here and there, but it is alpha software, it is to be expected.
There have been a couple instances between Mystic and other software
but I am not pointing only at Mystic as it often is a mutual situation.
I as well like Mystic because it designed or at least turned out to be "All In One" package. The node that Mystic occupies here only really
needs a mail mover. So BinkD, Husky, and Golded would fill the bill
fine. But as I stated, I like the integration that exists with Mystic.
Mystic is a great all in one solution for sysops, but still has it's quirks here and there, but it is alpha software, it is to be expected.
When I started SciNet back up I had to move the mail processing duties from Mystic to BinkD and some of the husky software. I still run Mystic because I love it, it just don't do any of the mail processing.
On 02 Jul 2019 at 04:49p, Jeff Smith pondered and said...
Can't say that I can do that. :-( As he decided to drop Mystic due to the
problems he was having. He tells me that he has switched over to BinkD,
Husky, and Golded. An arrangement that I have used in the past for
years. The problem I was having (Connecting) has been fixed. I offered
to help him work out his issues with Mystic but alas the decision is his.
Jeff whitelist and blacklist may have been a factor but another gotcha can be a typo in the domain name for the echonode setting. So if his or your domain name was mis-spelt then it can also cause those kinds of issues.
I'd also keep any password to no more than 8 chars and all uppercase..
Jeff whitelist and blacklist may have been a factor but another gotcha c a typo in the domain name for the echonode setting. So if his or your do name was mis-spelt then it can also cause those kinds of issues.
I can't actually say as he didn't respond to my blacklist query. But the domain that I was polling did match the domain listed in the nodelist
and did resolve to the correct IP. The connection could be established
but would be dropped due to a authentication failure. His logs showed
that he was using my correct domain name also. Based on what he stated this was just "The last straw". He didn't elaborate on what other issues that he had been having.
I have a spare Raspberry Pi3 B that I might install Mystic on just to do some testing.
The passwords used were comprised of eight alpha numerical characters
with all caps.
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 81:38:49 |
| Calls: | 2,068 |
| Calls today: | 1 |
| Files: | 11,134 |
| Messages: | 946,634 |