On 04 Sep 17  10:51:06, C.G. Learn said the following to All:   
      
   CL> 1. Whit the new netmail notification, it works great if I set Dbridge to   
   CL> Automatic, but when I set it to external, I get no notification I have new   
   CL> netmail, and since I use a 3rd pary processor, is there a way or an option    
   CL> can set to tell me I have new netmail using the external option. I'd love t   
      
   When D'Bridge tosses mail automatically, it creates two semaphore files -    
   DBRIDGE.NMW (NetMail Waiting) and DBRIDGE.EMW (EchoMail Waiting).   
      
   The mailer "idle screen" checks for those two semaphore files and if they    
   exist, displays the New Mail notification on the screen. DBRIDGE.EMW can also    
   contain the Echomail Groups if desired.   
      
   D'Bridge has no way of knowing what your external tosser does. It has no way    
   of knowing that your external tosser did in fact toss new mail; so the best I    
   can suggest is creating a batch file or condition that creates the semaphore    
   files based on the results of your tosser, if that is possible.   
      
   CL> 2. Just to be positive, when I use the 3rd party mail processor (GAPNET) fo   
   CL> echo mail, I want to put the packet to be exported into the queue directory   
   CL> correct. When I do this, it sits there and nothing happens. The extension i   
   CL> changed, but thats it, it never goes out. Should I change my program to wri   
   CL> netmail message to send it out, or am I missing a step somewhere. Sorry for   
   CL> the questions. Mailers and me just don't get along.   
      
   Any tosser, BBS program or 3rd-party application that generates any outbound   
   mail for another system has to use a common methodology to do so. Thats not a    
   D'Bridge-specific thing. That is also for FrontDoor, TIMS, Binkleyterm, etc.    
      
   Think of it as an agreed upon "standard" for all Fido programs to interact.   
      
   So in this case, you cannot just tell your BBS to put mail in the D'Bridge   
   Queue and expect it to be sent, unless the BBS software specifically supports   
   the D'Bridge Queue format. Chances are... it doesn't.   
      
   If the program you are using does not specifically support D'Bridge, then it   
   must use another method known as "ArcMail" or Netmail *.MSG attachments.    
   It may also be called "Frontdoor mode". What that means is that the program   
   generates a dummy Netmail message for the destination system with the packet   
   as a file attachment.   
      
   So you configure the program to write Netmails in the D'Bridge Netmail   
   directory. You configure that program's staging directory to one of your   
   choice. But NOT the D'Bridge Queue or Packet directories please.   
      
   When ArcMail is used, D'Bridge will scan the Netmail directory and build the    
   outgoing mail for the destination system... provided of course that the    
   routing, nodelist, Internet settings etc is all correct.   
      
   When D'Bridge builds the Queue, its reading that dummy Netmail and seeing that   
   it must send a file... in this case, the mail created by your external tosser.   
      
   I hope this explains this all better. ArcMail is the most basic method for    
   3rd-party external programs to talk to mailers, especially InterBBS games and    
   all that stuff.   
      
   The D'Bridge Queue and Packets directories are used internally by D'Bridge   
   and should NEVER be used by any other programs, unless the program   
   specifically has support for D'Bridge and those directories.   
      
   Nick   
      
   --- Renegade vY2Ka2   
    * Origin: Joey, do you like movies about gladiators? (1:229/426)