https://gitlab.synchro.net/main/sbbs/-/commit/15b230af547ff5932c6073e5
Modified Files:
	src/sbbs3/sbbsecho.c
Log Message:
Rework NetMail routing logic to handle point destinations betterWith this commmit, the logic is now:If the NetMail destination is a point and there's no linked-node for it   and the boss node for this point is not one of our AKAs   then route to the boss node (no linked-node match needed)   if the boss node matches a linked-node with a route configuration   then route to that configured route destination (2-levels of routing   and thus 2 "Routing NetMail" msgs will be logged in this scenario)If the NetMail destination is a point and there is a linked-node for it   then the netmail will not be routed		unless that linked node has a route configurationNetMail destined for non-points are treated the same as before thiscommit.No change in the routing of echomail for points.I think this change fixes issue #520 which can be traced back to commit45ced2a3b for poindexter FORTRAN (REALITY), 2 years ago almost to theday, where that change added point->boss routing, but only if the bosshad a matching linked-node configuration (for both echomail andnetmail).This commit also re-thinks commit ffe69b43623d (for Alterego) whichwould not route a point netmail if any our local AKAs matched thedestination address, igorining the point value. I think what wasintended here (I coudln't locate the original enhancmenet request orissue), was to not route if a local AKA was the *boss* of the point.And with this commit, that's now how it now works.As before, "test results appreciated".
--- SBBSecho 3.20-Linux