MSGID: 1:154/50@fidonet 684b9b5a   
   PID: C-NET AMIGA BBS 5.36b   
   Does anyone know why BinkD keeps deleting the 1:XXX/XXX.X.CLO files after they   
   are transfered?   
      
   This contains the ALT PATH specified in CONFIG/FTN/TOSSER field in the FTN   
   config.  C-Net seems to only create it once a day.  Once it is deleted, TOSS   
   will return an error saying it can not write tha packet to *.CLO   
      
   I have to mnaually create a blank .CLO in order for Message Base traffic to be   
   tossed.   
      
   I ended up writing a script to call CNET:TOSS which will write a blank file if   
   one is not found.   
      
   (Note is you go this route, you MUST add the SCRIPT permission in order for   
   CRON to be able to run it as an executable).   
      
   PROTECT  +s   
      
   Here is a copy of the script.   
      
    CNET Amiga TOSS script   
    12 June 2025 by Brent Hendricks (Rug Rat)   
    Connect to: The Rat's Den (AMIGA) - bbs.catracing.org 6840   
      
   Check to see if .clo is present, if not create it.   
   IF NOT Exists OUTBOUND:1.135.115.0.clo   
           ECHO > OUTBOUND:1.135.115.0.clo   
   ENDIF   
    Now run CNET:TOSS as normal   
   CNET:TOSS   
    * C-Net/5   
    * Origin: call.rofbbs.com ports 6800 6400 8502 / 423-541-8271 (1:154/50)   
   SEEN-BY: 104/119 105/81 106/201 114/10 128/187 129/305 135/115 153/7715   
   SEEN-BY: 154/10 50 110 218/700 220/20 30 221/6 226/30 44 50 227/114   
   SEEN-BY: 229/110 114 275 300 307 310 317 426 428 470 664 700 705 291/111   
   SEEN-BY: 301/1 320/219 322/757 396/45 902/26 3634/12 5075/35   
   PATH: 154/50 10 229/426