TID: Mystic BBS 1.12 A48   
   MSGID: 3:770/100 f0541f0a   
   REPLY: 4:801/188 e120bf71   
   TZUTC: 1200   
   On 22 Apr 2024 at 01:26a, Flavio Bessa pondered and said...   
       
    FB> On 13 Apr 2024, Paul Hayton said the following...   
    FB>     
    FB>  PH> Can you give me an example of what's happening now and what you would   
    FB>  PH> like to happen?   
    FB>    
    FB>     All right, my node is 4:801/188 and I connect to the hub at 4:80/1.    
      
   OK   
      
    FB>     4:80/1 has a direct link to 2:292/854. Route Info at Hub states that   
    FB> all netmail towards 2:* should go through there.    
      
   So confirming Route Info for the echomail node 2:292/854 defined at 4:80/1 has   
   2:*  ?? Just checking I understand this.   
      
   Also does 4:80/1 have any other echomail nodes with Zone 2 systems that are   
   defined and active or is 2:292/854 the only one?   
      
    FB>     4:801/188 has the Crash Netmail flag on at the Configuration part.    
      
   Understood, so this just means any netmail you send is sent quickly off to   
   it's next hop.   
      
    FB>     If I send a message to Bjorn Felten, 2:203/0, despite my nodelist is   
    FB> updated inside Mystic, netmail is routed through 4:80/1 -> 2:292/854 ->   
    FB> 2:203/0 instead of going directly to 2:203/0....    
      
   this sounds correct.   
      
   I am assuming your system routes all netmail to your HUB 4:80/1  ?   
      
   Do you have any other echomail nodes setup with systems in Fidonet on your BBS?   
      
   Based on the rule 2:* you have stated at 4:80/1 then Mystic would look to that   
   to route all Zone 2 netmail via 2:292/854  ...so that behavior is also   
   expected at the HUB system.   
      
   If you are wanting to send netmail direct to Bjorn at 2:203/0 then I'd suggest   
   establish a direct link with him and add his system as an echomail node to   
   your BBS.   
      
   Mystic will check to see if you have a direct connection with a system you are   
   sending netmail to and if it find that, it will route the netmail directly to   
   that echomail node and not look at the Route Info line you may (I am assuming   
   here) have set up for your HUB system ... presume something like a Route Info   
   statement like 1:* 2:* 3:* 4:*   or similar?   
      
   Best, Paul   
      
   Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going'   
   avon[at]bbs.nz | bbs.nz | fsxnet.nz    
      
   --- Mystic BBS v1.12 A48 (Linux/64)   
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)   
   SEEN-BY: 15/0 90/1 103/705 105/81 106/201 124/5016 128/260 129/305   
   SEEN-BY: 135/220 225 153/757 7715 154/10 30 203/0 218/700 840 220/70   
   SEEN-BY: 221/0 226/17 30 100 227/114 229/110 111 112 113 206 275 307   
   SEEN-BY: 229/317 400 426 428 470 550 664 700 240/1120 5832 266/512   
   SEEN-BY: 267/800 280/464 5003 282/1038 291/111 292/854 8125 301/1   
   SEEN-BY: 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58   
   SEEN-BY: 460/256 1124 467/888 633/280 712/848 770/1 3 100 340 772/210   
   SEEN-BY: 772/220 230 5020/400 5054/30 5075/35   
   PATH: 770/100 1 280/464 460/58 229/426