On 15 Oct 16  18:34:48, Zazz said the following to Nick Andre:

Z> The outbound folder for VADV is \va\fido\out\000001 (which is if you are on
Z> node 1 is where the packet is placed.  *.fr0
Z> 
Z> I told DBridge that the \va\fido\out\000001 is the Temp Queue.  So when I
Z> tell DBridge to refresh the queue it does it's thing, the 000001 folder is
Z> emptied but nothing shows up in the Queue

That right there is the problem. The directory you tried in D'Bridge is
unique to D'Bridge and must NEVER be shared with ANY other program. The F1 
Help screen warns of this. You are losing mail and deleting packets this way. 

Under absolutely NO circumstances should the Queue and Temporary Packets
directory be shared with other software; unless that software is specifically
designed and tested to work with D'Bridge.

But read below...

Z> I'll have to find out how the message base is stored.  It is in a database a
Z> far as I understand it but do not know anything else.  

The biggest challenge with BBS software that uses proprietary storage formats 
for mail, is what to do when it comes time to make them play nicely with 
3rd-party software to actually do Fido stuff. At the bare minimum, the BBS 
software has to have a way to at least create *.MSG-formatted mail files, so 
that software like D'Bridge can pack it up and build an outbound Queue entry.

This isn't a D'Bridge problem; no 3rd-party mailer can work with your BBS 
software unless there is a "common ground" for the two to
exchange mail with. 
Not Frontdoor, not Intermail, not Binkleyterm... nothing can work.

So the goal is to figure out how VADV can work with *.MSG storage for Netmail
and a method known as ArcMail file-attaches. This will allow D'Bridge to
work with your BBS software; though I will recommend the way is to allow
D'Bridge to process all Netmail AND Echomail outgoing messages using the
internal tosser.

I know VADV is popular in some circles, so I'm sure there is a way?

Nick

--- Renegade vY2Ka2