On 05/06/16, Mark Hofmann pondered and said...
 
 MH> Editing the Mystic system to use the same password I am using for the
 MH> session password, works and fixes the issue.

Just a small correction on that bit... I ended up adding a packet password in
to your echonode setting - there was already a session password applied but
that was not enough as Mystic was seeing a packet password coming from your
end as well. Until I added the packet password Mystic was dropping the
packets at import time.

It kind of looks like you're perhaps setting a session password at your end
but instead this is being sent as a packet password - dunno? :)

At least for now it's all working between us :)

Best, Paul

--- Mystic BBS v1.12 A13 (Windows)