NA> More to the point.... If D'Bridge is not sending messages to one system,   
   NA> but sending to others, the problem is most likely the BinkD   
   NA> stage-directory is missing. The stage directories are named in Base36   
   NA> Queue format and DBUTIL QNAME can be used to determine the directory   
   NA> name.   
   NA> For example, your Queue is in C:\QUEUE and you cannot send messages to   
   NA> 1:229/426. Type DBUTIL QNAME 1:229/426 and it returns 00106D.0BU. BinkD   
   NA> staging directories always start with "D-" so the directory   
   NA> C:\QUEUE\D-00106D.0BU should be created if it does not exist.   
      
   Thanks for the detailed information on the queue information.  I had forgotten   
   the method on figuring out the queue name vs. node information.  That was a   
   big help in investigating - and was hoping that was the issue, but the   
   directory for the Mystic node is there.   
      
   I'll try and explain the history on this as it makes no sense.   
      
   From my Mystic BBS, I AREAFIXed the Dovenet areas from my D'Bridge hub like I   
   do with everything else.  I also did a %RESCAN.  That worked fine, but it   
   never downloaded ALL of the messages from each area.  Not a big deal, but it   
   seems to get to a certain date and stop.   
      
   Fast forward to now, I never never received a single message to any echos on   
   Dovenet on the Mystic side.  I don't see them in the D'Bridge queue or   
   anything.  They are going to my WWIV BBS (different node), but not my Mystic   
   Node.     
      
   I'm starting to think it is *.MSG related in those areas for some reason -   
   espcially since the original %RESCAN never really picked up everything from   
   the get-go.   
      
   My D'Bridge hub is still working fine sending messages to my WWIV BBS, though.   
   Just strange!  Will do some more digging.   
      
   - Mark   
      
   --- WWIVToss v.1.51    
    * Origin:  http://www.weather-station.org * Bel Air, MD -USA (1:261/1304.0)