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...
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.
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 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.
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 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..
On 02 Jul 2019 at 06:43p, Jeff Smith pondered and said...
Based on what he stated this was just "The last straw". He didn't elaborate >> on what other issues that he had been having.
Yeah the domain name is certainly one thing to check but the stated domain name in the echomail node setup is always worth a check... i've seen a number of times where folks mis-spell that and so incoming and outgoing connects fail when you see 3:770/100@fionet for example...
I have a spare Raspberry Pi3 B that I might install Mystic on just to do
some testing.
OK lemme know if you need anything or want to do some stuff to test things.. happy to help :)
Sysop: | Zazz |
---|---|
Location: | Mesquite, Tx |
Users: | 7 |
Nodes: | 4 (0 / 4) |
Uptime: | 15:02:21 |
Calls: | 157 |
Files: | 2,092 |
Messages: | 144,266 |