1. Forum
  2. FidoNet
  3. MYSTIC

  • Mystic Connection Issue?

    From Jeff Smith@1:14/5 to All on Monday, July 01, 2019 23:43:24
    Hello everybody!

    30 Jun 19 15:04, I wrote to all: #

    #


    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...

    We have tried the same session password and no paswword. Compared node settings, tried with MD and session security enabled and disabled. All 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. 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?

    Jeff


    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Region 14 IP Server - ftn.region14.org (1:14/5)
  • From Jeff Smith@1:14/6 to Netsurge on Wednesday, July 03, 2019 01:32:52
    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.

    Jeff
    --- SBBSecho 3.06-Linux
    * Origin: The Twisted Balloon - Anoka, MN (1:14/6)
  • From Paul Hayton@3:770/100 to Netsurge on Wednesday, July 03, 2019 19:55:54
    On 02 Jul 2019 at 10:26p, Netsurge pondered and said...

    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.

    It's been in alpha more than it's been in full final release in recent years. So I do agree your mileage may vary according to expectations an op has when using it. I don't mind that personally as I think there is a lot of enjoyment to be had playing with the bleeding edge at times. I'm understanding that it may not be everyones cup of tea though.

    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.

    fsxNet has been using Mystic for all HUB duties since day one and I have to
    say it's been great.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Tony Langdon@3:633/410 to Jeff Smith on Wednesday, July 03, 2019 19:03:00
    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.

    Similar thing happened with my Mystic installation. It ended up becoming a mail hub, and works well for me. I could theoretically run it using BinkD and Husky, but Mystic is doing the job. Have had the occasional quirk with some software, but usually get it sorted with the affected node. Only had one that had to resort to using my QWK hub, IIRC..


    ... Be alert! The country needs more lerts.
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Paul Hayton on Wednesday, July 03, 2019 19:04:00
    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.

    Same with VKRadio, where the FTN hub runs Mystic.


    ... Real Programmers Practice Safe HEX
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Jeff Smith@1:282/1031 to Paul Hayton on Tuesday, July 02, 2019 18:43:00
    Hello Paul,

    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 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.

    I'd also keep any password to no more than 8 chars and all uppercase..

    The passwords used were comprised of eight alpha numerical characters with all
    caps.


    Jeff

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: Fidoneet: The Ouija Board - Anoka, MN -bbs.ouijabrd.net (1:282/1031)
  • From Jeff Smith@1:282/1031 to Paul Hayton on Tuesday, July 09, 2019 06:04:24
    Hello Paul,

    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...

    Umm... You misspelled Fidonet there. :-)

    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 :)

    Thanks Paul, will do. I'm the type that likes to know why things happen the way
    that they do.

    He has switched over to BinkD and we now connect fine.

    Jeff

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: Fidoneet: The Ouija Board - Anoka, MN -bbs.ouijabrd.net (1:282/1031)