TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 12920cb4   
   REPLY: 3:770/100 6975df88   
   TZUTC: -0500   
    PH> Can I check routing logic with you?   
      
   Yes the logic is to check if there is a direct address configured and route to   
   them if so.  If there isn't a direct entry for that address, then it will look   
   through and try to find the first routed match.   
      
    PH> I know most routing tables work on the last rule that matches applies,   
    PH> and clearly there's a defined direct route with 3/102 defined in 1/100   
    PH> HUB .. but would there be a way to override that behavior to create a   
    PH> forced rule to direct 3/102 netmail to 3/100 instead?   
      
   I just finished adding a "Bypass Direct" flag for echomail nodes which will   
   disable direct routing for that node, causing it to fall back to the netmail   
   routing policy.  Sounds like that should do exactly what you want!  Its in the   
   latest prealpha for A47 as of today (my today (Jan 30), not the today of time   
   travelers such as yourself).   
      
   Other "forks" of logic after that if you wanted them could be done by using   
   the "NOT" function of the routing   
      
   --- Mystic BBS v1.12 A47 2021/01/29 (Windows/64)   
    * Origin: Sector 7 | Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 90/1 103/705 105/81 120/340 457 123/10 131 124/5016   
   SEEN-BY: 129/215 305 154/10 30 40 50 700 203/0 220/80 90 221/0 1 6   
   SEEN-BY: 226/30 227/114 201 702 229/101 310 424 426 452 550 664 981   
   SEEN-BY: 229/1016 1017 240/5832 249/206 307 317 400 261/38 280/464   
   SEEN-BY: 280/5003 292/854 8125 317/3 322/757 335/364 342/200 396/45   
   SEEN-BY: 633/280 770/1 2452/250 3634/12   
   PATH: 129/215 154/10 280/464 292/854 229/426