REPLY: 1:153/757@fidonet 5f0ababf
MSGID: 1:320/319 5f91a84f
CHRS: CP437 2
TZUTC: -0400
TID: MBSE-FIDO 1.0.7.18 (GNU/Linux-x86_64)
Hello Alan!

19 Oct 20 15:41, you wrote to Sean Dennis:

 AI> Thanks for looking into it. I will create a fresh .pkt from BBBS to
 AI> another point I have set up here and pass it through MBSE so you can
 AI> see the input .pkt and also the output .pkt that MBSE creates.

 AI> I'll attach those directly to your node in a zip file shortly.

Copy me on this also.  I looked at your packet briefly, but it would help to 
see the packet that Mystic created when sending the message back to the MBSE 
system.  My initial impression is that Mystic isn't detecting that the message 
is for it, and is thus sending it back to your MBSE system.  MBSE sees that it 
is for the point system, and sends it back there.

Andrew

--- GoldED+/LNX 1.1.5-b20180707
 * Origin: MBSE BBS Development (1:320/319)
SEEN-BY: 1/123 18/200 90/1 120/340 123/131 226/30 227/114 229/101
SEEN-BY: 229/275 424 426 452 550 664 1016 240/5832 249/206 317 400
SEEN-BY: 292/854 317/3 322/757 342/200 633/280
PATH: 320/319 219 221/1 280/464 229/101 426