MSGID: 1:229/426 AD541287
On 03 Dec 16  09:14:18, Mark Hofmann said the following to All:

MH> For reasons I can't explain, I am unable to get the hub to send any message
MH> to my Mystic BBS node.  It doesn't pack any messages - even when I do a
MH> %RESCAN. I watch it go through the %RESCAN and the packet that gets sent ha
MH> no messages in it.  AREAFIX says I'm subscribed to all the areas, but none
MH> arrive or are packed on the D'Bridge side.  

The RESCAN functionality is heavily dependant on the state of your message 
areas. On *.MSG areas, it will rescan to the downlink the messages in each 
subscribed area when it receives that request. Needless to say if the *.MSG 
files are purged, or the area is Passthru, no rescanning can take place.
The ability to rescan messages was never written to be elaborate beyond this 
level of functionality. Any Rescan requests must also follow the security 
criteria defined in Config-Packet/Mail.

More to the point.... If D'Bridge is not sending messages to one system, but
sending to others, the problem is most likely the BinkD stage-directory is
missing. The stage directories are named in Base36 Queue format and DBUTIL
QNAME can be used to determine the directory name.

For example, your Queue is in C:\QUEUE and you cannot send messages to
1:229/426. Type DBUTIL QNAME 1:229/426 and it returns 00106D.0BU. BinkD 
staging directories always start with "D-" so the directory 
C:\QUEUE\D-00106D.0BU should be created if it does not exist.

The storage method if the Mystic system is a point, is "-POINT" plus whatever 
the point address is. D-POINT.006 means .6 off your primary address. 
Currently, it is not possible to have multiple point addresses defined; but 
there is a workaround you can do with DBUTIL MOVE that I can explain further.

Nick

--- Renegade vY2Ka2