REPLY: 2:250/1@fidonet 67c22176   
   MSGID: 2:250/1@fidonet 67c33bec   
   CHRS: UTF-8 2   
   TZUTC: 0000   
   TID: MBSE-FIDO 1.1.0 (Linux-x86_64)   
      
   Hello Andrew!   
      
   28 Feb 25 20:43, I wrote to you:   
      
   I have now added Sean Rima to the (so far) Z2DAILY nodelist as it was sent in   
   too late for entry to the main NODELIST system, but that will happen for next   
   Friday's one.   
      
   So Sean has added the AKA 250/101 and sent in requests for linking in to some   
   ECHO areas and it seams to be working - no real surprises there.   
      
   I do not follow the logic being used in mbse here as I am not the only one   
   running more that one net as there are a few around both in the USA and    
   Europe.   
      
   That said Michael may not have thought of that being a possibility when coding   
   the notify and areamgr / filemgr routines.   
      
   To my mind have the primary AKA in my case 250/1 at position 1 in the AKA    
   lists   
   should not be in the way of processing these requests as it would still be   
   valid for all connected nodes, yes ?   
      
   Clearly the fact that I have an AKA in the net the same as the subject node is   
   where mbse is confusing it but do not see why !   
      
      
   Ideas ?   
      
   Vincent   
      
      
    > Hello Andrew!   
      
    > 15 Feb 25 15:29, I wrote to you:   
      
      
    > As a follow on from previous msg regarding issues when using mbfido no   
    > on a secondary fido address at 2:263/1  where the infor sent is - well   
    > broken such as :   
      
    >  Dear Sean Rima:   
      
    >  The following is a flow report of all message areas   
      
    >  Group @G @J (@I)   
    >                                          P O S T E D         R E C E I   
    > V E D Message area                   Last week  Last month  Last week   
    > Last Month - ------------------------------ ----------   
    > ---------- ---------- ----------   
      
      
    > With the rest blank I suspect that it relates to the address of the   
    > node is not in 2:25 or 2:250.   
      
    > I am going to try and allocate a new node address 2:0/101 as an aka to   
    > 263/1 and see if that fixes it - just have to remember to route such   
    > to 2:263/1 though.   
      
    > Will advise.   
      
    > Vincent   
      
      
      
   Vincent   
      
      
   --- Mageia Linux v9 X64/Mbse v1.1.0/GoldED+/LNX 1.1.5-b20240309   
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)   
   SEEN-BY: 1/120 18/0 200 25/0 21 50/22 103/705 104/119 105/81 106/201   
   SEEN-BY: 123/0 25 180 755 3001 3002 124/5016 128/187 129/305 135/115   
   SEEN-BY: 153/757 7715 154/10 30 50 110 700 203/0 218/700 220/6 20   
   SEEN-BY: 220/90 221/0 6 222/2 226/18 30 44 50 227/114 229/110 114   
   SEEN-BY: 229/206 275 310 317 400 426 428 470 550 664 700 705 240/1120   
   SEEN-BY: 240/5832 250/0 1 2 3 4 5 7 8 11 13 14 15 263/0 266/512 275/1000   
   SEEN-BY: 280/464 5003 5006 291/111 292/854 8125 301/1 310/31 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 1321 770/1 902/26 2320/105 3634/0   
   SEEN-BY: 3634/12 27 57 58 60 119 5020/400 8912 5054/30 5075/35   
   PATH: 250/1 3634/12 154/10 280/464 460/58 229/426