Subj : Re: Possible bug
To   : Michael Pierce
From : g00r00
Date : Mon Sep 28 2020 09:42 pm

 MP> now for kicker..  even from node to node ie from 1:340/202 (mystic) to
 MP> 1:340/203 (sbbs) both latest any mail that is not direct gets an invalid
 MP> node address assigned to it (1:1/0) - this is very reminisent of the
 MP> sort of issues that were going on before

The default address (1:1/0) sounds like it could be related to the thing we're
talking about here so its probably a good idea to get that resolved.  If SBBS
gets an address from the origin line, then it'd probably end up with some
reasonable default like 1:1/0 if no address was there.

As far as the rest there are some many things that could be wrong there,
including if someone is using old versions or has an ill-configured netmail
route (also could be a bug too).  Not sure where to begin so I think making
sure the address is on the origin line is a good start.

I personally host a point system on SCINET, and they are able to send netmails
throughout when we tested it.  Netsurge confirmed all of the addressing in the
netmails produced from Mystic match the same when they are generated by HPT
(the Husky tosser) too.  This was several months ago though.

--- Mystic BBS v1.12 A47 2020/09/27 (Windows/64)
 * Origin: Sector 7 | Mystic WHQ (1:129/215)

.