>i don't know how bbbs logs or if you are on *nix but i have increased my syslo   
   >retention so i could have time to go back and hunt down anomalies days or week   
   > later...   
      
   I am running slackware and I haven't deleted any logs yet (it's a new install).   
    I will add the logs to logrotate at some point. I usually keep 30 days of   
   logs.   
      
   BBBS writes classic logs. Mailer sessions are logged in each nodes log and   
   utilities like bogus (the tosser/scanner) log to log0.   
      
   > tldr; do the logs indicate why that file was left behind and the processing   
   > didn't complete properly?   
      
   No, the log0 just logs one line like this..   
      
   181231 21:15 Message base locked   
      
   I run "bbbs bogus w" from the gotmail.bz script. Whenever bbbs or bbbsd get new   
    mail it runs the gotmail script. It's worked well for me on this installation   
   since Dec 15. 181231 is the first mention of Message base locked that I see in   
   my logs. gotmail.bz  is a compiled script. By default it touches gotmail.flg. I   
    added the "bbbs bogus w" command to the script as suggested in the sysop.txt.   
   Here is my gotmail.bz..   
      
   ---- begin ----   
   int main() {   
     int f;   
     if ((f=fopen(sprintf("%sgotmail.flg",bg_tempdir),"wb"))!=-1) fclose(f);   
     system("bbbs bogus w",0,0);   
   }   
   ---- end ----   
      
   --- BBBS/Li6 v4.10 Toy-3   
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)