@MSGID: <536AD76B.33580.sync_sys@vert.synchro.net>   
   @REPLY: <536A7501.33578.sync_sys@vert.synchro.net>   
    BM> EEN-BY: 154/10 203/0124 221/1 249/303 266/404 280/5003 320/119 123/500   
    BM> EEN-BY: 227/201 154/701 10 0   
    BM> PATH: 203/0 154/10   
    BM> I did all you said in adding ZONE_BLIND 4 to the cfg and it still sent   
    BM> out my aka's in the seen-by's.  I disabled the ZONE Blind optionand now   
    BM> it strips my aka's.  Cound Rob have done some other coding for this?   
    BM> This message has the toggle set to disable and there in no ZONE_BLIND   
    BM> statement in the cfg.  Check the paths and seenbys to see if 100/24 and   
    BM> 973/2 are still there.   
      
   It strips your AKAs, as well as any other nodes in other zones other than zone   
   1 out of the PATH statement. See the PATHI have here for this message as   
   evidence. Bjorn in Zone 2 to me in Zone 1. The system it passed before   
   lie in regards to their experiment?   
      
   Using ZONE_BLIND by itself would includeevery one of your addresses listed   
      
   The "ZONE_BLIND 4" option should only include your fidonet addresses, and not   
      
   If you had ZONE_BLIND 4 as the first line in your sbbsecho.cfg, you shouldn't   
   have sent out any other addresses besides your 1:* ones. If you did, then   
   something wasn't done properly. Did you try recycling Synchronet?   
      
   Joe is using this same feature on Win32, and it seems to be working fine for   
   him. I'mnot sure what the deal is seeing as though I'm running Linux here.   
      
   I can't really get the facts out of your message currently,because someone   
   between you and I are also stripping zones out of the PATH line (Probably   
   Ross, since HPT doesn't have an option to change that, but hopefully it will   
   in the future).   
      
   Regards,   
   Nick   
      
   --- Mystic BBS v1.10 A39 (Linux)   
    * Origin: Dark Sorrow | telnet://bbs.darksorrow.us (1:154/701)