TID: Mystic BBS 1.12 A48   
   MSGID: 3:770/100 ae610343   
   REPLY: 4:801/188 0085b28d   
   TZUTC: 1200   
   On 22 Apr 2024 at 12:07p, Flavio Bessa pondered and said...   
       
    FB>  PH> Based on the rule 2:* you have stated at 4:80/1 then Mystic would loo   
    FB>  PH> to that to route all Zone 2 netmail via 2:292/854  ...so that behavio   
    FB>  PH> is also expected at the HUB system.   
    FB>    
    FB>  PH> Mystic will check to see if you have a direct connection with a syste   
    FB>  PH> you are sending netmail to and if it find that, it will route the   
    FB>  PH> netmail directly to that echomail node and not look at the Route Info   
    FB>  PH> line you may (I am assuming here) have set up for your HUB system ...   
    FB>  PH> presume something like a Route Info statement like 1:* 2:* 3:* 4:*      
    FB>  PH> similar?   
    FB>        
    FB>     But that is the point... If I have the CRASH flag enabled for   
    FB> Netmail, Mystic should (according to the FTSC specs) read the nodelist,   
    FB> find out the Binkp address for Bjorn's system, and issue an unsecured   
    FB> session towards 2:203/0. That is what the other mailers do, and that is   
    FB> why we have nodelists in the first place...    
      
   No. The CRASH flag won't in itself be enough for Mystic to do what you hope it   
   will do. Also note that just because you may have run the MergeNodelists   
   function in MUTIL this will only scan the nodelists you point to and build a   
   text file in the data directory of Mystic. This is in turn used by the   
   nodelist browser feature, but that feature is like looking up a phone book for   
   a number, nothing more.   
      
   It does not impact on how Mystic deals with netmail (g00r00 may care to jump   
   in when next active to confirm or update these thoughts ;))   
      
   Mystic has it's own logic as to how it will route netmail. Refer to   
   whatsnew.txt to see what this is. g00r00 has documented it there. Look for   
   'netmail routing' in that document and read this to understand the steps   
   Mystic takes.   
      
   If you are unhappy with the way Mystic acts, then it's best to post some   
   feedback to this echo and suggest what you think it could do dif   
   erently/better etc. and why... and then you will need to wait for the software   
   author to reply.   
      
   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