Subj : Re: Mystic Connection Issue?
To   : Jeff Smith
From : Paul Hayton
Date : Tue Jul 09 2019 07:43 pm

On 02 Jul 2019 at 06:43p, Jeff Smith pondered and said...
 
 JS> > Jeff whitelist and blacklist may have been a factor but another gotcha c
 JS> > a typo in the domain name for the echonode setting. So if his or your do
 JS> > name was mis-spelt then it can also cause those kinds of issues.
 JS> 
 JS> I can't actually say as he didn't respond to my blacklist query. But the
 JS> domain that I was polling did match the domain listed in the nodelist
 JS> and did resolve to the correct IP. The connection could be established
 JS> but would be dropped due to a authentication failure. His logs showed
 JS> that he was using my correct domain name also. Based on what he stated
 JS> this was just "The last straw". He didn't elaborate on what other issues
 JS> 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...

 JS> I have a spare Raspberry Pi3 B that I might install Mystic on just to do
 JS> some testing.

OK lemme know if you need anything or want to do some stuff to test things..
happy to help :)

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

all good

Best, Paul

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

.